|Skip Navigation Links|
|Exit Print View|
|Installing Third-Party JAR Files for Oracle Java CAPS Java CAPS Documentation|
This section includes information for installing and configuring the third-party JAR files for the WebSphere MQ Adapter.
The following steps are for running the Third-Party Installer with default settings. If you are running the Installer for specific instantiations of NetBeans or GlassFish (separately), you must specify each specifically when running ant (for example, ant install-glassfish or ant install-netbeans).
On Windows: webspheremq.thirdpartyfile=C:/Program Files/IBM/Websphere MQ/Java/lib/com.ibm.mq.jar
On Solaris: webspheremq.thirdpartyfile= /opt/IBM/webspheremq/Java/lib/opt/com.ibm.mq.jar
The WebSphere MQ Adapter requires the file com.ibm.mq.jar, a system specific JAR file, for normal operation. If you are using WebSphere MQ 6.x, the adapter also requires the com.ibm.mqetclient.jar file for XA transactions in Client mode and for deploying EAR files to a WebLogic application server.
If you are using WebSphere MQ 7.x and JMS JCA, you also need the following files:
If you are using WebSphere MQ 7.x and the WebSphere MQ Adapter, you need the following additional files:
The files must be copied from the MQ server that you are running against. Depending on the mode of operation, the WebSphere MQ Library utilized by the adapter requires modules specific to the operating system. If a WebSphere MQ Adapter project is deployed to a different MQ server running on a different operating system, the files in the application server must be replaced with the files from that specific MQ server to ensure that the JAR file remains corresponds to he operation system of the current MQ server.
If you are using WebSphere MQ 6.x, the WebSphere MQ Adapter requires the com.ibm.mqetclient.jar file for XA transactions in Client mode and for deploying EAR files to a WebLogic application server. The JAR file is installed as part of the WebSphere MQ Extended Transaction client installation. Both the com.ibm.mq.jar and the com.ibm.mqetclient.jar must be added to the Integration Server classpath to run XA transactions in Client mode.