Administer > Manage WebSphere Commerce features > Messaging system > WebSphere MQ > Configure WebSphere Application Server for use with WebSphere MQ

Create WebSphere MQ messaging provider queue destinations

Execute these steps to create the JMS queues required by the listener for WebSphere MQ.

The JMS queues map to the WebSphere MQ message queues you identified or created in Configure WebSphere MQ for use with WebSphere Commerce.

The JMS queues map to the WebSphere MQ message queues...

JMS queue	WebSphere MQ queue	Target Client
JMSSerialInboundQueue	hostname.inbounds	JMS
JMSParallelInboundQueue	hostname.inboundp	JMS
JMSInboundQueue	hostname.inbound	JMS
JMSOutboundQueue	hostname.outbound	MQ
JMSErrorQueue	hostname.error	MQ

...where hostname is the TCP/IP name of the machine running WebSphere MQ.

A JMS queue is created by creating a WebSphere MQ messaging provider queue destination in WebSphere Application Server.

The JMS queue names provided in the table are the default names used by WebSphere Commerce. If you have modified the JMS queue names using the WebSphere Commerce Configuration manager, change the JMS queue names to match the new queue names.

If you have used any customized JMS queue names or JMS queue connection factory names using the WebSphere Commerce Configuration Manager or editing the WebSphere Commerce configuration file, the JMS queue names must be added here to match the new queue names of WebSphere MQ.

The number of queues to define depends on the application with which WebSphere Commerce is integrated. These five queues are the minimum number of queues required for integration.

The queue name are case-sensitive. Ensure that you use the correct case for the queue names.

Procedure

1. In the WAS Administrative Console navigation tree, expand...

   Resources | JMS | Queues

2. Select the scope of the queue connection factory from the list.

   The node value should be WC_instance, where instance is the name of the WCS instance. IBM recommends to create it under the scope of...

   Node=WC_instance name_node, Server=server1

3. Click New | WebSphere MQ messaging provider | OK

4. Create new queues for each inbound queue in the table above...

   Option	Description
   Name	Name for the new WebSphere MQ messaging provider inbound queue destination as shown in the JMS Queue column. For example... JMSSerialInboundQueue
   JNDI name	JNDI name for the new WebSphere MQ messaging provider inbound queue destination. Use the same name as entered in the Name field. For example... JMSSerialInboundQueue
   Queue name	Queue name for the WebSphere MQ Queue as shown in the WebSphere MQ queue column. For example hostname.inbounds

5. Click OK.

6. Create new queues for each outbound and error queue in the table above...

   Option	Description
   Name	Name for the new WebSphere MQ messaging provider outbound or error queue destination as shown in the JMS Queue column. For example JMSOutboundQueue JMSErrorQueue
   JNDI name	JNDI name for the new WebSphere MQ messaging provider outbound or error queue destination. Use the same name as entered in the Name field. For example... JMSSerialInboundQueue JMSErrorQueue
   Queue name	Queue name for the WebSphere MQ Queue as shown in the WebSphere MQ queue column. For example... hostname.outbound hostname.error

   For each outbound and error queue, click Apply.

7. Click Advanced properties.

8. Clear the check box...

   Append RFH version 2 headers to messages sent to this destination

+

Search Tips   |   Advanced Search