You can configure WebSphere Application Server for use with IBM MQ by determining the maximum number of ManagedConnections for the JCA-JMS connector, creating a IBM MQ messaging provider queue connection factory, creating IBM MQ messaging provider queue destinations, and configuring advanced properties for JMSQueueConnectionFactory and JMSOutboundQueue.
For runtime environments, you might want to leverage Run Engine commands to configure WebSphere Application Server for use with IBM MQ. For more information, see Run Engine commands. You can use the following Run Engine commands in your Transaction server container:
The following steps explain how to configure the connection through the WebSphere Application Server Administration console.
Setting the MQ_INSTALL_ROOT environment variable
Set the MQ_INSTALL_ROOT environment variable value in the WebSphere Application Server Administrative Console to direct WebSphere Application Server to where IBM MQ is installed.
Enabling the ActivitySession service
Enable the ActivitySession service.
Determining the maximum number of connections allowed for the Adapter for IBM MQ
To determine the maximum number of ManagedConnections for the JCA-JMS connector, you must perform these steps on the WebSphere Commerce machine.
Creating an IBM MQ messaging provider queue connection factory
To create an IBM MQ messaging provider queue connection factory, follow this procedure on the Transaction Server.
Creating IBM MQ messaging provider queue destinations
Perform these steps to create the JMS queues required for the WebSphere Commerce listener for IBM MQ.
(Optional) Defining multiple threads for serial and parallel listeners
By default, WebSphere Commerce configuration provides two inbound listeners: one serial listener and one parallel listener. To use multiple inbound queues, you must define multiple inbound listeners for IBM MQ.