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:
- Configuration of resources required to route a message from WebSphere MQ
Everyplace to WebSphere MQ
- Configuration of resources required to route a message from WebSphere MQ
to WebSphere MQ Everyplace
Figure 46.

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:
- A WebSphere MQ Everyplace bridges object is associated with a single
WebSphere MQ Everyplace queue manager.
- A single WebSphere MQ Everyplace bridges object may have more than one
bridge object associated with it. You may wish to configure several
WebSphere MQ bridge instances with different routings.
- Each bridge can have a number of WebSphere MQ queue manager proxy
definitions.
- Each WebSphere MQ queue manager proxy definition can have a number of
client connections that allow communication with WebSphere MQ
Everyplace.
- Each client connection connects to a single WebSphere MQ queue
manager. Each connection may use a different server
connection on the WebSphere MQ queue manager , or a different set of
security, send, and receive exits, ports or other parameters.
- A WebSphere MQ bridge client connection may have a number of transmission
queue listeners that use that bridge service to connect to the WebSphere MQ
queue manager.
- A listener uses only one client connection to establish its
connection.
- Each listener connects to a single transmission queue on the WebSphere MQ
system.
- Each listener moves messages from a single WebSphere MQ transmission queue
to anywhere on the WebSphere MQ Everyplace network, (through the WebSphere MQ
Everyplace queue manager its bridge is associated with). So a WebSphere
MQ bridge can funnel multiple WebSphere MQ message sources through one
WebSphere MQ Everyplace queue manager onto the WebSphere MQ Everyplace
network.
- When moving WebSphere MQ Everyplace messages to the WebSphere MQ network,
the WebSphere MQ Everyplace queue manager creates a number of
adapter objects. Each adapter object can connect to any
WebSphere MQ queue manager (providing it is configured) and can send its
messages to any queue. So an WebSphere MQ bridge can dispatch WebSphere
MQ Everyplace messages routed through a single WebSphere MQ Everyplace queue
manager to any WebSphere MQ queue manager.
Figure 47. Bridge object hierarchy

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