Bus topology that links to IBM MQ networks

Service integration buses can link to IBM MQ networks. Applications that are connected to an IBM MQ queue manager or queue-sharing group can send messages to an application that is attached to a service integration bus, and vice versa.

One way to connect a service integration bus to an IBM MQ network is to use a IBM MQ link. Another way is to use the IBM MQ server facility. This topic describes the WebSphere® MQ link.

A IBM MQ link connects a messaging engine to a IBM MQ queue manager or queue-sharing group (known as the gateway queue manager) by using sender and receiver channels, thereby connecting the bus and the IBM MQ network.

The IBM MQ link provides connectivity not just with the messaging engine that hosts the link, but also with the other messaging engines in the bus. All the messaging engines in the bus appear to the IBM MQ network as if they were a single queue manager (they inherit the queue manager name from the IBM MQ link).

IBM MQ links can be used in a number of different configurations as shown in Figure 1 and Figure 2. A messaging engine can contain multiple IBM MQ links.

Figure 1. Service integration buses with links to an IBM MQ network
Two service integration buses, each connected through a IBM MQ link on a messaging engine to a IBM MQ system.
Figure 2. Service integration bus with links to IBM MQ networks
Two IBM MQ systems, each connected through a IBM MQ link to separate messaging engines in a service integration bus.

You can also use an IBM MQ link to form a publish/subscribe bridge that allows publication and subscription between WebSphere Application Server and the IBM MQ native publish/subscribe capability.