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

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.

Decide which method to use to configure these resources. We can mediate a destination using the dmgr console as described in this task, or using the mediateSIBDestination command.

Before performing this task, ensure the following resources exist:

• The mediation to apply to the destination.
• The WebSphere MQ server bus member where the mediation point is to be assigned.
• The WebSphere MQ queue to use as the mediation point, with the queue attributes set to shareable.

• For a service integration mediation, a second bus member (not a WebSphere MQ server bus member) to use as the mediation execution point where the mediation code runs.

The queue manager on the WebSphere MQ network does not have to be available when we complete this task, but the destination is not usable until the queue manager becomes available. We can mediate a destination with a WebSphere MQ mediation point. This ensures that messages arriving at the designated WebSphere MQ queue are mediated. In this scenario, the mediated messages are delivered to the queue point, or to another destination that is determined by the default forward routing path destination, or by the mediation code. The mediation can be hosted by service integration, or hosted by WebSphere MQ.

1. Start the dmgr console.
2. cd list of destinations for the appropriate bus. Click Service integration -> Buses -> bus_name -> [Destination resources] Destinations.

3. Select the check box beside the destination to mediate, then click Mediate. The Mediation wizard is displayed.
4. Step 1: Select mediation.

   To mediate the destination using a mediation hosted by service integration:

   1. Select The mediation to apply to this destination.

   2. From the drop-down list, select the mediation.

   3. Click Next.

   To mediate the destination using a WebSphere MQ program (for example, a WebSphere MQ flow):

   1. Select Externally mediated.

   2. Click Next.

5. Step 2: Assign the mediation to a bus member.

   When a mediation is assigned to a WebSphere MQ server bus member, you need a separate bus member not a WebSphere MQ server to act as the mediation execution point and process the messages.

   1. From the drop-down list, select the WebSphere MQ server bus member where the mediation point is to be assigned.

   2. Optional: If we are using a service integration mediation, select the bus member where the mediation is to run.

      For a mediation hosted by service integration, select a bus member from the list box that is labeled Select a bus member where the mediation will run. If we are using an external mediation, by definition it does not run in a bus member.

   3. Click Next.

6. Optional: If the mediation point is a WebSphere MQ queue, set the WebSphere MQ mediation point attributes.

   This step is only displayed if you assigned the mediation point to a WebSphere MQ queue in the previous step.

   1. Specify a value in the WebSphere MQ queue name filter field, then click Go.

      The wizard automatically discovers available WebSphere MQ queues. However, some WebSphere MQ topologies have many thousands of queues defined to a queue manager. Use this filter to limit the number of queues listed.

      The default filter value is an asterisk (*). If this value (or no value) is set then all queues, or all queues of a specific type (based on any queue type custom property set), are listed. Any other value specified must meet the following criteria:

      • It must contain between 1 and 48 characters.
      • It must conform to the WebSphere MQ queue naming rules (see the Rules for naming WebSphere MQ objects topic in the WebSphere MQ information center).

      We can also use the wildcard character (*) with other text. For example, if you enter a value of PAYROLL*, then all available queues with names that start with PAYROLL are displayed.

   2. Specify a WebSphere MQ queue name.

      Select a queue name from the filtered list. If the list does not include the queue you want, select the last entry in the list labeled other, please specify. A text entry box is displayed next to the drop-down list. Type the queue name into the text entry box.

      If the queue is found on the remote WebSphere MQ system, the properties of the queue as defined within WebSphere MQ are displayed as read-only fields. This should help you to confirm that we have found the queue you want, and that it is configured as you intend. If the queue is not found, these read-only fields are removed from view.

   3. Specify the reliability levels that you require when inbound nonpersistent and inbound persistent WebSphere MQ messages are converted to service integration format messages.

      Mediations receive messages direct from the specified WebSphere MQ queue, so in general the reliability level for a message is of no interest to the mediation because the message has already been delivered successfully. However, the message is converted to a service integration format message (and typically to a JMS format service integration message) as it is received, and this option specifies the reliability level for the service integration format message. For information about the available reliability levels, see WebSphere MQ queue points [Settings].

   4. Specify whether you want WebSphere MQ to include an MQRFH2 message header when sending messages to the queue.

      The MQRFH2 header stores service integration messaging information that does not have a corresponding WebSphere MQ message header field. When a message is sent to the destination, service integration instructs WebSphere MQ to write the message to the queue. This option specifies whether service integration instructs WebSphere MQ to write the message with an MQRFH2 header.

      If the consumer of the message (in this case, the mediation) is a JMS application running in WebSphere MQ or service integration, or a WebSphere MQ XMS application, or a WebSphere MQ MQI application that expects an MQRFH2 header, select this option. If the mediation is a WebSphere MQ MQI application that does not expect an MQRFH2 header, do not select this option.

   5. Click Next.

7. Check the summary of your selections, then click Finish to confirm mediation of the destination.

Results

You have mediated a destination using a WebSphere MQ queue as the mediation point.

Related concepts:

WebSphere MQ queue points and mediation points
WebSphere MQ server and mediated exchange scenarios
Mediations

Reference:

createSIBDestination command
createSIBDestinations command
mediateSIBDestination command
unmediateSIBDestination command

Related information:

A practical introduction to message mediation -- Part 1

A practical introduction to message mediation -- Part 3

A practical introduction to message mediation -- Part 4

A practical introduction to message mediation -- Part 5
Mediation execution points [Collection]
Mediation points [Settings]
WebSphere MQ mediation points [Collection]
WebSphere MQ mediation points [Settings]
Mediation points [Collection]
Mediation points [Collection]

+

Search Tips   |   Advanced Search