WAS v8.5 > WebSphere applications > Messaging resources > Interoperation with WebSphere MQ

Interoperation using a WebSphere MQ server

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

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

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

Next, you add the WebSphere MQ server as a member of the service integration bus (or buses) that require access to the queues the WebSphere MQ server hosts. If we have several service integration buses in your cell, we can add the same WebSphere 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 a WebSphere MQ queue located on the WebSphere MQ server, or retrieves messages directly from that queue, or both. To help you define your service integration destinations, we can (optionally) select the WebSphere MQ queue to use from a list which the dmgr console gets directly from the WebSphere MQ queue manager or queue sharing group. This facility is called "queue discovery".

To mediate a service integration queue-type destination, then you must 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).

We can create and configure a WebSphere MQ server or by using wsadmin. If we use the dmgr console, the server creation wizard can automatically discover resources in the WebSphere MQ network.

Subtopics

• Network topologies for interoperation using a WebSphere MQ server connection and WebSphere MQ for z/OS shared queues
  These examples show simple and complex topologies that enable WAS to interoperate with WebSphere MQ using a WebSphere MQ server connection, and a topology for using WebSphere MQ server connections with WebSphere MQ for z/OS shared queues to create a highly available messaging system.
• WebSphere MQ queue points and mediation points
  A WebSphere MQ queue point is used, by a bus destination on a WebSphere MQ server, to hold messages that are ready to be put onto a WebSphere MQ queue. If messages for the WebSphere MQ queue (or queue-sharing group) are processed by a mediation before being made available to WebSphere MQ, then the service integration destination uses a WebSphere MQ mediation point.
• WebSphere MQ server and mediated exchange scenarios
  When you mediate a service integration bus destination, your mediation runs in a bus member and we specify a combination of mediation points and queue points to handle the messages that are mediated. When you interoperate with WebSphere MQ using WebSphere MQ server, we can use one of several mediated exchange scenarios.
• WebSphere MQ server: Connection and authentication
  Each WebSphere MQ server definition includes the connection properties and authentication settings that service integration uses to connect to the associated WebSphere MQ queue manager or queue-sharing group, either for resource discovery or for messaging.
• User identification
  Service integration messages contain two user IDs - a system user ID and an application user ID. WebSphere MQ can set the user identifier field of the WebSphere MQ message descriptor (MQMD) from the system user ID used in the service integration message. Additional processing is required to preserve the service integration application user ID when interoperating with WebSphere MQ using a WebSphere MQ server.
• Request-reply messaging using a WebSphere MQ server
  We can provide a reply-to destination in a message sent to a destination assigned to a WebSphere MQ server bus member. If the reply comes from a WebSphere MQ application, for example a WebSphere MQ JMS application, some restrictions apply to the reply-to destination. You must also configure a WebSphere MQ link over which the reply can flow.
• WebSphere MQ server: Transport chain security
  System security for a connection between service integration and a WebSphere MQ network is provided by the Transport Level Security (TLS) and SSL protocols.

Related concepts:

Message exchange through a WebSphere MQ link
WebSphere MQ server and mediated exchange scenarios

Related

Use a WebSphere MQ server to integrate WebSphere MQ queues into a bus

Reference:

SIBAdminCommands: WebSphere MQ server administrative commands for AdminTask
WebSphere MQ server: Restrictions with mixed level cells and clusters

+

Search Tips   |   Advanced Search