You use a WebSphere® MQ server to configure a direct (single bus) connection to a WebSphere MQ for z/OS® queue manager or queue sharing group. For WebSphere Application Server Version 6.1, this must be WebSphere MQ for z/OS Version 6 or later. The administrative
tasks for working with WebSphere MQ
server include creating a WebSphere MQ
server definition, adding it to a service integration bus, specifying
a destination, and (optionally) mediating the destination.
You can configure a service integration queue-type destination
to add messages directly onto a WebSphere MQ queue, or to retrieve
messages directly from that queue, or both. Service integration does
this by communicating directly with the WebSphere MQ queue manager
or queue sharing group where the queue is located.
To configure a queue-type destination that adds messages directly
onto a WebSphere MQ queue, or retrieves messages directly from that
queue, or both, you must complete the following broad steps:
- Define a WebSphere MQ server in your Websphere Application Server
cell. This definition represents the WebSphere MQ queue manager or
queue sharing group where the queue is located. It includes, for example,
information about how the administrative console connects to that
queue manager or queue sharing group for queue discovery.
Note that you do not need a separate WebSphere MQ server definition
for each queue located on that queue manager or queue sharing group;
the same definition works for all queues on that server.
- Make the WebSphere MQ server a member of the service integration
bus that contains the queue-type destinations you want to define.
When you do this, you provide information about how service integration
connects to that queue manager or queue sharing group in order to
add messages to, or retrieve messages from, WebSphere MQ. This can
be different from the way the administrative console connects - for
example, it can use different security credentials.
Note that if you have several service integration buses in your
cell, you can add the same WebSphere MQ server as a bus member into
more than one of these buses.
After you have done this, you can define queue-type destinations
in the service integration bus so that service integration adds messages
directly onto a WebSphere MQ queue located on the WebSphere MQ server,
or retrieves messages directly from that queue, or both.
If you want to mediate a service integration queue-type destination,
then you need to define two queues within the destination. One is
used to queue messages arriving at the destination ready for mediation;
this is called the mediation point. The other is used to queue messages
after mediation is complete and the messages are ready to be consumed;
this is called the queue point. Either the mediation point, or the
queue point, or both, can be defined as WebSphere MQ queues (as previously
described).
Note: You can also configure your service integration bus to exchange
messages indirectly with a WebSphere MQ
network using a WebSphere MQ link. In this case, you
define the WebSphere MQ
network as a foreign bus, and you define the queues within that network
as foreign or alias destinations. You do not need to define the WebSphere MQ queue managers
or queue sharing groups in the foreign bus (other than the gateway
queue manager) as service integration resources, because service integration
does not communicate with them directly.