Rules allow users to customize the behavior of some main WebSphere MQ Everyplace components. WebSphere MQ Everyplace provides default rules where necessary, but you can replace these with application or installation-specific rules to meet customer requirements. The rule types supported differ in how they are triggered and in what they can do. Rules contain logic and can therefore perform a wide range of functions.
Attribute rules apply to the Java codebase only. This rule class is given control whenever a change of state is attempted, for example, a change of:
The rule would normally allow or disallow the change.
WebSphere MQ bridge rules apply to the Java codebase only. These rule classes are given control when the WebSphere MQ Everyplace to WebSphere MQ bridge code has a change of state. There is a separate bridge rule class to determine each of the following:
Chapter 2, Rules, of the WebSphere MQ Everyplace System Programming Guide and Chapter 7, Interoperability with other messaging systems, of the WebSphere MQ Everyplace Application Programming Guide provide detailed information on WebSphere MQ bridge rules.
This rule class is invoked at key points in the lifestyle of a queue, for example when:
This rule class invoked at key points in the lifecycle of a queue manager, for example when: