IBM WebSphere MQ classes for JMS and software management tools

Software management tools such as Apache Maven can be used with the IBM® WebSphere® MQ classes for JMS.

Many large development organizations use these tools to centrally manage repositories of third-party libraries.

The IBM WebSphere MQ classes for JMS are composed of a number of JAR files. When you are developing Java language applications by using this API, an installation of an IBM WebSphere MQ Server, Client, or Client SupportPac is required on the machine where the application is being developed.

If you want to use such a tool and add the JAR files that make up the IBM WebSphere MQ classes for JMS to a centrally managed repository, the following points must be observed:
  • A repository or container must be made available only to developers within your organization. Any distribution outside of the organization is not permitted.
  • The repository needs to contain a complete and consistent set of JAR files from a single IBM WebSphere MQ release or Fix Pack.
  • You are responsible for updating the repository with any maintenance provided by IBM Support.
For IBM WebSphere MQ Version 7.5, the following JAR files need to be installed into the repository:
  • com.ibm.mqjms.jar.
  • com.ibm.mq.jar
  • com.ibm.mq.jmqi.jar
  • com.ibm.mq.pcf.jar
  • com.ibm.mq.headers.jar
  • CL3Export.jar is required if you are using the IBM WebSphere MQ classes for JMS.
  • CL3Nonexport.jar is required if you are using the IBM WebSphere MQ classes for JMS.
  • jndi.jar is required if you are using the IBM WebSphere MQ classes for JMS.
  • ldap.jar is required if you are using the IBM WebSphere MQ classes for JMS.
  • rmm.jar is required if you are using the IBM WebSphere MQ classes for JMS.
  • dhbcore.jar is required if you are using the IBM WebSphere MQ classes for JMS.
  • jms.jar is required if you are using the IBM WebSphere MQ classes for JMS.
  • fscontext.jar is required if you are using the IBM WebSphere MQ classes for JMS and accessing JMS administered objects that are stored in a file system JNDI context.
  • providerutil.jar if you are using the IBM WebSphere MQ classes for JMS and accessing JMS administered objects that are stored in a file system JNDI context.