Classes

This section does not apply to the MQe native C codebase.

MQe provides a choice of classes for certain functions that allow you to customize MQe behavior to meet specific application requirements. In some cases the interfaces to classes are documented so that additional alternatives can be developed. The table below 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 Java API Programming Reference and C API Programming Reference for definitive lists of the supported classes.

Many of these classes are automatically given an alias by MQe, these are documented in the Java API Programming Reference in com.ibm.mqe.MQe.alias.

Table 1. Class options
Class Alternatives supplied Interfaces documentedMQe packageHow to implement
AdministrationNoYes  
Authenticators YesNocom.ibm.mqe.attributesextend com.ibm.mqe.MQeAuthenticator
Communications adapter YesYescom.ibm.mqe.adaptersextend com.ibm.mqe.adapters.MQeCommunicationsAdapter
Communications style YesNo  
Compressors YesNocom.ibm.mqe.attributesextend com.ibm.mqe.MQeCompressor
Cryptors YesNocom.ibm.mqe.attributesextend com.ibm.mqe.MQeCryptor
Event log Sample providedYes implement com.ibm.mqe.MQeEventLogInterface
Messages NoYescom.ibm.mqeextend com.ibm.mqe.MQeMsgObject
Queue storage YesNo Normally the default as defined by the alias MsgLog: should be used. See more in Queue persistent storage.
RulesDefault classes providedYes extend com.ibm.mqe.MQeRule
Storage adapter YesYescom.ibm.mqe.adaptersextend com.ibm.mqe.adapters.MQeAdapter
     
TraceSamples providedYescom.ibm.mqe.trace 

Parent topic: How MQe works