IBM MQ classes for JMS and software management tools

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

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

The IBM MQ classes for JMS and IBM MQ classes for Jakarta Messaging are composed of a number of JAR files. When you are developing Java language applications by using this API, an installation of either an IBM MQ Server, IBM MQ Client, or IBM MQ 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 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 MQ release or Fix Pack.
You are responsible for updating the repository with any maintenance provided by IBM Support.

The following JAR files need to be installed into the repository:

com.ibm.mq.allclient.jar and jms.jar are required if you are using the IBM MQ classes for JMS.
com.ibm.mq.jakarta.client.jar and jakarta.jms-api.jar are required if you are using IBM MQ classes for Jakarta Messaging.
fscontext.jar is required if you are using IBM MQ classes for JMS or IBM MQ classes for Jakarta Messaging and are accessing JMS administered objects that are stored in a file system JNDI context.
providerutil.jar is required if you are using the IBM MQ classes for JMS or IBM MQ classes for Jakarta Messaging and are accessing JMS administered objects that are stored in a file system JNDI context.
The Bouncy Castle security provider and CMS support JAR files are required for support for non-IBM JREs. For more information, see Support for non-IBM JREs.