Pulling Messages From WebSphere MQ

By setting up a Transmit queue on WebSphere MQ, and a bridge listener on a WebSphere MQ Everyplace queue manager we can enable the latter to pull messages from the former. Although in theory this is sufficient to pull messages from the transmission queue, we cannot place messages onto the transmission queue without creating extra queues on a WebSphere MQ queue manager.

Single pull route

To allow the messages to be correctly routed we create extra queues on a WebSphere MQ queue manager. The simplest form is to create a remote queue on WebSphere MQ to allow messages addressed to TargetQueue@MQeEarthQM to be accepted by the WebSphere MQ queue manager, see Figure 89.

Figure 89. Creating a remote queue on WebSphere MQ.


Messages addressed to TargetQueue@MQeEarthQM are placed upon the WebSphere MQ Transmit queue. The bridge listener then pulls them from the transmit queue and presents them to the WebSphere MQ Everyplace queue manager. Message resolution then takes place, see Figure 90.

Figure 90. Bridge listener pulling from a WebSphere MQ Everyplace transmit queue


This is effectively a single pull message route, see Figure 91.

Figure 91. A single pull message route.


Multiple Pull Route

It is generally more efficient to use a multiple pull message route as this requires the same number of resource definitions, but will handle all the traffic for WebSphere MQ Everyplace queue manager. This is done using a Remote queue manager alias on WebSphere MQ (effectively a remote queue where the target queue name is the same as the target queue manager name, see Figure 92).

Figure 92. A multiple pull message route.


Message resolution works as previous, but now messages for any queue on MQeEarthQM will be move, making this a multiple pull message route, see Figure 93.

Figure 93. Multiple pull route, expressed using message route schema




© IBM Corporation 2002, 2003. All Rights Reserved