Overview#
The Merge Processor exists to reconcile objects in
EDirectory with the ones in the connected application when equivalent objects already exist on both sides.
If the XDS Document reaches the Merge Processor, then the engine has determined there the entry exists in EDirectory and the Connected Application.
The Merge Processor's behavior can be controlled by setting the values for the Merge Authority on a per attribute basis in the Novell IDM Driver Filters interface within iManager or Novell Designer and controls the operation of the Merge Processor.
The Merge Processor, when invoked, queries destination data store for all attributes listed in the
Novell IDM Driver Filters for the current object's class, then builds <modify> events for both source and destination data stores based on the
Merge Authority on each attribute in the
Novell IDM Driver Filters. The
DirXML Merge-Resync Process provides more details on the process.
When is the Merge Processor Used?#
The Merge Processor could be activated in either the
Subscriber Flow of in the
Publisher Flow.
The Merge Processor can be triggered by add or modify event. They could be any one of these four originating events:
- When a <sync> (migrate) event occurs on an associated object.
No matching rule is performed, the filter is read with its merge-authority settings, the engine will issue one or more modify commands in each directory (to eDirectory and to the application).
- When a <sync> event occurs on an unassociated object.
The matching rule is performed, upon a successful match, the filter is read with its merge-authority settings, the engine will issue one or more modify commands in each directory (to eDirectory and to the application).
If no match is found, the sync is converted to a synthetic add
- a regular <add> on an unassociated object.
The matching rule is performed, upon a successful match, the filter is read with its merge-authority settings, the engine will issue one or more modify commands in each directory (to eDirectory and to the application). If no match is found, the event just continues through the rest of the channel.
- a regular <modify> on an unassociated object.
The matching rule is performed, upon a successful match, the filter is read with its merge-authority settings, the engine will issue one or more modify commands in each directory (to eDirectory and to the application). If no match is found, the event is converted to a synthetic add.
There might be more information for this subject on one of the following: