+

Search Tips   |   Advanced Search

IBM MQ link sample configuration

This sample configuration illustrates how we can use an IBM MQ link to connect WebSphere Application Server service integration messaging to IBM MQ messaging.

An IBM MQ link connects one service integration messaging engine, called the gateway messaging engine, to one IBM MQ queue manager or queue-sharing group, called the gateway queue manager. All messaging engines in the service integration bus use the gateway messaging engine to route messages to and from the IBM MQ network; all queue managers and queue-sharing groups in the IBM MQ network use the gateway queue manager to route messages to and from the service integration bus.

Typically, an IBM MQ link consists of two TCP/IP connections:

IBM MQ calls these TCP/IP connections message channels, a receiver channel which connects to the IBM MQ link sender channel and a sender channel which connects to the IBM MQ link receiver channel. The following figure shows a configuration like the one just described, with a IBM MQ link sender channel called BUS1.TO.QM01 and an IBM MQ link receiver channel called QM01.TO.BUS1.

If we only require messages to flow in one direction, we need only define one TCP/IP connection. For example, an IBM MQ link sender channel in service integration that connects to a receiver channel in IBM MQ is enough to support message flow from service integration to IBM MQ. However, this sample builds a configuration that allows messages to flow in both directions.


Sample configuration context

The purpose of this sample is to connect a WAS configuration to an IBM MQ configuration so that asynchronous messages can flow in both directions between the two messaging systems. The sample assumes that we have already set up a WAS configuration like this:

The sample also assumes that we already have an IBM MQ configuration like this:

You select London.server1-BUS1 to be the gateway messaging engine and QM01 to be the gateway queue manager.


Sample configuration for the connections

This section describes the settings that you or your IBM MQ administrator need to configure for the connections:

After configuring and activating these components the applications can exchange messages between WAS service integration messaging and IBM MQ messaging. Optionally we can configure additional administrative artifacts that allow you more detailed control over the queues and destinations, see Sample configuration for the destinations.


Sample configuration for the destinations

The sample JMS destinations in Sample configuration for the connections point directly to the corresponding IBM MQ queues and service integration destinations. If we prefer, we can configure additional components so that:

Refer to the IBM MQ documentation for information about when and how to define remote and alias queues.