You can use WebSphere® MQ links to send
a message from one WebSphere MQ
network to another through a WebSphere Application Server application
server.
The following figure shows how you can exchange messages between
two WebSphere MQ networks
through an intermediate service integration bus. A WebSphere MQ network
is connected by a WebSphere MQ link to a service integration bus ,
which in turn is connected by a WebSphere MQ link to another WebSphere
MQ network. Both the WebSphere MQ networks are direct foreign buses,
and the service integration bus is a local bus.
Figure 1. Exchanging
messages between two WebSphere MQ
networks through an intermediate application server.
Configuration and operation of messaging between two WebSphere MQ networks (buses) through an
intermediate service integration bus is much simpler if you choose
a service integration bus name that complies with WebSphere MQ queue manager naming restrictions:
- The queue managers in the WebSphere MQ
networks "see" the intermediate service integration bus as a
queue manager, and refer to it using the virtual queue manager name.
Provided that the service integration bus name complies with WebSphere MQ restrictions
for queue manager names, it is possible (and highly desirable) for
the virtual queue manager name used by both WebSphere MQ networks to be the same as
the bus name used by service integration.
- The service integration bus includes two gateway messaging engines,
one connecting to each of the WebSphere MQ
networks using WebSphere MQ links (known to the WebSphere MQ gateway queue
managers as WebSphere MQ
sender-receiver channel pairs). The service integration bus must
define the two WebSphere MQ
networks as foreign buses with names the same as the WebSphere MQ names for the gateway queue
managers.
Messages received by the service integration bus from one WebSphere MQ network and destined
for another WebSphere MQ
network specify both the send-to queue name and the send-to queue
manager name. Service integration interprets the send-to queue manager
name as a bus name. When the send-to queue manager is the gateway
queue manager for the send-to WebSphere MQ
network, service integration routes the message correctly. When the
send-to queue manager is not the gateway queue manager for the send-to WebSphere MQ network, there
are two options:
- In service integration, define the send-to queue manager as an
indirect foreign bus, connected by the WebSphere MQ foreign bus defined with the
name of the gateway queue manager.
- In service integration, define the send-to queue (destination
name in service integration terminology) and queue manager (bus name
in service integration terminology) combination with an alias destination
that maps the combination to the send-to WebSphere MQ network (foreign bus in service
integration terminology) with the destination name in the form send-to-queue-name@send-to-queue-manager-name.
Messages received by the service integration bus from one WebSphere MQ network and destined
for another WebSphere MQ
network can include a reply-to queue. This is specified as the reply-to
queue name and the reply-to queue manager name. When the service
integration bus receives the message, the WebSphere MQ link replaces this reply-to
information with a service integration bus destination comprising
a bus name (which is the WebSphere MQ
queue manager name of the gateway queue manager) and a destination
name of the form reply-to-queue-name@reply-to-queue-manager-name.
This new reply-to information travels with the message to the receiving WebSphere MQ application.
Note that this requires the combined length of the reply-to queue
name, the "@" character, and the reply-to queue manager name to be
less than or equal to the WebSphere MQ
maximum queue name length of 48 characters.