The JMS transport protocol uses JMS queues to hold the JMS messages passed between Business Integration Connect and the back-end system. With WebSphere MQ version 5.3, creation of the JMS queues involves the following steps:
If you have not already defined a queue manager for Business Integration Connect and the back-end system, you must do so before creating the MQ JMS queues. You will need a queue manager if you are doing JMS integration. You must decide whether to install a new queue manager or to use an existing one. An existing queue manager can be the same queue manager as Business Integration Connect, the same queue manager as the back-end system, or another existing queue manager. Refer to the WebSphere MQ documentation for instructions on how to create a queue manager.
The samples in this chapter assume that a WebSphere MQ queue manager exists and is named as follows:
bcg.queue.manager
Once the queue manager exists, make sure that the following objects are created:
To create the MQ channels and transmission queue, use the WebSphere MQ Command Environment, runmqsc, which WebSphere MQ provides. This tool provides a command-line interface for you to enter queue-management commands.
To use runmqsc tool to create your MQ channels and transmission queue, follow these steps:
WebSphereMQ_Root\java\bin
where WebSphereMQ_Root is the installation directory of WebSphere MQ.
runmqsc queueManager
where queueManager is the name of your WebSphere MQ queue manager.
define qlocal(transQueueName) usage(xmitq) put(enabled) get(enabled)
where transQueueName is the desired name of your JMS transmission queue.
define channel(sndrChannelName) chltype(sdr) xmitq(transQueueName) conname('remote m/c ip') stop channel(sndrChannelName)
where sndrChannelName is the desired name of your JMS sender channel andtransQueueName is the name of the JMS transmission queue you created in step 3a.
define channel(rcvrChannelName) chltype(rcvr) xmitq(transQueueName) stop channel(rcvrChannelName)
where rcvrChannelName is the desired name of your JMS receiver channel andtransQueueName is the name of the JMS transmission queue you created in step 3a.
Figure 30 shows the creation of sample JMS channels and a transmission queue hosted by the bcg.queue.manager queue manager.
Figure 30. Commands to create sample JMS channels and transmission queue
runmqsc bcg.queue.manager
define qlocal(TRANSQ) usage(xmitq) put(enabled) get(enabled) define channel(SENDER) chltype(sdr) xmitq(TRANSQ) conname('remote m/c ip') stop channel(SENDER) define channel(RECEIVER) chltype(rcvr) stop channel(RECEIVER)
The commands in Figure 30 create the following MQ objects:
To create the MQ JMS local queues, use the WebSphere MQ Command Environment, runmqsc.
To use the runmqsc tool to create your local MQ queues, follow these steps:
define qlocal(inQueueName)
where inQueueName is the desired name of your JMS inbound queue.
define qlocal(outQueueName)
where outQueueName is the desired name of your JMS outbound queue.
end
You can leave your command prompt open, as you will need it in subsequent configuration steps.
Figure 31 shows the creation of sample JMS queues hosted by the bcg.queue.manager queue manager.
Figure 31. Commands to create sample JMS queues
define qlocal(JMSIN) define qlocal(JMSOUT)
The commands in Figure 31 create the following JMS queues: