Configuring the WebSphere MQ bridge

The configuration of the WebSphere MQ bridge requires you to perform some actions on the WebSphere MQ queue manager, and some on the WebSphere MQ Everyplace queue manager. The bridge can be divided into two pieces:

Figure 46.

This diagram shows the configuration of resources required to route a message from WebSphere MQ Everyplace to WebSphere MQ and from WebSphere MQ to WebSphere MQ Everyplace

Configuration of both types of routes are discussed in the following sections.

The bridge objects are defined in a hierarchy as shown in Figure 47

The following rules govern the relationship between the various objects:

Figure 47. Bridge object hierarchy

Diagrammatic representation of hierarchy of bridge objects described above.

The bridge configuration option allows a WebSphere MQ Everyplace queue managar to communicate with WebSphere MQ host and distributed queue managers through client channels. The bridge component manages a pool of client channels that can be attached to one or more host or distributed queue managers. You can configure multiple bridge-enabled WebSphere MQ Everyplace queue managers in a single network.

A gateway may have a number of transmit queue listeners that use that gateway to connect to the WebSphere MQ queue manager and retrieve a messages from WebSphere MQ to WebSphere MQ Everyplace. A listener uses only one service to establish its connection, with each listener connecting to a single transmission queue on the WebSphere MQ queue manager. Each listener moves messages from a single WebSphere MQ transmission queue to anywhere on the WebSphere MQ Everyplace network, via its parent gateway queue manager. Thus, a single gateway queue manager can funnel multiple WebSphere MQ message sources into the WebSphere MQ Everyplace network.

When moving messages in the other direction, from WebSphere MQ Everyplace to WebSphere MQ, the gateway queue manager configures one or more bridge queues. Each bridge queue can connect to any queue manager directly and send its messages to the target queue. In this way a gateway can dispatch WebSphere MQ Everyplace messages routed through a single WebSphere MQ Everyplace queue manager to any WebSphere MQ queue manager, either directly or indirectly.



© IBM Corporation 2002, 2003. All Rights Reserved