WebSphere MQ Everyplace is supplied with a set of class libraries in the
form of jar files that can be used when deploying applications that utilize
WebSphere MQ Everyplace. There are two types of jar file; base jar
files and extension jar files. The base jar files allow a usable queue
manager to be created, administered and run. The extension jar files
can be used in addition to the base jar files to provide additional
capability.
- MQeBase.jar
- Contains classes that provide for a basic queue manager running in client
and server mode on a J2ME CDC/Foundation or J2SE or better Java
runtime.
- MQeMidp.jar
- Similar to MQeBase.jar but for use on a J2ME CLDC/MIDP Java
runtime. Allows a queue manager to run in client mode. All MIDP
compliant classes are included in this jar. No extension jars can be
used with this one, as they are not MIDP compliant.
- MQeGateway.jar
- Contains classes that provide for a basic queue manager running in client,
server and bridge mode on a J2SE or better Java runtime.
- MQeJMS.jar
- Contains the classes that extend an WebSphere MQ Everyplace queue manager
to provide a JMS programming interface.
- MQeRetail.jar
- Contains extra classes for use in retail environments. In
particular, these classes are useful on a 4690 retail system.
- MQeSecurity.jar
- A set of classes that are used to provide both queue and message based
security. It contains a set of cryptors, compressors and
authenticators.
- MQeBindings.jar
- This file contains all C bindings specific information. It is
required if access to a Java queue manager from a C application is needed
(only on Win32 platforms).
- MQeMigration.jar
- Contains classes that assist in migrating from an earlier version of
WebSphere MQ Everyplace.
- 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.
- MQeCore.jar
- This contains a minimal set of classes. On its own it is not usable
but it can be used as a base for building a small footprint WebSphere MQ
Everyplace system. More details on reducing footprint can be found in
the "Optimizing footprint" section.
© IBM Corporation 2002, 2003. All Rights Reserved