Creating IBM MQ messaging provider queue destinations

Perform these steps to create the JMS queues required for the HCL Commerce listener for IBM MQ.

HCL Commerce Version 9.1.10.0 or laterNote: This task step is automated in deployments of HCL Commerce 9.1.10.0 and greater, and can be skipped. For more information, see Configuring WebSphere Application Server for use with IBM MQ.

About this task

The JMS queues map to the IBM MQ message queues you identified or created in Configuring IBM MQ for use with HCL Commerce. The JMS queues map to the IBM MQ message queues as follows:
JMS queue to IBM MQ queue mappings
JMS queue IBM 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 IBM MQ.

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

The JMS queue names provided in the table are the default names used by HCL Commerce. If you have modified the JMS queue names, the JMS queue names must be changed to match the new queue names.

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

Note: The number of queues to define depends on the application with which HCL Commerce is integrated. These five queues are the minimum number of queues required for integration.
Important: The queue name are case-sensitive. Ensure that you use the correct case for the queue names.

Procedure

  1. In the WebSphere Application Server Administrative Console navigation tree, expand Resources and select JMS then Queues.
  2. Select the scope of the queue connection factory from the list. The node value should be WC_instance_name, where instance_name is the name of the HCL Commerce instance. It is recommended to create it under the scope of Node=WC_instance name_node, Server=server1 level.
  3. Click New.
  4. Select IBM MQ messaging provider and click OK.
  5. Create new queues for each inbound queue in the table above as follows:
    OptionDescription
    Name Enter a name for the new IBM MQ messaging provider inbound queue destination as shown in the JMS Queue column. For example, JMSSerialInboundQueue.
    JNDI name Enter the JNDI name for the new IBM MQ messaging provider inbound queue destination. Use the same name as entered in the Name field. For example, JMSSerialInboundQueue.
    Queue name Enter the queue name for the IBM MQ Queue as shown in the IBM MQ queue column. For example, hostname.inbounds.
  6. Click OK.
  7. Create new queues for each outbound and error queue in the table above as follows:
    OptionDescription
    Name Enter a name for the new IBM MQ messaging provider outbound or error queue destination as shown in the JMS Queue column, for example, JMSOutboundQueue or JMSErrorQueue.
    JNDI name Enter the JNDI name for the new IBM MQ messaging provider outbound or error queue destination. Use the same name as entered in the Name field. For example, JMSSerialInboundQueue or JMSErrorQueue.
    Queue name Enter the queue name for the IBM MQ Queue as shown in the IBM MQ queue column. For example, hostname.outbound or hostname.error.
    For each outbound and error queue, click Apply.
    1. Click Advanced properties.
    2. Clear the Append RFH version 2 headers to messages sent to this destination check box.
    3. Click OK.
  8. When you have created all of the JMS queues:
    1. Click Save in the Administrative Console task bar.
    2. On the Save page, click Save.