Create a queue-type destination and assigning it to a WebSphere MQ queue
We can use the 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.
Get the name of the WebSphere MQ queue from the administrator, and ensure that the following configuration is established:
- The WebSphere MQ server is added as a member of a bus
- The WebSphere MQ queue for the queue point exists
- The WebSphere MQ administrator has set the queue attributes to "shareable"
A shareable queue can be accessed by more than one service integration application.
Decide which method to use to configure these resources. We can create a bus destination using the console as described in this task, or using the createSIBDestinations command.
After we have added a WebSphere MQ server as a bus member, we can create a queue-type destination on the bus member that uses a WebSphere MQ queue as a queue point. This configuration enables service integration applications to send messages to and receive messages from that queue.
- Start the console.
- Navigate to the list of destinations for the appropriate bus.
Click Service integration -> Buses -> bus_name -> [Destination resources] Destinations.
The Destinations [Collection] form is displayed.
- Click New. The "Create a new destination" panel is displayed.
- Select Queue as the destination type, then click Next. The "Create a new queue" wizard is displayed.
- Set the queue attributes. Enter the name we want WebSphere Application Server to use to refer to the associated WebSphere MQ queue, and (optionally) a description of the queue.
- Assign the queue to the bus member that is to store and process the messages for the queue.
Select a WebSphere MQ server bus member from the list of available bus members.
- Set the WebSphere MQ queue point attributes:
- 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.
- Specify a WebSphere MQ queue name.
Select a queue name from the filtered list. If the list does not include the queue we 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 we want, and that it is configured as you intend. If the queue is not found, these read-only fields are removed from view.
- Specify the reliability levels that you require when inbound nonpersistent and inbound persistent WebSphere MQ messages are converted to service integration format messages.
Applications receive messages direct from the specified WebSphere MQ queue, so in general the reliability level for a message is of no interest to the receiver 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].
- Specify whether we 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 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 consumer is a WebSphere MQ MQI application that does not expect an MQRFH2 header, do not select this option.
- Click Next.
- Click Finish to confirm queue creation.
Results
You have created a queue-type destination with a WebSphere MQ queue point.
What to do next
We are now ready to (optionally) mediate the new destination using the WebSphere MQ queue as the mediation point.
Related concepts
WebSphere MQ queue points and mediation points WebSphere MQ server and mediated exchange scenarios Mediations
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 WebSphere MQ queue points [Collection] WebSphere MQ queue points [Settings]