Taking action on the event:

Deployment Configurations 4-9 ■ Creating a new account and associating with proper owner identity ■ Updating the matched account ■ Deleting the matched account ■ Creating a new user in Oracle Identity Manager ■ Modifying an existing user in Oracle Identity Manager ■ Deleting an existing user ■ Enabling and disabling account status by updating the status attribute ■ Enabling or disabling user ■ Creating, updating, or deleting role ■ Creating or deleting role membership ■ Creating or deleting role hierarchy

6. Follow up actions triggered by the reconciliation event:

After the action is taken, follow up tasks can be started based on the reconciliation event. An example of follow up tasks or post-processing task is creating a request to provision a resource, such as a laptop computer, after a user creation event.

4.2.1.2 Mode of Reconciliation

The mode of reconciliation is either pull or push that depends on the connector used. Most connectors, such as Active Directory, use the pull model. For the pull model, a pull reconciliation task is scheduled in the IAM Scheduler. The task runs at recurring intervals. Typically, the pull-based reconciliation connectors submit the reconciliation events within a scheduled task. Every time the scheduled task runs, a new reconciliation run is triggered and the reconciliation events are created in batches. When the batch size is met, the batch is submitted for processing. At the end of the scheduled task, an end of job listener is triggered, which submits all the batches whose size is not met. Other reconciliation connectors, such as the PeopleSoft connector, use a push model. The connector comprises of an HTTP listener that detects any asynchronous messages issued by PeopleSoft. On receiving a message, the listener submits reconciliation events by calling the reconciliation API. The events are processed by the reconciliation engine in batches when the batch size is met. For batches where batch size is not met, a scheduled task runs periodically and submits the batches for reconciliation processing. Pull or push model is used based on the nature of the target system and how the changes can be detected in the target system. But irrespective of the push or pull Note: The actions on the event can be manually performed through the UI, or they can be automatic actions. See Also: Reconciliation Engine on page 4-14 for information about role membership and role hierarchy See Also: Managing Scheduled Tasks for information about the IAM Scheduler in the Oracle Fusion Middleware Administrators Guide for Oracle Identity Manager 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