Point-to-point messaging with a WebSphere MQ network

This topic describes the concept of point-to-point messaging with WebSphere® MQ.

The WebSphere 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, a WebSphere MQ queue manager that acts as a gateway to other queue managers.

Point-to-point messaging might be:
The following figure shows the flow of point-to-point messages across the WebSphere MQ link. In this example, a service integration bus in WebSphere Application Server, is connected to a foreign bus that represents a WebSphere MQ network. The service integration bus contains a gateway messaging engine with a WebSphere MQ link, which has an MQLinkSender and an MQLinkReceiver. The foreign bus contains a gateway queue manager that has WebSphere MQ channels: Receiver and Sender. Two channel connections are shown; one runs from the MQLinkSender on the WebSphere MQ link to the Receiver in the foreign bus that represents WebSphere MQ, and the other runs from the Sender in the foreign bus to the MQLinkReceiver on the WebSphere MQ link.
Figure 1. Exchanging messages between WebSphere MQ link sender and receiver channels, and a gateway queue manager with receiver and sender channels.
This figure is described in the surrounding text.

See Request-reply across the WebSphere MQ link for more information about these reply messages transmitted across the WebSphere MQ link.

Point-to-point messaging may also include:
The following figure shows how messages can be exchanged between applications and messaging engines that are on the same bus, and between the WebSphere MQ link and queue managers connected to the gateway queue manager in the WebSphere MQ network. In this example, a service integration bus in WebSphere Application Server is connected to a foreign bus that represents a WebSphere MQ network. The service integration bus contains a gateway messaging engine that has a WebSphere MQ link. Messaging engine 2 and Messaging engine 3 are on the same bus and connect to the gateway messaging engine. Messaging engine 2 and Messaging engine 3 each connect to a JMS application outside the bus. The foreign bus contains a gateway queue manager with WebSphere MQ channels. Queue manager 2 and Queue manager 3 are in the foreign bus and connect to the gateway queue manager. There is a two-way connection between the WebSphere MQ link on the service integration bus, and the WebSphere MQ channels on the gateway queue manager in the WebSphere MQ network.
Figure 2. Exchanging messages between messaging engines on a bus that has a WebSphere MQ link that is connected to a gateway queue manager on a foreign bus.
This figure is described in the surrounding text.

There are a number of differences between WebSphere Application Server messaging technology and WebSphere MQ messaging technology:




Subtopics
Request-reply across the WebSphere MQ link
Related concepts
Message reliability levels
Learning about interoperating with WebSphere MQ using WebSphere MQ links
Related tasks
Specifying whether messages are forwarded to WebSphere MQ as JMS messages
Related reference
How service integration converts the message body to and from WebSphere MQ format
How service integration converts the message header fields and properties to and from WebSphere MQ format
Mapping of additional MQRFH2 header fields in service integration
Mapping of message delivery options flowing through the WebSphere MQ link
Concept topic Concept topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Aug 31, 2013 12:02:36 AM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=pix&product=was-nd-zos&topic=cjc0004_
File name: cjc0004_.html