Connector Architecture

1.5 Connector Architecture

The Fusion Apps is implemented by using the Identity Connector Framework (ICF).

The ICF is a component that is required in order to use Identity Connector. ICF provides basic reconciliation and provisioning operations that are common to all Oracle Identity Governance connectors. In addition, ICF provides common features that developers would otherwise need to implement on their own, such as, buffering, time outs, and filtering. ICF is distributed together with Oracle Identity Governance. Therefore, you do not need to configure or modify ICF.

The following figure shows the architecture of the Fusion Apps.

Figure 1-1 Fusion Apps Connector Architecture

The connector is configured to run in one of the following modes:

Account management

Account management is also known as target resource management. In this mode, the target system is used as a target resource and the connector enables the following operations:

Provisioning

Provisioning involves creating and updating users and workers and deleting users on the target system through Oracle Identity Governance. During provisioning, the adapters invoke the ICF operation; ICF in turn invokes the create operation on the Fusion Apps Identity Connector Bundle, and then the bundle calls the target system API (Fusion Apps API) for provisioning operations. The API on the target system accepts provisioning data from the bundle, carries out the required operation on the target system, and returns the response from the target system back to the bundle, which passes it to the adapters.

Target resource reconciliation

During reconciliation, a scheduled task initiates an ICF operation, which involves searching the Fusion Apps Identity Connector Bundle. This bundle interfaces with the Fusion Apps API to retrieve user and worker records that meet specific criteria. These records are then returned via the bundle and ICF to the scheduled task, where they are integrated into Oracle Identity Governance.

Each record from the target system is compared to existing Fusion Apps resources provisioned in OIM. When a match is found, updates from the target system's Fusion Apps record are copied to the corresponding Fusion Apps resource in Oracle Identity Governance. If there's no match, the record's name is compared with OIM user logins. In the event of a match, the data from the target system's record is utilized to provision a Fusion Apps resource for the OIM user.

The Fusion Apps Identity Connector Bundle communicates with the Fusion Apps API using the HTTPS protocol. The Fusion Apps API provides programmatic access to Fusion Apps through SCIM/REST API endpoints. SCIM APIs are used to manage users' information and REST APIs are used to manage workers' information. Fusion Apps APIs are used to perform create, read, update, and delete (CRUD) operations on Fusion Apps target application.