Installation of the WebSphere MQ resource adapter
The WebSphere MQ resource adapter is supplied as a resource archive (RAR) file called wmq.jmsra.rar. This file is installed with WebSphere MQ Java in the directory shown in Table 1.
The RAR file contains the following Java archive (JAR) files:
The directory containing wmq.jmsra.rar for each platform Platform Directory AIX /usr/mqm/java/lib/jca HP-UX, Linux, and Solaris /opt/mqm/java/lib/jca i5/OS /QIBM/ProdData/mqm/java/lib/jca Windows install_dir\Java\lib\jca install_dir is the directory where you installed the WebSphere MQ server or WebSphere MQ client. The default directory is C:\\IBM\WebSphere MQ, but you might have chosen a different directory.
- com.ibm.mq.jar, which contains WebSphere MQ base Java
- com.ibm.mqjms.jar, which contains WebSphere MQ JMS
- mqconnector.jar, which contains the WebSphere MQ implementation of the JCA interfaces
- dhbcore.jar, which is an additional library required by WebSphere MQ JMS
You must install the WebSphere MQ resource adapter RAR file in your application server, but the way you do this depends on the application server. See the documentation for your application server for information about how to install a resource adapter RAR file.
For non-transacted client connections, no other files are required. For bindings connections, WebSphere MQ Java must be installed. On UNIX systems, also ensure that the Java Native Interface (JNI) libraries are in the system path. See Table 1 for the location of the WebSphere MQ Java libraries, which include the JNI libraries. On Windows, the WebSphere MQ Java libraries are added to the system path automatically during installation of WebSphere MQ Java.
Distributed transactions are supported by default in bindings mode but, in client mode, they are supported only in the following cases:
- If you are using WebSphere Application Server, V6.0
- For any other application server, if the extended transactional client JAR file, com.ibm.mqetclient.jar, is in the class path
Table 2 summarizes the support for non-transacted and transacted connections. For an explanation of client and bindings modes, see Connection options.
Support for non-transacted and transacted connections Type of connection Non-transacted connections Transacted connections Client mode Supported by default Supported if you are using WebSphere Application Server, V6.0 or if com.ibm.mqetclient.jar is in the class path Bindings mode Supported if the JNI libraries are in the system path Supported if the JNI libraries are in the system path The WebSphere MQ resource adapter and the version of WebSphere MQ Java used by the resource adapter must be at the same release level.
uj40060_