WAS v8.5 > Administer applications and their environment > Welcome to administering Messaging resources > Manage messaging with the default messaging provider > Interoperate with a WebSphere MQ network

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

A WebSphere MQ server represents a WebSphere MQ queue manager or (for WebSphere MQ for z/OS ) queue-sharing group. 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.

WAS can interoperate with WebSphere MQ in any of the following ways:

• Using the WebSphere MQ messaging provider
• Using a WebSphere MQ link
• Using a WebSphere MQ server

Each type of interoperation is designed for different situations, and provides different advantages. For information about the differences between these approaches, see Interoperate with a WebSphere MQ network.

Decide which method to use to configure these resources. We can configure WebSphere MQ server resources using the dmgr console as described in this task, or using the SIBAdminCommands: WebSphere MQ server administrative commands for AdminTask. To set up and use a WebSphere MQ server, you configure the server properties, add the server to a service integration bus as a bus member, and create a WebSphere MQ queue-type destination. Destinations assigned to a WebSphere MQ server bus member can also be mediated.

You add the WebSphere MQ server as a bus member so that messaging engines on the bus can access queues on the target WebSphere MQ system. If your WebSphere MQ server is connected to a queue-sharing group, your bus applications can access shared queues on the target installation.

Notes:

• We can configure a WebSphere MQ server to connect to a WebSphere MQ queue manager using either a bindings mode or a client mode connection. To use client mode with WebSphere MQ for z/OS, you need an additional product called the Client Attach Facility.
• You should configure the queues on the WebSphere MQ network as "shareable". This allows multiple server instances to get messages from the queues.

1. Create a WebSphere MQ server definition and configure the server properties.
2. Add the new WebSphere MQ server as a member of a bus so that messaging engines on the bus can access queues on the target WebSphere MQ installation.
3. Create a WebSphere MQ queue type destination for the new bus member and assign it to a WebSphere MQ queue.

4. Optional: Mediate the new destination using the WebSphere MQ queue as the mediation point.

Subtopics

• Create a WebSphere MQ server definition
  A WebSphere MQ server represents a WebSphere MQ queue manager or (for WebSphere MQ for z/OS) queue-sharing group. To create a WebSphere MQ server definition, we use the dmgr console to define the server connection and quality of service properties.
• Add a WebSphere MQ server as a member of a bus
  A WebSphere MQ server represents a WebSphere MQ queue manager or (for WebSphere MQ for z/OS) queue-sharing group. A WebSphere MQ server bus member is used as a bus member for assigning queue points and mediation points to WebSphere MQ queues.
• Create a queue-type destination and assigning it to a WebSphere MQ queue
  We can use the dmgr console to create a queue-type destination and assign it to a WebSphere MQ queue. Select the WebSphere MQ server to host the queue, then specify the WebSphere MQ queue to be hosted.
• Mediating a destination using a WebSphere MQ queue as the mediation point
  Mediate a destination using the dmgr console to specify a WebSphere MQ server bus member where the mediation point is to be assigned, and a WebSphere MQ queue to use as the mediation point where messages are stored. To mediate the destination using a service integration mediation, you must also specify a second bus member (not a WebSphere MQ server) to use as the mediation execution point and process the messages.

Related concepts:

Interoperation using a WebSphere MQ server

+

Search Tips   |   Advanced Search