A rule class is a repository for one or more rules that share a common event structure. A rule class may also share similar rule action preferences or values associated with each rule for appropriate action execution. A rule is an expression defined using the attributes of an event structure.

On this page, you can specify event management policies for a single primitive event structure for a composite event. These settings for each primitive event will override the rule class-level properties

The consumption policy for the reuse of each primitive event for this composite event. The consumption policy options are:

• Shared - a primitive event can be used to match any number of rules and execute their action. The primitive event is removed from the system only when its duration specification is met. This is the default consumption policy.
• Exclusive - a primitive event can be used to match only one rule (which ever matches first). Once the corresponding rule action is executed, this event is removed from the system, irrespective of the event duration specification (Transaction, Session, or Elapsed time).
• Rule - (for composite events) implies that primitive events are not consumed by the system and individual rules may decide to consume the events using a special procedure. Primitive events can only accept a value of "Shared" for the consumption policies. Identifiers for individual primitive events returned from the action callback procedure and rule class results view are used to consume the primitive events before executing the corresponding rule action.
• None - no consumption policy specifed. When "None" is specified for a member consumption policy, the rule class level consumption policy is in effect.

The event duration or life span of each unconsumed primitive event for this composite event. The duration policy options are:

• Elapsed time - the duration of a primitive event added to the system is determined by an event timeout associated with the rule class. The event timeout is specified as elapsed time (in hours, or days, or minutes) and this is added to the creation time (determined by its rlm$CrtTime attribute) to determine the exact time of event execution.
• Call - the duration of a primitive event can be considered for rule matching only during the PROCESS_RULES or ADD_EVENT call. These events are not considered for rule matching after the call regardless of any rule executions during the call.
• None - no duration policy specified. When "None" is specified for a duration policy, then the rule class level duration policy is in effect.

This is a summary of the choices made in this Property Editor. It is not editable.

Related Topics

Rule Class Wizard

Rule Class Wizard - Rule Class Designer

Rule Class Wizard - Composite Rule Class Property Editor

Event Structure Wizard

Rule Creation Wizard