Enabling SOA Using WebSphere Messaging

110 Enabling SOA Using WebSphere Messaging

5.1 WebSphere MQ configuration

This section gives an overview of the elements required in WebSphere MQ to

receive and deliver messages. It covers the basics of creating queue managers

and queues, and connecting one queue manager to another. If you are not

familiar with WebSphere MQ concepts, review “WebSphere MQ” on page 28.

To illustrate, let us assume that an application wants to input data to node 1 and

another application wants to get the data from node 2. Assured data delivery is a

requirement.

First we need a queue manager on each node. QM1 will be created on node 1

and QM2 on node 2. In QM1, we have to define a remote queue definition,

sender channel, and transmission queue. In QM2, we have to define target

queue, receiver channel, and listener. This configuration is shown in Figure 5-1.

Figure 5-1 WebSphere MQ - WebSphere MQ integration

Note that in this configuration the following is true:

򐂰 The MQLINK queue in QM1 is a remote queue definition pointing to the

TARGET queue in QM2.

򐂰 QM2 queue in QM1 is a transmission queue.

򐂰 There is a pair of sender and receiver channels between the two queue

managers.

When application APP1 puts XML data on the MQLINK queue, the data is

delivered through the channel. Application APP2 gets the XML data from the

TARGET queue.