What is installed

The latest versions of both WebSphere MQ base Java and WebSphere MQ JMS (together known as WebSphere MQ Java) are installed with WebSphere MQ. You may need to override default installation options to make sure this is done.

Refer to the following books for more information about installing WebSphere MQ:

WebSphere MQ for AIX, V5.3 Quick Beginnings for AIX

WebSphere MQ for HP-UX, V5.3 Quick Beginnings for HP-UX

WebSphere MQ for iSeries V5.3 Quick Beginnings for OS/400

WebSphere MQ for Linux for Intel and Linux for zSeries, V5.3 Quick Beginnings for Linux

WebSphere MQ for Solaris, V5.3 Quick Beginnings for Solaris

WebSphere MQ for Windows, V5.3 Quick Beginnings for Windows systems

WebSphere MQ for z/OS System Setup Guide for z/OS

WebSphere MQ base Java is contained in the following Java .jar files:

com.ibm.mq.jar: This code includes support for all the connection options.
com.ibm.mqbind.jar: This code supports only the bindings connection and is not supplied or supported on all platforms. We recommend that you do not use it in any new applications.

WebSphere MQ JMS is contained in the following Java .jar file:

com.ibm.mqjms.jar

The following Java libraries from Sun Microsystems are redistributed with the WebSphere MQ JMS product:

connector.jar: Version 1.0
fscontext.jar: Early Access 4 Release
jms.jar: Version 1.0.2
jndi.jar: Version 1.1.2 (except for z/OS & OS/390)
ldap.jar: Version 1.0.3 (except for z/OS & OS/390)
providerutil.jar: Version 1.0

When installation is complete, files and samples are installed in the locations shown in Installation directories.

After installation, you must update your environment variables, as shown in Environment variables.

Note:: Take care if you install the product, then subsequently install or reinstall a version of SupportPac^(TM) MA88. This may cause your WebSphere MQ Java support to revert to an earlier level.

Installation directories

The WebSphere MQ Java V5.3 files are installed in the directories shown in Table 2.

Table 2. Product installation directories

Platform	Directory
AIX	/usr/mqm/java/
z/OS & OS/390	install_dir/mqm/java/
iSeries & AS/400^(R)	/QIBM/ProdData/mqm/java/
HP-UX and Sun Solaris	/opt/mqm/java/
Linux	install_dir/mqm/java/
Windows systems	\Program Files\IBM\WebSphere MQ\java
Note: install_dir is the directory in which you installed the product. On Linux, this is likely to be /opt and on z/OS & OS/390 it is likely to be /usr/lpp.

Some sample programs, such as the Installation Verification Programs (IVP), are supplied. Table 3 lists the directory path to these on different platforms. WebSphere MQ base Java samples are within a subdirectory base and WebSphere MQ JMS samples are within a subdirectory jms.

Table 3. Samples directories

Platform	Directory
AIX	/usr/mqm/samp/java/
z/OS & OS/390	install_dir/mqm/java/samples/
iSeries & AS/400	/QIBM/ProdData/mqm/java/samples/
HP-UX and Sun Solaris	/opt/mqm/samp/java/
Linux	install_dir/mqm/samp/java/
Windows systems	\Program Files\IBM\WebSphere MQ\tools\Java\
Note: install_dir is the directory in which you installed the product. On Linux, this is likely to be /opt and on z/OS & OS/390 it is likely to be /usr/lpp.

Environment variables

After installation, you must update your CLASSPATH environment variable to include the WebSphere MQ base Java code and samples directories. Table 4 shows typical CLASSPATH settings for the various platforms.

WebSphere MQ Java uses other environment variables. Some are platform dependent and are listed in Table 5. Two are common across platforms, MQ_JAVA_INSTALL_PATH and MQ_JAVA_DATA_PATH. On Windows systems, these variables are automatically set by the installation program, but on other platforms you need to set them manually to complete installation.

MQ_JAVA_INSTALL_PATH points to the product installation directory, as shown in Table 2. MQ_JAVA_DATA_PATH points to the root directory for logging and tracing, and is included so that you can use the same directory for WebSphere MQ Java and the base WebSphere MQ product.

Table 4. Sample CLASSPATH statements for the product

Platform	Sample CLASSPATH
AIX	CLASSPATH=/usr/mqm/java/lib/com.ibm.mq.jar: /usr/mqm/java/lib/connector.jar: /usr/mqm/java/lib: /usr/mqm/samp/java/base:
HP-UX and Sun Solaris	CLASSPATH=/opt/mqm/java/lib/com.ibm.mq.jar: /opt/mqm/java/lib/connector.jar: /opt/mqm/java/lib: /opt/mqm/samp/java/base:
Windows systems	CLASSPATH=mq_root_dir^(CPDNL1)\java\lib\com.ibm.mq.jar; mq_root_dir\java\lib\connector.jar; mq_root_dir\java\lib\; mq_root_dir\tools\java\base\;
z/OS & OS/390	CLASSPATH=install_dir^(CPDNL2)/mqm/java/lib/com.ibm.mq.jar: install_dir/mqm/java/lib/connector.jar: install_dir/mqm/java/lib: install_dir/mqm/java/samples/base:
iSeries & AS/400	CLASSPATH=/QIBM/ProdData/mqm/java/lib/com.ibm.mq.jar: /QIBM/ProdData/mqm/java/lib/connector.jar: /QIBM/ProdData/mqm/java/lib: /QIBM/ProdData/mqm/java/samples/base:
Linux	CLASSPATH=install_dir^(CPDNL2)/mqm/java/lib/com.ibm.mq.jar: install_dir/mqm/java/lib/connector.jar: install_dir/mqm/java/lib: install_dir/mqm/samp/java/base:
Notes: mq_root_dir stands here for the directory used to install WebSphere MQ on Windows systems. This is normally `C:\Program Files\IBM\WebSphere MQ\`. install_dir is the directory in which you installed the product

To use WebSphere MQ JMS, you must include additional jar files in the classpath. These are listed in Post installation setup.

If there are existing applications with a dependency on the deprecated bindings package com.ibm.mqbind, you must also add the file com.ibm.mqbind.jar to your classpath.

You must update additional environment variables on some platforms, as shown in Table 5.

Table 5. Environment variables for the product

Platform	Environment variable
AIX	LD_LIBRARY_PATH=/usr/mqm/java/lib
HP-UX	SHLIB_PATH=/opt/mqm/java/lib
Sun Solaris	LD_LIBRARY_PATH=/opt/mqm/java/lib
Windows systems	PATH=install_dir\lib
z/OS & OS/390	LIBPATH=install_dir/mqm/java/lib
Linux	LD_LIBRARY_PATH=install_dir/mqm/java/lib
Note: install_dir is the installation directory for the product

Notes:

To use WebSphere MQ Bindings for Java on OS/400, ensure that the library QMQMJAVA is in your library list.
Ensure that you append the WebSphere MQ variables and do not overwrite any of the existing system environment variables. If you overwrite existing system environment variables, the application might fail during compilation or at runtime.