JMS connectivity issues using IBM MQ Server

JMS connection for Product Master is set and configured by using IBM® MQ server.

Symptoms

Unable to connect to IBM MQ using Product Master. The queues, queue connection factory, and queue manage are defined in the IBM MQ server.

Resolving the problem

IBM MQ client jars are required to be included in Product Master class path. To configure this environment follow these steps:
  1. Ensure that the IBM MQ client is installed. The client should be of the same version as the IBM MQ server.
    Important: If the version of IBM MQ client and the IBM MQ Resource Adapter (RA) included with WebSphere Application Server do not match, the following error is generated:

    MQJCA1008: An incorrect version of the IBM MQ classes for JMS was found. Deployment failed during WebSphere Application server startup due to MQ version mismatch in between MQ files included in WebSphere Application server installation and MQ client installation

    To avoid this error, create the following symbolic links to load the JAR files directly into the class path from the resource adapter of the WebSphere Application Server.

    • ln -s $WAS_HOME/installedConnectors/wmq.jmsra.rar/com.ibm.mq.jar
      $TOP/jars/com.ibm.mq.jar
    • ln -s $WAS_HOME/installedConnectors/wmq.jmsra.rar/com.ibm.mq.jmqi.jar
      $TOP/jars/com.ibm.mq.jmqi.jar
    • ln -s $WAS_HOME/installedConnectors/wmq.jmsra.rar/com.ibm.mqjms.jar
      $TOP/jars/ com.ibm.mqjms.jar
  2. Stop all of the Product Master services by using the stop script:
    cd $TOP/bin/go
      ./abort_local.sh
        
  3. Edit the $TOP/bin/conf/env_settings.ini file to enable the inclusion of IBM MQ jars. The section details are:
    #MQ client section
    [mq]
    enabled=yes
    #home will default to /opt/mqm if not set
    home=<mq_home>
    If /opt/mqm is not the defined home for IBM MQ client installation, include the correct directory value in <mq_home>.
  4. Issue the $TOP/bin/configureEnv.sh file to reset the classpath variable. This includes the IBM MQ client jars in the class path.
  5. Start all of the Product Master services by using the start script:
        cd $TOP/bin/go
      ./start_local_rmlogs.sh
    Note: You can need to backup to the $TOP/logs folder.
    You should now be able to connect to IBM MQ server by using the JMS connection configured.