Obtaining the IBM MQ classes for JMS separately
The IBM® MQ classes for JMS are available within a self-extracting JAR file that you can download from Fix Central if you want to obtain just the IBM MQ classes for JMS JAR files, for deployment into a software management tool, or to use with stand-alone client applications.
Before you begin
Before you start this task, make sure that you have a Java runtime environment (JRE) installed on your machine and that the JRE has been added to the system path.
The Java installer that is used in this installation process does not require running as root or any specific user. The only requirement is that the user it is run as has access write to the directory that you want the files to go in.
About this task
Before IBM MQ 8.0, the IBM WebSphere® MQ classes for Java or IBM WebSphere MQ classes for JMS are not available as a separate download. For IBM WebSphere MQ 7.5 or earlier, if you are developing and running Java language applications that use either the IBM WebSphere MQ classes for Java or IBM WebSphere MQ classes for JMS, you need to install them either by performing a full server installation or by installing one of the client SupportPacs onto the system where the application is being developed and the system where the application will run. This installation installs many more files than the IBM WebSphere MQ classes for Java and IBM WebSphere MQ classes for JMS files.
- The IBM MQ classes for JMS
- The IBM MQ classes for Java
- The IBM MQ resource adapter
- The IBM MQ OSGi bundles
![[MQ 9.2.0.2 Mar 2021]](ng9202.gif)
From
IBM MQ 9.2.0 Fix Pack 2 for Long Term Support and
IBM MQ 9.2.2 for Continuous Delivery, the JMSAdmin tool is installed as part of the
self-extracting JAR file, which contains the following extra files that are related to the JMSAdmin tool:- The JMSAdmin.bat file used to start the JMSAdmin tool on Windows.
- The JMSAdmin script that is used to start the tool on Linux® and UNIX platforms.
- The sample configuration file for the JMSAdmin tool (JMSAdmin.config).
![[MQ 9.2.0.2 Mar 2021]](ng9202.gif)
A client that is installed using the self-extracting JAR file can
use the JMSAdmin tool to create JMS administered objects within a file system context
(.bindings file). The client can also look up and use these administered
objects.
![[MQ 9.2.0.2 Mar 2021]](ng9202.gif)
Previously, the self-extracting JAR file installed the
com.ibm.mq.allclient.jar file and all of its pre-requisite JAR files into the
wmq/JavaSE directory within the specified installation directory. From IBM MQ 9.2.0 Fix Pack 2 andIBM MQ 9.2.2, these files are
installed into the wmq/JavaSE/lib directory and the files related to the
JMSAdmin tool are installed into the wmq/JavaSE/bin directory.
When you run the executable JAR file, it displays the IBM MQ license agreement, which must be accepted. It asks for a directory in which to install the IBM MQ classes for Java, IBM MQ classes for JMS, the resource adapter, and OSGi bundles. If the selected installation directory does not exist, it is created and the program files are installed. However, if the directory exists, an error is reported and no files are installed.