Overview
The MQe Application Programming Interface
(API) is the programming interface to MQe. Two languages are supported, Java
and C.
- The Java version
- Provides access to all MQe function at Version 2. The detailed classes,
methods, and procedures are described in the Java API Programming Reference. Examples of MQe programming
are given throughout this information center.
There are three versions of the C support:
- The Native C codebase
- Provides access to a major subset of MQe function, the main restriction
being that only device queue managers can be used. Other restrictions are
as follows (see also the table below):-
- Does not support store-and-forward queues or bridge queues
- Supports the HTTP adapter only
- Supports the RLE compressor only
- Supports the RC4 cryptor only
- Supports the MAttribute and local security features only
The detailed methods and procedures are described in the C API Programming Reference. Examples of programming
MQe for the C bindings are given throughout this information center.
- The C Bindings
- are supplied for use until the Native C codebase provides full functionality.
Your application calls the C API in the bindings, and the call is routed to
the Java classes for MQe to carry out the function. The bindings were written
for MQe Version 1, but still provide access to nearly all of the Java function
in MQe Version 2. The detailed methods and procedures are described in the C API Programming
Reference. Examples of programming MQe for the C bindings are given
in the C
Bindings Programming Guide.
- The C support for Palm
- provides access for a subset of the MQe function for use on Palm devices,
the main restriction being that only device queue managers can be used. The
C support for Palm remains at MQe Version 1. Details of the classes and procedures,
together with programming guidance, are provided in C Programming Guide for Palm OS.
Types of queue manager
Throughout this documentation,
and in the table below, the following queue manager descriptions are used,
and it is important to distinguish between them:-
- Device queue manager
- A queue manager with no listener component, and no bridge component. It
therefore can only send messages, it cannot receive them.
- Server queue manager
- A queue manager that can have a listener added. With the listener it can
receive messages as well as send them.
- Gateway queue manager
- A queue manager that can have a listener and a bridge added. With the
listener it can receive messages as well as send them, and with the bridge
it can communicate with MQ.