+

Search Tips   |   Advanced Search

Interoperation using an IBM MQ server

An IBM MQ server represents an IBM MQ queue manager or (for IBM MQ for z/OS ) queue-sharing group. Service integration can communicate directly with an IBM MQ queue manager or queue sharing group where an IBM MQ queue is located. We can configure a service integration queue-type destination to add messages directly onto the IBM MQ queue, and retrieve messages directly from the queue.

The interoperation through IBM MQ server (queue manager or queue-sharing group) is deprecated in WebSphere Application Server version 9. As an alternative method, use IBM MQ resource adapter or IBM MQ link to connect to the IBM MQ network for interoperation. See Deprecated features.

For interoperation with WAS v7.0 or later, the version of IBM MQ must be IBM MQ for z/OS v6 or later, or IBM MQ (distributed platforms) v7 or later.

To configure WAS for this style of interoperation with IBM MQ, we define an IBM MQ server. This definition represents the IBM MQ queue manager or queue sharing group that hosts the queue which we want to access. The definition has cell scope. The same IBM MQ server definition works for all queues in the queue manager or queue sharing group.

Next, we add the IBM MQ server as a member of the service integration bus (or buses) that require access to the queues that the IBM MQ server hosts. If we have several service integration buses in the cell, we can add the same IBM MQ server as a bus member into more than one of these buses.

After we have done this, we can define queue-type destinations in the service integration bus so that service integration adds messages directly onto an IBM MQ queue located on the IBM MQ server, or retrieves messages directly from that queue, or both. To help we define your service integration destinations, we can (optionally) select the IBM MQ queue we want to use from a list which the administrative console gets directly from the IBM MQ queue manager or queue sharing group. This facility is called "queue discovery".

To mediate a service integration queue-type destination, then 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 IBM MQ queues (as previously described).

Create and configure an IBM MQ server by or . If we use the administrative console, the server creation wizard can automatically discover resources in the IBM MQ network.


Subtopics


Related:

  • Message exchange through an IBM MQ link
  • IBM MQ server and mediated exchange scenarios
  • Use an IBM MQ server to integrate IBM MQ queues into a bus
  • SIBAdminCommands: IBM MQ server administrative commands for the AdminTask object
  • IBM MQ server: Restrictions with mixed level cells and clusters