Configuring the WebSphere Message Broker JMS node to implement Apache messaging server communication

The Apache ActiveMQ (hereinafter referred to as ActiveMQ) is the most popular and powerful open source message agent and messaging server. It supports JMS 1.1 and Java EE 1.4. Because many enterprises are integrating open source technology into their message http://www.aliyun.com/zixun/aggregation/13748.html "", this article will use an example message to show how to configure the Ibm®websphere ®message Broker (hereinafter referred to as message Broker) that enables it to integrate with the Apache ActiveMQ as a JMS provider.

To demonstrate the integration of message Broker with ActiveMQ, this article uses the integrated, Service (IaaS) provider Meddius, which uses ActiveMQ to provide a HL7 solution through JMS. In the following illustration, ActiveMQ receives HL7 messages from Meddius via JMS, sends them to message Broker (it uses its own Compute nodes to process them), and then writes the HL7 transaction to a database table.

Figure 1

Configure ActiveMQ

Download and install ActiveMQ V5.7 from the Apache ActiveMQ Web site to a Microsoft Windows machine with message Broker Toolkit installed. After the installation is complete, start the ActiveMQ message agent: Run the batch file Apache-activemq-5.6.0\bin\activemq.bat. Until you see the following message in the console output:
Figure 2

Open a browser window, and then enter Http://localhost:8161/admin in the URL box to open the ActiveMQ management console:
Figure 3

Click the Queues tab and create two queues: In.q and D out. Q:
Figure 4

Create a JNDI property file that contains the contents shown below and save it as Jndi.properties:java.naming.factory.initial = Org.apache.activemq.jndi.ActiveMQInitialContextFactoryjava.naming.provider.url = vm:// Localhostconnectionfactorynames = ConnectionFactory, queueconnectionfactory, topicconnectionfactoryqueue.jmsinq = in . QQUEUE.JMSOUTQ = out. Q

Jmsinq and JMSOUTQ correspond to physical queues in. Q and out. Q's JMS target.

You can also use a predefined connection factory named ConnectionFactory to add dynamicqueues/as a prefix to the actual queue name to avoid creating jndi.properties files.