Configuring WebSphere MQ for use with WebSphere Commerce

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

Procedure

  1. Add the non-root WebSphere Commerce user ID to the mqm user group. The non-root WebSphere Commerce user ID was created before installing WebSphere Commerce.
  2. Windows Add the Windows user ID used to start WebSphere Commerce to the mqm group.
  3. Identify the Queue Manager that WebSphere Commerce will use. This can be an existing Queue Manager or a newly created Queue Manager. The choice of the Queue Manager depends on you integration configuration.

    For instructions on creating a Queue Manager, refer to the WebSphere MQ documentation.

    The instructions in this chapter assume that the Queue Manager name is hostname.qm, where hostname is the host name (without a domain) for the machine running WebSphere MQ.

    Take note of both the Queue Manager name and the port number used by the Queue Manager listener. This information is used in later steps.
    Important:

    Ensure that the operating system user ID used to start WebSphere Commerce is also authorized for the Queue Manager. For instructions on authorizing a user ID for a WebSphere MQ Queue Manager, refer to the WebSphere MQ documentation.

    Also, The Queue Manager name is case-sensitive. Ensure that you use the correct case for the Queue Manager name in later steps.

  4. Identify the local message queues for the Queue Manager. These can be existing message queues or newly created queues.

    For instructions on creating queues, refer to the WebSphere MQ documentation.

    The instructions in this chapter 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 WebSphere 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 will be processed in parallel manner.
    hostname.inbounds Any message arrive at this queue will be 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 running WebSphere MQ.
    Take note of the names of the message queues you identified or created. This information is used in later steps.
    Important:

    Ensure that the operating system user ID used to start WebSphere Commerce is also authorized for the message queues. For instructions on authorizing a user ID for a WebSphere MQ message queue, refer to the WebSphere MQ documentation.

    Also, queue names are case-sensitive. Ensure that you use the correct case for the queue names 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.
  5. (Client mode only) Create a listener port for the Queue Manager you created.
  6. After completing the steps to configure WebSphere MQ, continue with the instructions in Configuring WebSphere Application Server for use with WebSphere MQ.