Follow up actions triggered by the reconciliation event:

4-10 Oracle Fusion Middleware Users Guide for Oracle Identity Manager model being used, reconciliation is performed by using a scheduled task that runs in the IAM Scheduler. Changelog reconciliation is the default reconciliation mode. In this mode, only changed attributes are reconciled. Unspecified fields are ignored. You typically use the Changelog reconciliation mode when a connector is aware of the list of changed attributes. Along with the changed attributes, Oracle Identity Manager needs a list of required fields for matching. The Changelog reconciliation mode was supported in previous Oracle Identity Manager releases, so all connectors work in this mode. Regular reconciliation is a new reconciliation mode, introduced in this release, where the reconciliation engine completely replaces the existing snapshot of the entity. You typically use this reconciliation mode when the connector cannot determine which attributes have changed, and therefore, sends an entire snapshot of the entity. For new connectors, you can specify this mode when performing a full reconciliation. Using regular reconciliation mode results in better performance because the events are processed faster. Table 4–2 lists the differences between regular and changelog reconciliation modes:

4.2.1.3 Approach Used for Reconciliation

When you run reconciliation for the first time on a target system, all users and accounts on the target system are reconciled into Oracle Identity Manager by default. This is called full reconciliation. To perform full reconciliation, the connector sends the reconciliation events for each entity in the target system. The reconciliation engine processes the events as create or update events depending on whether or not the entity already exists in Oracle Identity Manager. The connector also identifies all the deleted entries and sends the deletion events to Oracle Identity Manager. Note: You can also create the reconciliation events directly by using the reconciliation APIs. Note: The mode of reconciliation depends on the connector implementation. For information about connector implementation, see Connector for Reconciliation on page 4-21. Table 4–2 Regular and Changelog Reconciliation Modes Regular Changelog Must pass a full set of mapped attributes Must pass a subset of mapped attributes that are required by the specific profile and used by matching a rule Performs better in batch processing mode no difference in performance while in single event processing mode Creates and updates all fields Creates and updates only specified fields, and all other fields remain unchanged See Also: Changing the Profile Mode in the Oracle Fusion Middleware Administrators Guide for Oracle Identity Manager for information about changing the reconciliation mode