Interoperation using an IBM MQ link
An IBM MQ link provides a server to server channel connection between a service integration bus and an IBM MQ queue manager or queue-sharing group, which acts as the gateway to the IBM MQ network.
An IBM MQ link enables WebSphere Application Server applications to send point-to-point messages to IBM MQ queues, which are defined as destinations in the service integration bus. The link also enables IBM MQ applications to send point-to-point messages to destinations in the service integration bus, which are defined as remote queues in IBM MQ. With a publish/subscribe bridge, the link also enables WAS applications to subscribe to messages published by IBM MQ applications, and IBM MQ applications to subscribe to messages published by WAS applications.
The IBM MQ queue manager or (for IBM MQ for z/OS) queue-sharing group that provides the gateway for an IBM MQ link to connect to an IBM MQ network is known as the gateway queue manager. When defining an IBM MQ link, you nominate one IBM MQ queue manager or queue-sharing group to act as a gateway queue manager. This queue manager or queue-sharing group must exist and be active in the IBM MQ network
To the gateway queue manager, the messaging engine with the IBM MQ link (and hence the bus that the messaging engine is a member of) appears to be an IBM MQ queue manager. To the messaging engine with the IBM MQ link, the gateway queue manager (and any other queue managers connected to it) appears to be a foreign bus.
The IBM MQ link has sender and receiver channels defined on it. These channels communicate with, respectively, partner receiver and sender channels on the gateway queue manager. The IBM MQ link communicates with IBM MQ using the IBM MQ message formats and communication protocol. The IBM MQ link converts the service integration message formats to and from the IBM MQ message formats.
When WAS applications send messages over the IBM MQ link, the messages are transmitted through the IBM MQ link sender channel to the partner receiver channel on the gateway queue manager. The receiver puts the messages to the target destinations in the IBM MQ network.
Messages from the IBM MQ network, that are destined for WAS applications, are sent to the gateway queue manager. The sender channel on the gateway queue manager transmits the messages to the IBM MQ link link receiver channel, from where they are distributed to the target destinations on WAS.
Subtopics
- Network topologies for interoperation using an IBM MQ link
These examples show a range of network topologies, from simple to complex, that enable WAS to interoperate with IBM MQ using an IBM MQ link.- Message exchange through an IBM MQ link
A IBM MQ link connects to a specific foreign bus that represents an IBM MQ network, and enables messaging engines on a service integration bus to exchange messages with queue managers on the IBM MQ network.- Point-to-point messaging with an IBM MQ network
The IBM MQ link, defined on a messaging engine in the service integration bus, describes the attributes required to connect to, and send or receive messages to or from, an IBM MQ queue manager or (for IBM MQ for z/OS) queue sharing group that acts as a gateway to the IBM MQ network.- Publish/subscribe messaging through an IBM link
On a IBM MQ link, we can set up publish/subscribe messaging between WAS and the IBM MQ publish/subscribe function, or a separate publish/subscribe broker.- Request-reply messaging through an IBM MQ link
When a JMS producer sends a message, it can provide a reply-to destination. The reply-to destination is a JMS destination defined using the producer's messaging provider. This style of messaging is known as request-reply, or request and response. Request-reply messages can be exchanged across the IBM MQ link as either point-to-point or publish/subscribe messages.- Strict message ordering using the strict message ordering facility of the WAS default messaging provider
Strict message ordering can be achieved when deploying message driven bean applications to the IBM MQ messaging provider for WAS when no special facilities have been coded into the application to handle messages arriving out of order using the strict message ordering facility of the WAS default messaging provider.- Secure connections to an IBM MQ network
Connections between a WAS and an IBM MQ network can use the SSL protocol to increase the confidentiality and integrity of messages transferred between a messaging engine on a service integration bus and IBM MQ.- Messaging between two application servers through IBM MQ
Use IBM MQ links to send a WAS message from one application server to another through an IBM MQ network.- Messaging between two IBM MQ networks through an application server
Use IBM MQ links to send a message from one IBM MQ network to another through a WAS application server.