Integrating IBM MQ with HCL Commerce

HCL Commerce provides a listener for IBM MQ for inbound requests, and an adapter for IBM MQ for outbound requests, to integrate back-end, and external systems with HCL Commerce.

You can set up the connection between HCL Commerce and IBM MQ in one of two connection modes:
Bindings mode
HCL Commerce is installed on the same machine as IBM MQ and it connects to IBM MQ through IBM MQ classes for Java by using the Java Messaging Server (JMS) API. Since communication is through inter-process bindings connection rather than through TCP/IP connection, bindings mode might provide better performance than client mode.
Client mode
HCL Commerce and IBM MQ connect by using TCP/IP. This mode must be used when HCL Commerce is installed on one machine and IBM MQ is installed on a separate machine. This mode requires that the IBM MQ client is installed on the HCL Commerce machine.
  • The listener supports IBM MQ Version 8.x and IBM MQ Version 9.x.

  • IBM MQ does not support machine names that contain spaces. If you install IBM MQ on a computer with a machine name that contains spaces, you cannot create any queue managers.
HCL Commerce Version or laterNote: Integration with IBM MQ was simplified in HCL Commerce

Specifically, the configuration of WebSphere Application Server is now automated, and much of the following manual configuration can be skipped. Instead, you must provide IBM MQ configuration information during deployment within your deployment configuration.

To specify your IBM MQ integration configuration for HCL Commerce deployments:

Before you begin

  • Install IBM MQ Version 9.x,
  • Create the JMS queue connection factory and JMS queues that map to the corresponding physical IBM MQ objects. Then, the HCL Commerce listener for IBM MQ can access IBM MQ entities through JMS.