Setting up bindings mode

Install the IBM® MQ resource adapter for bindings mode connectivity to IBM MQ.

1. Locate the Unix System Services Components directory of the version of IBM MQ that you are going to connect to.
   For example, this directory might be called /usr/lpp/mqm/V9R1M0/. The directory contains a java/lib subdirectory, which contains a number of native libraries (.so files).

   Attention: If you are going to connect to multiple versions of queue manager, use the latest version.
2. Edit the server.xml file of the IBM z/OS Connect EE server.
   Add the following lines:

   1. 
      <variable name="wmqJmsClient.rar.location"  
                value="MQJAVA_LIB_DIR/jca/wmq.jmsra.rar"/>
      <wmqJmsClient nativeLibraryPath="MQJAVA_LIB_DIR"/>
      

      where MQJAVA_LIB_DIR is based off the directory located in step 1, for example, /usr/lpp/mqm/V9R1M0/java/lib.
   2. Save the changes.

   The first line tells IBM z/OS Connect EE where to locate the IBM MQ resource adapter.

   The second line tells the IBM MQ resource adapter where to locate the native libraries that are used for bindings connections to IBM MQ.

   See wmqJmsClient, and Deploying JMS applications to Liberty to use the IBM MQ messaging provider for more information.

3. Set up the STEPLIB of your server to include IBM MQ libraries.
   You must do this so that the native libraries located in step 1 can connect to the queue manager.

   Typically this involves editing the JCL, that starts your server, to include the following:

   
   //STEPLIB DD DSN=HLQ.SCSQAUTH,DISP=SHR
   // DD DSN=HLQ.SCSQANLE,DISP=SHR

   where HLQ is the high level qualifier of the data sets containing the IBM MQ installation.

   If you are going to connect to multiple versions of IBM MQ from the same server, use the data sets from the most recent version.