Oracle® Identity Manager Connector Guide for Oracle E-Business User Management Release 9.0.4 Part Number E10435-04 |
|
|
View PDF |
Oracle Identity Manager automates access rights management, security, and provisioning of IT resources. Oracle Identity Manager connectors are used to integrate Oracle Identity Manager with third-party applications. This guide discusses the procedure to deploy the connector that is used to integrate Oracle Identity Manager with Oracle E-Business User Management.
This chapter contains the following sections:
Note:
In this guide, the term Oracle Identity Manager server refers to the computer on which Oracle Identity Manager is installed.At some places in this guide, Oracle E-Business User Management has been referred to as the target system.
Reconciliation involves duplicating in Oracle Identity Manager the creation of and modifications to user accounts on the target system. It is an automated process initiated by a scheduled task that you configure.
See Also:
The "Deployment Configurations of Oracle Identity Manager" section in Oracle Identity Manager Connector Concepts Guide for conceptual information about reconciliation configurationsBased on the type of data reconciled from the target system, reconciliation can be divided into the following types:
Lookup fields reconciliation involves reconciling the Responsibility lookup field.
User reconciliation involves reconciling the following fields:
Provisioning involves creating or modifying a user's account information on the target system through Oracle Identity Manager. You use the Oracle Identity Manager Administrative and User Console to perform provisioning operations.
See Also:
The "Deployment Configurations of Oracle Identity Manager" section in Oracle Identity Manager Connector Concepts Guide for conceptual information about provisioningFor this target system, the following fields are provisioned:
User ID (read-only)
userName
password
confPassword
lifeSpanType
lifeSpanValue
startDate
endDate
employeeId
description
respName
respStartDate
respEndDate
Note:
During provisioning, if you want to link a newly created user account with an employee account, then you must ensure that theOracleHR.Employees
lookup field is populated. For this, you must install the Oracle E-Business Employee Reconciliation connector and reconcile employee data.
If you do not want to link a newly created user account with an employee account, then the OracleHR.Employees
lookup field is not required.
Target System Stored Procedures Used During Provisioning
The following target system stored procedures are used for provisioning operations:
fnd_global.APPS_INITIALIZE
FND_USER_PKG.CreateUser
FND_USER_PKG.UpdateUser
FND_USER_PKG.DisableUser
FND_USER_PKG.EnableUser
FND_USER_PKG.AddResp
FND_USER_PKG.DelResp
FND_USER_PKG.change_user_name
The following table lists the functions that are available with this connector.
Function | Type | Description |
---|---|---|
Create User | Provisioning | Creates a user |
Disable User | Provisioning | Disables a user
When this function is run, the end date assigned to the user account is changed to the current date. |
Email Updated | Provisioning | Updates the e-mail address of a user |
Password Updated | Provisioning | Updates the password of a user |
Description Updated | Provisioning | Updates the description of a user |
Start Date Updated | Provisioning | Updates the start date of a user's account validity period |
End Date Updated | Provisioning | Updates the end date of a user's account validity period |
LifeSpan Type Updated | Provisioning | Updates the Life Span type of a user |
LifeSpan Updated | Provisioning | Updates the Life Span value of a user |
Enable User | Provisioning | Enables a user so that the user is able to log in to Oracle E-Business User Management
When this function is run on a disabled user account, the end date of the user account is changed to a null value. |
Add Responsibility | Provisioning | Adds a responsibility to a user |
Remove Responsibility | Provisioning | Removes a responsibility from a user
When this function is run, the end date of the responsibility allocation is changed to the current date. |
Update user name | Provisioning | Updates the user name of a user. |
Employee Id Updated | Provisioning | Updates the employee ID of a user |
Update Xellerate User (OIM User) | Reconciliation | Updates an Oracle Identity Manager user with data received from Oracle E-Business User Management |
Update Apps Resource | Reconciliation | Updates an Oracle Identity Manager resource with data received from Oracle E-Business User Management |
Create Link with Oracle HR Employee | Reconciliation | Sets the employee ID of an Xellerate User (OIM User) to the corresponding Oracle E-Business User Management user |
See Also:
Appendix A for information about attribute mappings between Oracle Identity Manager and Oracle E-Business User ManagementThe connector supports the following languages:
Arabic
Chinese Simplified
Chinese Traditional
Danish
English
French
German
Italian
Japanese
Korean
Portuguese (Brazilian)
Spanish
See Also:
Oracle Identity Manager Globalization Guide for information about supported special charactersThe files and directories on the installation media are listed and described in Table 1-1.
Table 1-1 Files and Directories on the Installation Media
You might have a deployment of an earlier release of the connector. While deploying the latest release, you might want to know the release number of the earlier release. To determine the release number of the connector that has already been deployed:
In a temporary directory, extract the contents of the following JAR file:
OIM_HOME/xellerate/ScheduleTask/xlReconOracleApps.jar
Open the manifest.mf
file in a text editor. The manifest.mf
file is one of the files bundled inside the xlReconOracleApps.jar
file.
In the manifest.mf
file, the release number of the connector is displayed as the value of the Version property.