Messaging between two application servers through WebSphere MQ

You can use WebSphere® MQ links to send a message from one WebSphere Application Server application server to another through a WebSphere MQ network.

The following figure shows how you can exchange messages between two application servers through an intermediate WebSphere MQ network. A local service integration bus is connected by a WebSphere MQ link to a WebSphere MQ network, which is a direct foreign bus. The WebSphere MQ network is in turn connected by a WebSphere MQ link to another service integration bus, which is a indirect foreign bus.
Figure 1. Exchanging messages between two application servers through an intermediate WebSphere MQ network.
This figure is described in the surrounding text.

In the general case, the WebSphere MQ network includes two gateway queue managers; one connects to the local bus using a WebSphere MQ sender-receiver channel pair (known to the local bus as a WebSphere MQ link), the other connects to the indirect foreign bus using another WebSphere MQ sender-receiver channel pair (known to the indirect foreign bus as a WebSphere MQ link). In the simplest case, the same gateway queue manager connects to both the local bus and the indirect foreign bus.

The WebSphere MQ network must be configured to route messages as required between the local bus and the indirect foreign bus. Details of this configuration are not normally important to WebSphere Application Server administrators, but can be found in the WebSphere MQ Intercommunication book (SC34-6059).

Configuration and operation of messaging between two service integration buses through an intermediate WebSphere MQ network is much simpler if you choose bus names that comply with WebSphere MQ queue manager naming restrictions, and if you choose bus destination names that comply with WebSphere MQ queue naming restrictions:

While messages are being transported through the WebSphere MQ network, important context information is transported in the MQRFH2 header. You should configure the application so that the MQRFH2 header is included.

WebSphere MQ request messages contain a single reply-to queue name to which a receiving application can send responses. The service integration bus has a more advanced reply path (not just a single queue name). You can use reply-to queues for point-to-point messages (queues) and for topics.

Messages with topic style reply-to destinations must have the appropriate publish and subscribe bridge topic mappings defined in the relevant direction in order for reply messages to be transferred between a WebSphere MQ network and WebSphere Application Server. This is not automatic as it is for messages with queue reply destinations.




Related concepts
Learning about interoperating with WebSphere MQ using WebSphere MQ links
Concept topic Concept topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Aug 31, 2013 4:28:44 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=pix&product=was-nd-mp&topic=cjc0006_
File name: cjc0006_.html