WebSphere WebSphere Application Server Network Deployment, Version 6.0.x Operating Systems: AIX, HP-UX, Linux, Solaris, Windows

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 may be:
Figure 1. Exchanging messages between WebSphere MQ link sender and receiver channels, and a gateway queue manager with receiver and sender channels.

The figure below shows the flow of point-to-point messages across the WebSphere MQ link.


The graphic shows a service integration bus in a WebSphere Application Server (on the left), and a foreign bus which represents a WebSphere MQ network (on the right). In the application server there is a messaging engine with a WebSphere MQ link which has an MQLinkSender and an MQLinkReceiver. In the foreign bus there is a gateway queue manager which has WebSphere MQ channels: Receiver and Sender.  A connection, which is a channel, is shown running from the MQLinkSender on the WebSphere MQ link to the Receiver in the foreign bus that represents WebSphere MQ.   A connection, which is a channel, is shown running from the Sender in the foreign bus to the MQLinkReceiver on the WebSphere MQ link.

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 figure below 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. The figure includes the WebSphere MQ client link, and if you wish, you can read more about the client in Managing WebSphere Version 5 JMS use of WebSphere version 6 messaging resources.
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.
The graphic shows a service integration bus in a WebSphere Application Server (on the left), connected to a foreign bus which represents a WebSphere MQ network (on the right). In the application server there is a messaging engine - 'Messaging engine 1' - which has a WebSphere MQ link on it. Connected to Messaging engine 1 are 'Messaging engine 2' and 'Messaging engine 3', which are on the same bus. Messaging engine 2 has an MQ client link on it and the MQ client link is connected to a JMS application outside the bus. Messaging engine 3 is connected directed to a JMS application outside the bus.   In the foreign bus there is a gateway queue manager with WebSphere MQ channels. Connected to the gateway queue manager are 'Queue manager 2' and 'Queue manager 3'; these queue managers are shown outside the foreign bus. A connection is shown between the WebSphere MQ link (on the bus) and the WebSphere MQ channels on the gateway queue manager in the WebSphere MQ network (the foreign bus).

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


Concept topic

Terms of Use | Feedback

Last updated: 5 Oct 2005
http://publib.boulder.ibm.com/infocenter/ws60help/index.jsp?topic=/com.ibm.websphere.pmc.nd.doc\concepts\cjc0004_.html

© Copyright IBM Corporation 2004, 2005. All Rights Reserved.
This information center is powered by Eclipse technology. (http://www.eclipse.org)