Classes

This section does not apply to the WebSphere MQ Everyplace native C codebase.

WebSphere MQ Everyplace provides a choice of classes for certain functions that allow you to customize WebSphere MQ Everyplace behavior to meet specific application requirements. In some cases the interfaces to classes are documented so that additional alternatives can be developed. Table 4 summarizes the possibilities. Classes can be identified either explicitly or through the use of alias names.

Note:
Some of the classes are not provided in the C Bindings API. See WebSphere MQ Everyplace Java Programming Reference and WebSphere MQ Everyplace C Programming Reference on the product CD for definitive lists of the supported classes.


Table 4. Class options

Class Alternatives supplied Interfaces documented
Administration No Yes
Authenticators Yes No
Communications adapter Yes Yes
Communications style Yes No
Compressors Yes No
Cryptors Yes No
Event log Sample provided Yes
Messages No Yes
Queue storage Yes No
Rules Default classes provided Yes
Trace Samples provided Yes

Application loading

This section does not apply to the C codebase.

When a WebSphere MQ Everyplace queue manager is loaded, the initiating application must load any other applications into the JVM. Standard Java facilities can be used for this, or you can use the class loader included as part of WebSphere MQ Everyplace. Therefore, multiple applications can run against a single queue manager in the same JVM. Alternatively, you can use multiple JVM, but each requires its own queue manager and each of these must have a unique name.



© IBM Corporation 2002. All Rights Reserved