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

Figure 97. A client communicating with WebSphere MQ.


We have added the following:

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

Figure 98. 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 99.

Figure 99. 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 100.

Figure 100. Pushing messages to WebSphere MQ


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

Figure 101. 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, 2003. All Rights Reserved