4.5 Event Processing

The DirXML engine applies rules and event filters to events coming from eDirectory and from the application. The order varies according to the channel.The following sections list the order of application. The lists assume that the event passes all the rules. Events which fail are dropped.

4.5.1 Subscriber Channel

When an operation occurs in eDirectory that generates an add, move, delete, rename, or modify event, the DirXML engine performs the following steps in the order listed.

  1. Verifies that the event contains object classes and attributes allowed by the subscriber filter.
  2. Applies the event transformation rules.
  3. If the event is a modify event on an unassociated object, converts the event to an add event.
  4. If the event is an add event, applies the following:
    • Matching rules
    • Create rules
    • Placement rules
  5. Applies the command transformation rules.
  6. Applies the schema mapping rules.
  7. Applies any output transformations.
  8. Sends the commands to the driver.

Any of the rules can cause an event to be dropped.

  • If event doesn't pass the filter, it is dropped.
  • If the matching rules produce multiple matches for the entry, an error is logged and the event is dropped.
  • If the entry does not pass the criteria for a create rule, the event is dropped.
  • If the entry does not pass the criteria for a placement rule, the event is dropped.

You need to analyze the dropped events to determine if the rules are producing the desired results or if the rules need to be refined.

4.5.2 Publisher Channel

When an event occurs in the application, the publisher channel of the driver sends the engine an XML document to process. The DirXML engine then performs the following steps before sending the event to eDirectory.

  1. Applies the input transformation rules.
  2. Applies the schema mapping rules.
  3. Applies the event transformation rules.
  4. Applies the publisher event filter.
  5. If the event is a modify event on an unassociated object, converts the event to an add event.
  6. If the event is an add event, applies the following rules:
    • Matching rules
    • Create rules
    • Placement rules
  7. Applies the command transformation rule.
  8. Sends the event to eDirectory.

Any of the rules can cause an event to be dropped.

  • If event doesn't pass the filter, it is dropped
  • If the matching rules produce multiple matches for the entry, an error is logged and the event is dropped.
  • If the entry does not pass the criteria for a create rule, the event is dropped.
  • If the entry does not pass the criteria for a placement rule, the event is dropped.

You need to analyze the dropped events to determine if the rules are producing the desired results or if the rules need to be refined.