14.2 When Is Synchronization Done?

The Identity Manager engine performs object synchronization or merging in the following circumstances:

  • A <sync> event element is submitted on the Subscriber or Publisher channel.

  • A <sync> event element is submitted on the Subscriber channel in the following circumstances:

    • The state of the object’s association value is set to “manual” or “migrate.” (This causes an eDirectory event, which in turn causes the Identity Manager caching system to queue an object synchronization command in the affected driver’s cache.)

    • An object synchronization command is read from the driver’s cache.

  • A <sync> event element is submitted on the Publisher channel in the following circumstances:

    • A driver submits a <sync> event element. No known driver currently does this.

    • The Identity Manager engine submits a <sync> event element for each object found as the result of a migrate-into-NDS query. These <sync> events are submitted by using the Subscriber thread, but are processed using the Publisher channel filter and policies.

  • An <add> event (real or synthetic) is submitted on a channel and the channel Matching policy finds a matching object in the target system.

  • An <add> event with an association is submitted on the Subscriber channel. This normally occurs only in exceptional cases, such as the bulk load of objects into eDirectory with DirXML-Associations attribute values.

  • An <add> event is submitted on the Publisher channel and an object is found in eDirectory that already has the association value reported with the <add> event.

The Identity Manager engine generates synchronization requests for zero or more objects in the following cases:

  • The user issues a manual driver synchronization request. This corresponds to the Resync button in the Driver Set property page in ConsoleOne, or to the Synchronize button on the iManager Identity Manager Driver Overview page.

  • The Identity Manager engine encounters an error with the driver’s cache and cannot recover from the cache error. The driver’s cache is deleted and the engine generates object synchronization commands as detailed in How Does the Identity Manager Engine Decide Which Object to Synchronize?.