Using rules

Introduction to using MQe rules

MQe uses rules (which are essentially user exits) to allow applications to monitor and modify the behavior of some of its major components. Rules take the form of methods on Java™ classes or functions in C methods that are loaded when MQe components are initialized.

A component's rules are invoked at certain points during its execution cycle. Rules methods with particular signatures are expected to be available, so when providing implementations of rules, ensure that you use the correct signatures.

Default or example rules are provided for all relevant MQe components. You can customize these to satisfy particular user requirements. Within the Java code base, the MQeQueueProxy interface provides the user with accessor methods for queues, allowing the user to interact with queues in certain rule methods.

Rules may be grouped into the following categories:
  • Queue manager rules.
  • Queue rules.
  • Attribute rules.
  • Bridge rules.

Rules may also be categorized into two groups depending upon whether they can affect application behavior (modification rules) or are intended for notification purposes only (notification rules).


Terms of use | WebSphere software

(c) Copyright IBM Corporation 2004, 2005. All rights reserved.