Skip Headers
Oracle® Identity Manager Connector Guide for Oracle E-Business User Management
Release 9.0.4

Part Number E10435-04
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

1 About the Connector

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.

1.1 Reconciliation Module

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 configurations

Based on the type of data reconciled from the target system, reconciliation can be divided into the following types:

1.1.1 Lookup Fields Reconciliation

Lookup fields reconciliation involves reconciling the Responsibility lookup field.

1.1.2 User Reconciliation

User reconciliation involves reconciling the following fields:

1.1.2.1 Reconciled Resource Object Fields

The following target system fields are reconciled:

  • User ID

  • username

  • E-mail

  • Desc

  • lifeSpanType

  • lifeSpanValue

  • startDate

  • endDate

  • employeeId

  • respName

  • respStartDate

  • respEndDate

1.1.2.2 Reconciled Xellerate User (OIM User) Fields

The following target system fields are reconciled only if trusted source reconciliation is implemented:

  • User ID

  • First Name

  • Last Name

  • Organization

  • User Type

  • Employee Type

1.2 Provisioning Module

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 provisioning

For this target system, the following fields are provisioned:

Note:

During provisioning, if you want to link a newly created user account with an employee account, then you must ensure that the OracleHR.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:

1.3 Supported Functionality

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 Management

1.4 Multilanguage Support

The connector supports the following languages:

See Also:

Oracle Identity Manager Globalization Guide for information about supported special characters

1.5 Files and Directories on the Installation Media

The 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

File in the Installation Media Directory Description
configuration/Oracle EBS User Management-CI.xml

This XML file contains configuration information that is used during connector installation.

config/attributemapping_prov.properties

This file contains the dynamic attributes required for provisioning.

config/attributemapping_recon.properties

This file contains the dynamic attributes required for reconciliation.

config/storedprocedures.properties

This files contains the information regarding the stored procedures and various parameters that are used at the time of provisioning.

lib/xlHostAccess.jar

This file contains the class files that are required for provisioning. During connector deployment, this file is copied into the following directories:

OIM_HOME/xellerate/JavaTasks
lib/xlReconOracleApps.jar

This file contains the class files that are required for reconciliation. During connector deployment, this file is copied into the following directories:

OIM_HOME/xellerate/ScheduleTask

Files in the resources directory

Each of these resource bundles contains language-specific information that is used by the connector. During connector deployment, this file is copied into the following directories:

OIM_HOME/xellerate/connectorResources

Note: A resource bundle is a file containing localized versions of the text strings that are displayed on the user interface of Oracle Identity Manager. These text strings include GUI element labels and messages displayed on the Administrative and User Console.

scripts/OimUserSynonyms.sql

This file contains commands to create synonyms for the OIM wrapper and various tables used in the target system schema for reconciliation.

scripts/OimUserGrants.sql

This file contains commands to provide the required grants to the target system account that is used for connector operations.

scripts/OimUser.sql

This file contains commands to create and configure the target system account that is used for connector operations.

scripts/OIM_FND_USER_PKG.pck

This file contains the package declaration and body for the OIM wrapper for FND_USER_PKG.

scripts/OIM_FND_GLOBAL.pck

This file contains the package declaration and body for the OIM wrapper for FND_GLOBAL.

scripts/OIM.sh
scripts/OIM.bat

This script contains commands to call the SQL files in the scripts directory.

test/config/config.properties

This file contains the parameters required to connect to and perform provisioning on the target system.

test/config/log.properties

This file is used for storing log information.

test/scripts/OracleEbiz.bat
test/scripts/OracleEbiz.sh

This file is used to start the testing utility.

xml/oracleAppsResAdp.xml

This file contains definitions for the following components of the connector:

  • IT resource type

  • IT resource

  • Process form

  • Process tasks and adapters (along with their mappings)

  • Resource object

  • Provisioning process

  • Scheduled tasks for lookup fields and user reconciliation

xml/XellUserOraApps.xml

This XML file contains the configuration for the Xellerate User (OIM User). You must import this file only if you plan to use the connector in trusted source reconciliation mode.


File in the Installation Media Directory Description
configuration/Oracle EBS User Management-CI.xml
This XML file contains configuration information that is used during connector installation.
config/attributemapping_prov.properties
This file contains the dynamic attributes required for provisioning.
config/attributemapping_recon.properties
This file contains the dynamic attributes required for reconciliation.
config/storedprocedures.properties
This files contains the information regarding the stored procedures and various parameters that are used at the time of provisioning.
lib/xlHostAccess.jar
This file contains the class files that are required for provisioning. During connector deployment, this file is copied into the following directories:
OIM_HOME/xellerate/JavaTasks
lib/xlReconOracleApps.jar
This file contains the class files that are required for reconciliation. During connector deployment, this file is copied into the following directories:
OIM_HOME/xellerate/ScheduleTask
Files in the resources directory Each of these resource bundles contains language-specific information that is used by the connector. During connector deployment, this file is copied into the following directories:
OIM_HOME/xellerate/connectorResources

Note: A resource bundle is a file containing localized versions of the text strings that are displayed on the user interface of Oracle Identity Manager. These text strings include GUI element labels and messages displayed on the Administrative and User Console.

scripts/OimUserSynonyms.sql
This file contains commands to create synonyms for the OIM wrapper and various tables used in the target system schema for reconciliation.
scripts/OimUserGrants.sql
This file contains commands to provide the required grants to the target system account that is used for connector operations.
scripts/OimUser.sql
This file contains commands to create and configure the target system account that is used for connector operations.
scripts/OIM_FND_USER_PKG.pck
This file contains the package declaration and body for the OIM wrapper for FND_USER_PKG.
scripts/OIM_FND_GLOBAL.pck
This file contains the package declaration and body for the OIM wrapper for FND_GLOBAL.
scripts/OIM.sh
scripts/OIM.bat
This script contains commands to call the SQL files in the scripts directory.
test/config/config.properties
This file contains the parameters required to connect to and perform provisioning on the target system.
test/config/log.properties
This file is used for storing log information.
test/scripts/OracleEbiz.bat
test/scripts/OracleEbiz.sh
This file is used to start the testing utility.
xml/oracleAppsResAdp.xml
This file contains definitions for the following components of the connector:
  • IT resource type

  • IT resource

  • Process form

  • Process tasks and adapters (along with their mappings)

  • Resource object

  • Provisioning process

  • Scheduled tasks for lookup fields and user reconciliation

xml/XellUserOraApps.xml
This XML file contains the configuration for the Xellerate User (OIM User). You must import this file only if you plan to use the connector in trusted source reconciliation mode.

1.6 Determining the Release Number of the Connector

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:

  1. In a temporary directory, extract the contents of the following JAR file:

    OIM_HOME/xellerate/ScheduleTask/xlReconOracleApps.jar
    
  2. 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.