Processing of the reconciliation event data:

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