Prerequisites for IBM MQ classes for JMS

This topic tells you what we need to know before using IBM MQ classes for JMS. To develop and run IBM MQ classes for JMS applications, we need certain software components as prerequisites.

For information about the prerequisites for IBM MQ classes for JMS, see System Requirements for IBM MQ.

To develop IBM MQ classes for JMS applications, we need a Java SE Software Development Kit (SDK). for details of the JDKs supported by your operating system, see System Requirements for IBM MQ.

To run IBM MQ classes for JMS applications, we need the following software components:

  • An IBM MQ queue manager.
  • A Java runtime environment (JRE), for each system on which you run applications.
  • For IBM i, Qshell, which is option 30 of the operating system.
  • For z/OS, UNIX and Linux System Services (USS).

The IBM JSSE provider includes a FIPS certified cryptographic provider, so can be programmatically configured for FIPS 140-2 compliance ready for immediate use. Therefore, FIPS 140-2 compliance can be supported directly from IBM MQ classes for Java and IBM MQ classes for JMS.

Oracle's JSSE provider can have a FIPS certified cryptographic provider that is configured into it, but this is not ready for immediate use and is not available for programmatic configuration. Therefore, in this case, IBM MQ classes for Java and IBM MQ classes for JMS cannot enable FIPS 140-2 compliance directly. You might be able to manually enable such compliance, but IBM cannot currently provide guidance on this.

We can use Internet Protocol Version 6 (IPv6) addresses in the IBM MQ classes for JMS applications if IPv6 addresses are supported by your Java virtual machine (JVM) and the TCP/IP implementation on your operating system. The IBM MQ JMS administration tool (see Configure JMS objects using the administration tool ) also accepts IPv6 addresses.

The IBM MQ JMS administration tool and IBM MQ Explorer use the Java Naming Directory Interface (JNDI) to access a directory service, which stores administered objects. IBM MQ classes for JMS applications can also use JNDI to retrieve administered objects from a directory service. A service provider is code that provides access to a directory service by mapping JNDI calls to the directory service. A file system service provider in the files fscontext.jar and providerutil.jar is supplied with IBM MQ classes for JMS. The file system service provider provides access to a directory service based on the local file system.

If you intend to use a directory service based on an LDAP server, we must install and configure an LDAP server, or have access to an existing LDAP server. In particular, we must configure the LDAP server to store Java objects. For information about how to install and configure your LDAP server, see the documentation that is supplied with the server.

Parent topic: Use IBM MQ classes for JMS