Configure IBM MQ for use with WebSphere Commerce

WebSphere Commerce requires a set of information to be defined in IBM MQ for WebSphere Commerce to work with IBM MQ. These include a queue manager and a set of queues.

Before beginning

• (AIX) (Linux) Add root user (root) to the mqm user group.

• (Developer) Add the Windows user ID used to start WebSphere Commerce development environment to the mqm group.

• Ensure that the operating system user ID used to start WebSphere Commerce is also authorized for the queue manager.

• Queue manager names and queue names are case-sensitive. Ensure using the correct case.

• For instructions on creating a queue manager or queue, see the IBM MQ Version 8 documentation.

Procedure

1. Identify the queue manager for WebSphere Commerce to use. The queue can be on an existing queue manager or a newly created queue manager. The choice of the queue manager depends on your integration configuration.

   These instructions assume that the queue manager name is hostname.qm, where hostname is the host name (without a domain) for the machine that is running IBM MQ.

   Take note of both the queue manager host name and the port number used by the queue manager listener. This information is used in later steps.

2. Identify the local message queues for the queue manager. These queues can be existing message queues or newly created queues. These instructions assume that the following local message queues are created:

   Queue	Description
   hostname.error	Default error queue. Collects erratic inbound messages.
   hostname.inbound	Used by SendReceiveImmediate mode of the adapter for IBM MQ. It is where the reply and response messages from the backend system should go. WebSphere Commerce can optionally pick reply and response messages based on an outgoing request to a backend system.
   hostname.inboundp	Any message arrive at this queue is processed in parallel manner.
   hostname.inbounds	Any message arrive at this queue is processed in serial manner based on the message delivery sequence option of the queue.
   hostname.outbound	Used for WebSphere Commerce initiated outbound messages and reply messages from WebSphere Commerce.

   Where hostname is the TCP/IP name of the machine that is running IBM MQ.

   Take note of the names of the message queues you identified or created. This information is used in later steps.

   Note: 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.

3. (Client mode only) Create a listener port for any queue manager created.

Next topic: Configure WebSphere Application Server for use with IBM MQ