Configuring IBM MQ for use with HCL Commerce

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

Before you begin

  • AIXLinuxAdd root user (root) to the mqm user group.
  • HCL Commerce Developer Add the Windows user ID used to start HCL Commerce Developer to the mqm group.
  • Ensure that the operating system user ID used to start HCL Commerce is also authorized for the queue manager.
  • Queue manager names and queue names are case-sensitive. Ensure that you use 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 HCL 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 that is 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. HCL 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 HCL Commerce initiated outbound messages and reply messages from HCL 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 HCL Commerce is integrated. These five queues are the minimum number of queues that are required for integration.
  3. (Client mode only) Create a listener port for any queue manager that you create.