Oracle® Identity Management Integration Guide
10g Release 2 (10.1.2) B14085-02 |
|
Previous |
Next |
In this example, the MyCompany enterprise requires that all users be created in Oracle Human Resources. Directory Integration and Provisioning must propagate new user records to all other repositories in the enterprise.
Figure B-2 shows how Directory Integration and Provisioning performs this task.
Figure B-2 shows the creation of a new user in Oracle Human Resources, which, in turn, causes an entry for that user to be created in Oracle Internet Directory and the SunONE Directory Server. It also shows the process of provisioning the user to access two applications in the enterprise: OracleAS Portal and Oracle Content Management Software Development Kit. User creation and provisioning occur in the following manner:
The Oracle Human Resources administrator creates the user in the Oracle Human Resources database.
Directory Integration and Provisioning, through the Oracle Directory Synchronization Service, detects the new-user creation.
Directory Integration and Provisioning, through the Oracle Directory Synchronization Service creates the entry for the user in Oracle Internet Directory.
Directory Integration and Provisioning, through the Oracle Directory Synchronization Service, creates an entry in the SunONE Directory Server.
Because the user entry is available in Oracle Internet Directory, the OracleAS Portal administrator can now provision the user to use the services of OracleAS Portal. During this task, the OracleAS Portal software automatically retrieves the user details from Oracle Internet Directory.
The Oracle Content Management Software Development Kit administrator also provisions the user to use Oracle Content Management Software Development Kit services by using a similar process.
Note that Directory Integration and Provisioning does not directly notify OracleAS Portal or Oracle Content Management Software Development Kit about new users. This is because not all users created in Oracle Human Resources need access to all services. In this case, the deployment must explicitly provision the users to use these services, as in steps 5 and 6.