JMS requirements

In order to use the MQe JMS programming interface, the JMS interface classes are required.

These are contained typically in jms.jar.

MQe does not ship with jms.jar, and this must be downloaded before JMS can be used.

At the time of writing, this can be freely downloaded from http://java.sun.com/products/jms/docs.html. The JMS Version 1.0.2b jar file is required.

JNDI

In addition, if JMS administered objects are to be stored and retrieved using the Java™ Naming and Directory Interface (JNDI), the javax.naming.* classes must be available.

If Java 1 is being used, for example, a 1.1.8 JRE, jndi.jar must be obtained and added to the classpath.

If Java 2 is being used, for example a 1.2 or later JRE, the JRE might contain these classes.

You can use MQe without JNDI, but at the cost of a small degree of provider dependence. MQe-specific classes must be used for the ConnectionFactory and Destination objects.

You can download JNDI jar files from http://java.sun.com/products/jndi


Terms of use | WebSphere software

(c) Copyright IBM Corporation 2004, 2005. All rights reserved.