When deploying MQe 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.
MQe provides the following examples of how the MQe classes can be packaged
into .jar files. These examples are in the<MQeInstallDir>\Java\Jars directory
of a standard MQe installation.
There are three types of jar file;
base,
extension, and
other:
- 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
- The other jar files include example, and core, sets of classes for you
to use as a base for your development
Base jar files
- 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.
Extension jar files
- MQeJMS.jar
- Contains the classes that extend an MQe 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 MQe.
- MQeDeprecated.jar
- This contains all of the deprecated class files that are no longer needed
by an MQe application. These deprecated class files help you run applications
written using a previous version of MQe, without making any changes.
- MQeDiagnostics.jar
- This file helps to diagnose problems with MQe classes. It contains tooling
to search the class path to find out the level of each class found.
- MQeJMX.jar
- Contains the classes needed to administer MQe using JMX.
- MQeJMSAdmin.jar
- Contains the classes needed to administer MQe using JMS.
- MQeJMSSQL.jar
- Contains the classes needed to administer MQe using SQL.
Other jar files
- MQeExamples.jar
- A packaging of all the MQe examples into one jar file. This includes all
of the examples supplied with MQe, 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 MQe system. More
details on reducing footprint can be found in Optimizing footprint.
- MQeBundle.jar
- This jar provides the MQe 'bundle' for OSGi frameworks and is a code-only
bundle.
- MQeClientBundle.jar
- Example OSGi bundles showing how to run MQe within the OSGi framework.s
- MQeServerBundle.jar
- Example OSGi bundles showing how to run MQe within the OSGi framework.
OSGi-related examples
- MQeJMSReceiver.jar
- Example OSGi bundles using the JMS interface.
- MQeJMSSender.jar
- Example OSGi bundles using the JMS interface.
JMS-related examples
- MQeJMSAdmin.jar
- Provides classes to create and edit administered objects stored in a JNDI
namespace.
- MQeJMSSQL.jar
- Provides the classes required if JMS SQL selectors are to be used.
- MQeTraceDecode.jar
- Provides classes to decode MQe trace file.