WebSphere MQ Everyplace WebSphere MQ Bridge Message Resolution

A connection between WebSphere MQ Everyplace and WebSphere MQ queue managers involves a collection of objects. The following diagram shows only the entities that form the communications link between the two queue managers, see Figure 83.

Figure 83. Connecting WebSphere MQ Everyplace and WebSphere MQ queue managers.


The important entities are:

These entities are used in the following examples of bridge connectivity, but not shown in the diagrams.

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 84.

Figure 84. 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 85.

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


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

Figure 86. 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 87).

Figure 87. 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 88.

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


Pushing messages to WebSphere MQ

Pushing messages to WebSphere MQ is more straightforward. Again we need to presume the presence of the common components described above, but now we need to create a Bridge Queue which is an WebSphere MQ Everyplace Remote queue that refers to a queue on a WebSphere MQ queue manager, see Figure 89.

Figure 89. Pushing messages to WebSphere MQ.


Messages travel as expected across this remote queue definition, see Figure 90.

Figure 90. Messages travelling across a remote queue definition.


This is exactly the same as a simple push message route between two queue managers, see Figure 91.

Figure 91. Simplified view of route pushing messages to WebSphere MQ


Connecting a client to WebSphere MQ via a bridge

A common topology is to allow messages to flow between WebSphere MQ and a client WebSphere MQ Everyplace queue manager. This cannot happen directly, but requires an intermediate bridge-enabled MQeQueue manager. The client can then be a small footprint device with no knowledge of WebSphere MQ. If we start from the configuration we have above, we can show the additions we will need to make to allow a client (MQeMoonQM, on a device called moon) to communicate with WebSphere MQ, see Figure 92.

Figure 92. A client communicating with WebSphere MQ.


We have added the following:

The topology is more readily seen as message routes, see Figure 93.

Figure 93. Simplified pull routes from WebSphere MQ through a WebSphere MQ Everyplace gateway to a WebSphere MQ Everyplace device style queue manager


Messages can be pushed to WebSphere MQ by using a via connection to chain remote queues, see Figure 94.

Figure 94. Pushing messages using a via connection.


Here we have added a via connection, to route messages destined for MQSaturnQM via MQeEarthQM, and we have added a remote queue definition for MQSaturnQ@MQSaturnQM. The messages can now flow from the client to WebSphere MQ, see Figure 95.

Figure 95. Pushing messages to WebSphere MQ


This topology is more easily understood as a collection of message routes, see Figure 96.

Figure 96. Simplified view showing routes which push messages from a device style WebSphere MQ Everyplace queue manager to a WebSphere MQ queue manager




© IBM Corporation 2002. All Rights Reserved