Installing Third-Party JAR Files for the WebSphere MQ Adapter

This section includes information for installing and configuring the third-party JAR files for the WebSphere MQ Adapter.

To Install the JAR Files for WebSphere MQ

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).

1. Install the Third-Party Library Installer and set up the environment, as described in Setting Up the Third-Party Library Installer.
2. Navigate to the location of the Third-Party Library Installer.
3. Customize the build.properties file with at least the following changes. For more information on build properties, see To Configure the Build File.
   1. Remove all values from the product.name property except webspheremq.
   2. Modify the webspheremq.thirdpartyfile property by adding the full path to com.ibm.mq.jar.

      For example:

      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

4. Shutdown the instances of Java CAPS NetBeans and GlassFish.
5. Invoke the Third Party Installer by typing ant.
6. Restart the Java CAPS NetBeans instance.

WebSphere MQ Adapter Required JAR Files

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:

• com.ibm.mqjms.jar

• dhbcore.jar

• connector.jar

• com.ibm.mq.jmqi.com

If you are using WebSphere MQ 7.x and the WebSphere MQ Adapter, you need the following additional files:

• dhbcore.jar

• com.ibm.mq.jmqi.com

• com.ibm.mq.commonservices.jar

• com.ibm.mq.headers.jar

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.

To Install the System-Specific JAR Files

1. Navigate to WebSphereMQ_Home\java\lib.
2. Copy the required JAR files (listed above).
3. Paste the JAR files to the JavaCAPS_Home\appserver\lib directory.

Adding the required JAR files to the Integration Server Classpath for XA Transactions

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.

To add the required JAR files to the IS Classpath

1. Note the location of the com.ibm.mq.jar and the com.ibm.mqclient.jar files on your logical host.
2. Open the Integration Server Administration tool. Add the absolute path for both JAR files to the IS Administration tool's Classpath Prefix field.
3. Save your work.