Connector Architecture

1.5 Connector Architecture

The Cerner 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.

Figure 1-1 shows the architecture of the Cerner.

Figure 1-1 Cerner 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, updating, or disabling users on the target system through Oracle Identity Governance. During provisioning, the Adapters invoke ICF operation, ICF in turn invokes create operation on the Cerner Identity Connector Bundle and then the bundle calls the target system API (Cerner 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 invokes an ICF operation. ICF in turn invokes a search operation on the Cerner Identity Connector Bundle and then the bundle calls Cerner API for Reconciliation operation. The API extracts user records that match the reconciliation criteria and hands them over through the bundle and ICF back to the scheduled task, which brings the records to Oracle Identity Governance.

Each record fetched from the target system is compared with Cerner resources that are already provisioned to OIM Users. If a match is found, then the update made to the Cerner record from the target system is copied to the Cerner resource in Oracle Identity Governance. If no match is found, then the Name of the record is compared with the User Login of each OIM User. If a match is found, then data in the target system record is used to provision a Cerner resource to the OIM User.

The Cerner Identity Connector Bundle communicates with the Cerner API using the HTTP protocol. The Cerner API provides programmatic access to Cerner through Cerner SOAP API endpoint. Apps can use the SOAP API to perform create, read, and update, operations on directory data and directory objects, such as users, personnel groups, Organization, Organization Groups and Personal alias.