Java deployment

When deploying WebSphere MQ Everyplace applications, you are recommended to pack the minimum set of classes required by the application into compressed jar files. This ensures that the application requires the minimum system resources. WebSphere MQ Everyplace provides the following examples of how the WebSphere MQ Everyplace classes can be packaged into .jar files. These examples are in the<MQeInstallDir>\Java\Jars directory of a standard WebSphere MQ Everyplace installation.

WebSphere MQ Everyplace ships the following .jar files

MQeBase.jar
This file contains basic information only. It does not contain any security information, compressors, cryptors, or authenticators. It contains all communication information, queue types, administration for all of the included resources. It also contains a client and server. With the MQeBase.jar, you can send WebSphere MQ Everyplace and WebSphere MQ Everyplace MQ messages. It supports the diskfields, memory, and reduceddiskfields adapters.

MQeBindings.jar
This file contains all C bindings specific information. You need this .jar file to use the C library bindings to control a Java WebSphere MQ Everyplace queue manager. It includes com.ibm.mqe.bindings, which you need to use the C library bindings.

MQeCore.jar
This contains mandatory classes.

MQeDeprecated.jar
This contains all of the deprecated class files that are no longer needed by a WebSphere MQ Everyplace application. These deprecated class files help you run applications written using a previous version of WebSphere MQ Everyplace, without making any changes.

MQeDiagnostics.jar
This file helps to diagnose problems with WebSphere MQ Everyplace classes. It contains tooling to search the class path to find out the level of each class found.

MQeExamples.jar
A packaging of all the WebSphere MQ Everyplace examples into one jar file. This includes all of the examples supplied with WebSphere MQ Everyplace, but excludes the deprecated classes.

MQeGateway.jar
This contains the classes that can be used on a server platform. It includes the bridge class, but excludes the deprecated classes.

MQeJMS.jar
This contains the classes that provide a subset of the JMS interface, suitable for use on smaller devices.

MQeMidp.jar
This is equivalent to MQeBasic.jar, but it is for use with J2ME.

MQeMigration.jar
This contains classes in the com.ibm.mqe.validation package.

MQeRetail.jar
This contains extra message stores with short filenames.

MQeSecurity.jar
A set of classes that can be used to extend both the MQeBasic.jar to allow both queue and message based security.

A new jar file, the MQeMidpBase.jar

To run WebSphere MQ Everyplace applications, you must set up the Java runtime environment to include the required WebSphere MQ Everyplace and application classes. Using a standard Java runtime environment (JRE), you must set the CLASSPATH to include any required jar files.

Example statements are:

Windows
Set CLASSPATH=<MQeInstallDir>\Jars\MQeDevice.jar;%CLASSPATH%

UNIX
CLASSPATH=<MQeInstallDir>/Java/Jars/MQeDevice.jar:$CLASSPATH
export CLASSPATH
 


© IBM Corporation 2002. All Rights Reserved