Administer > Manage WebSphere Commerce features > Messaging system
WebSphere MQ
Overview
In terms of WebSphere MQ, WebSphere Commerce provides...
- Listener for inbound requests
- Adapter for outbound requests
The listener supports WebSphere MQ v6.0, v7.0 and higher, and includes...
- WebSphere MQ classes for Java
- WebSphere MQ classes for Java Message Service
To connect to a remote MQ v6.0 server, use the WebSphere MQ v6.0 client. To connect to a remote WebSphere MQ v7.0 server, use the WebSphere MQ v7.0 client.
To enable the Commerce listener to access WebSphere MQ entities, such as queue managers and queues, map Commerce to physical WebSphere MQ objects by creating...
Connections to MQ come in two modes...
Bindings mode Commerce is installed on the same machine as MQ and connects using MQ classes for Java using the JMS API. Performance might be better than client mode because communication is through inter-process bindings connection rather than through TCP/IP connections.
Client mode Commerce and MQ connect using TCP/IP. Required when Commerce is installed on one machine and MQ is installed on a separate machine.
To use this mode, the MQ client needs to be installed on the WebSphere Commerce machine.
The use of the message engine or WAS v5 default messaging is not supported by the WebSphere Commerce adapter for MQ.
Use WebSphere MQ with WebSphere Commerce
- If required, install WebSphere MQ
- Identify existing MQ objects or create new MQ objects.
- Create the JMS queue connection factory and JMS queues.
- Enable the commerce listener for MQ
- Test the WebSphere MQ configuration
- Define multiple threads for serial and parallel listeners (Optional)