Using the Listener for IBM MQ

The Listener for IBM MQ can be used as an alternative interface to the HCL Commerce system and functionality. The Listener for IBM MQ not only processes inbound requests, but can provide a reply to the request. Any command that formulates a response can be configured to provide a response through the Listener for IBM MQ.

About this task

When an inbound message is received by the Listener for IBM MQ it is mapped to a command and that command is called with the parameters specified in the inbound message. If a response is to be generated from this inbound request, an entry in the Struts configuration file is needed. If a response is generated by the command, that response is placed on the outbound queue of the Parallel or Serial Connector. The queue that is used depends on which connector received the inbound request.

If an error with the inbound request occurs, the message generating the error is placed on the error queue. To generate an error response to the outbound queue, another entry is needed in the Struts configuration file. This entry maps the error response using the proper device format.

To configure the Listener for IBM MQ component to provide responses for inbound messages:


  1. Verify that the HCL Commerce configuration file includes an Outbound Queue for Parallel and Serial Listeners for IBM MQ by ensuring that syntax similar to the following is included for the Inbound Parallel and Serial Connector:
    <EditableProperty Admin="outQueue" 
          value="JMSOutboundQueue" />

    The JMS queue object, JMSOutboundQueue, specifies the location of the reply message queue. You can define a different names for the Serial and Parallel Listener outbound queues. If you define new names, you must map the names to the MQ queue object by using the WebSphere Application Server Administration Console. See Creating IBM MQ messaging provider queue destinations for more information.

  2. Add an entry in the Struts configuration file to define the response needed for the inbound request. This step is required both for existing HCL Commerce commands and for new commands. Use the following values:
    The same value as for regular HTTP responses
    docname=JSP filename
    For XML inbound messages
    For legacy inbound messages