Overview of configuring the bridge

The configuration of the MQ bridge requires you to perform some actions on the MQ queue manager, and some on the MQe queue manager. The bridge can be divided into two pieces:
  • Configuration of resources required to route a message from MQe to MQ
  • Configuration of resources required to route a message from MQ to MQe

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

Figure 1. Bridge configuration
This diagram shows the configuration of resources required to route a message from MQe to MQ and from MQ to MQe

The bridge objects are defined in a hierarchy as shown in the following diagram:

Figure 2. Bridge object hierarchy
Diagrammatic representation of hierarchy of bridge objects described above.
The following rules govern the relationship between the various objects in that diagram:
  • An MQe bridges object is associated with a single MQe queue manager.
  • A single bridges object may have more than one bridge object associated with it. You might want to configure several MQ bridge instances with different routings.
  • Each bridge can have a number of MQ queue manager proxy definitions.
  • Each MQ queue manager proxy definition can have a number of client connections that allow communication with MQe.
  • Each client connection connects to a single MQ queue manager. Each connection may use a different server connection on the MQ queue manager, or a different set of security, send, and receive exits, ports or other parameters.
  • An MQ bridge client connection may have a number of transmission queue listeners that use that bridge service to connect to the MQ queue manager.
  • A listener uses only one client connection to establish its connection.
  • Each listener connects to a single transmission queue on the MQ system.
  • Each listener moves messages from a single MQ transmission queue to anywhere on the MQe network, (through the MQe queue manager its bridge is associated with). So an MQ bridge can funnel multiple MQ message sources through one MQe queue manager onto the MQe network.
  • When moving MQe messages to the MQ network, the MQe queue manager creates a number of adapter objects. Each adapter object can connect to any MQ queue manager (providing it is configured) and can send its messages to any queue. So an MQ bridge can dispatch MQe messages routed through a single MQe queue manager to any MQ queue manager.

The bridge configuration option allows an MQe queue manager to communicate with 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 MQe queue managers in a single network.

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

When moving messages in the other direction, from MQe to 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 MQe messages routed through a single MQe queue manager to any MQ queue manager, either directly or indirectly.


Terms of use | WebSphere software

(c) Copyright IBM Corporation 2004, 2005. All rights reserved.