IBM MQ classes for Java redistributable JAR files

The relocatable JAR files can be moved to systems that need to run IBM MQ classes for Java.

Important:

• Apart from the relocatable JAR files described in Relocatable JAR files, copying the IBM MQ classes for Java JAR files or native libraries to other machines, or to a different location on a machine where the IBM MQ classes for Java have been installed, is not supported.
• To avoid classloader conflicts, it is not recommended to bundle the relocatable JAR files within multiple applications inside the same Java runtime. In this scenario, consider making the IBM MQ relocatable JAR files available on the Java runtime's classpath.
• Do not include the relocatable JAR files within applications deployed into Java EE application servers, such as WebSphere Application Server. In these environments, the IBM MQ resource adapter should be deployed and used instead, as this contains the IBM MQ classes for Java. Note that WebSphere Application Server embeds the IBM MQ resource adapter, so there is no need to deploy it manually into this environment. In addition to this, the IBM MQ classes for Java are not supported in WebSphere Liberty. For more information, see Liberty and the IBM MQ resource adapter.
• If we are bundling the relocatable JAR files within the applications, ensure that we include all prerequisite JAR files as described in Relocatable JAR files. We should also ensure that we have appropriate procedures to update the bundled JAR files as part of application maintenance, to ensure that the IBM MQ classes for Java remain current and known issues are re-mediated.

Relocatable JAR files

Within an enterprise, the following files can be moved to systems that need to run IBM MQ classes for Java applications:

• com.ibm.mq.allclient.jar
• com.ibm.mq.traceControl.jar
• bcpkix-jdk15on.jar
• bcprov-jdk15on.jar
• org.json.jar

The Bouncy Castle security provider and CMS support JAR files, bcpkix-jdk15on.jar and bcprov-jdk15on.jar, are required. For more information, see Support for non-IBM JREs.

The org.json.jar file is required if the IBM MQ classes for Java application uses a CCDT in JSON format.

The file com.ibm.mq.allclient.jar contains the IBM MQ classes for JMS, the IBM MQ classes for Java, and the PCF and Headers Classes. If you move this file to a new location, make sure that you take steps to keep this new location maintained with new IBM MQ Fix Packs. Also, make sure that the use of this file is made known to IBM Support if we are getting an interim fix.

To determine the version of the com.ibm.mq.allclient.jar file, use the command:

java -jar com.ibm.mq.allclient.jar

The following example shows some sample output from this command:

C:\Program Files\IBM\MQ_1\java\lib>java -jar com.ibm.mq.allclient.jar
Name:       Java Message Service Client
Version:    9.0.0.0
Level:      p000-L140428.1
Build Type: Production
Location:   file:/C:/Program Files/IBM/MQ_1/java/lib/com.ibm.mq.allclient.jar

Name:       WebSphere MQ classes for Java Message Service
Version:    9.0.0.0
Level:      p000-L140428.1
Build Type: Production
Location:   file:/C:/Program Files/IBM/MQ_1/java/lib/com.ibm.mq.allclient.jar

Name:       WebSphere MQ JMS Provider
Version:    9.0.0.0
Level:      p000-L140428.1 mqjbnd=p000-L140428.1
Build Type: Production
Location:   file:/C:/Program Files/IBM/MQ_1/java/lib/com.ibm.mq.allclient.jar

Name:       Common Services for Java Platform, Standard Edition
Version:    9.0.0.0
Level:      p000-L140428.1
Build Type: Production
Location:   file:/C:/Program Files/IBM/MQ_1/java/lib/com.ibm.mq.allclient.jar

The com.ibm.mq.traceControl.jar file is used to dynamically control trace for IBM MQ classes for JMS applications. For more information, see Control trace in a running process by using IBM MQ classes for Java and IBM MQ classes for JMS.

Parent topic: What is installed for IBM MQ classes for Java