Skip Headers
Oracle® Identity Manager Connector Guide for Oracle E-Business Employee Reconciliation
Release 9.0.4

E10434-05
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
PDF · Mobi · ePub

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 Employee Reconciliation.

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 Employee Reconciliation 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:

The following section discusses the tables created by the connector in the APPS schema during the reconciliation process:

1.1.1 Lookup Fields Reconciliation

Lookup fields reconciliation involves reconciling the Person ID lookup field.

1.1.2 Employee Reconciliation

Employee reconciliation involves reconciling the following fields:

1.1.2.1 Reconciled Resource Object Fields

The following target system fields are reconciled:

  • First Name

  • email

  • PersonId

  • Middle Name

  • Last Name

  • Dept

  • SSN

  • Title

  • Location

  • Manager

  • City

  • PostalCode

  • Country

  • Telno

  • EmployeeNumber

  • ManagerId

  • Nationality

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.1.3 Tables Used During Reconciliation

The following table are created by the connector and used during reconciliation:

1.1.3.1 gl_temp_tab Table

The gl_temp_tab table is a temporary table created in the APPS schema during reconciliation. This table is populated by the SQL query that is stored in the getNewEmps variable of the query.properties file. This table contains the following columns:

  • RECNUM (NUMBER data type)

  • person_id (NUMBER data type)

  • LAST_UPDATE_DATE (DATE data type)

The gl_temp_tab table is dropped at the end of each reconciliation run.

1.1.3.2 XELLERATE_TEMP_EMP Table

The XELLERATE_TEMP_EMP table is created in the APPS schema at the start of the first reconciliation run. It contains the person_id column. This table is populated by the SQL query that is stored in the getNewEmps variable of the query.properties file. The person ID values stored in this table are copied from the per_all_people_f table of the APPS schema. From the second reconciliation run onward, the following steps are automatically performed:

  1. Person ID values in the per_all_people_f table are compared with the ones in the XELLERATE_TEMP_EMP table. The person IDs that exist in XELLERATE_TEMP_EMP table and do not exist in the per_all_people_f table represent the accounts that have been deleted after the last reconciliation run.

  2. Person IDs of the deleted accounts are sent to Oracle Identity Manager for deletion.

  3. The rows of the XELLERATE_TEMP_EMP table are deleted and the existing rows of the per_all_people_f table are copied into the XELLERATE_TEMP_EMP table.

1.2 Supported Functionality

The following table lists the functions that are available with this connector.

Function Type Description
Reconcile New User Reconciliation Creates an Oracle Identity Manager user in trusted mode
Reconcile Delete User Reconciliation Deletes an Oracle Identity Manager user account, in both trusted source and target resource mode
Reconcile Updated User Reconciliation Updates an Oracle Identity Manager user record during reconciliation, in both trusted source and target resource mode

See Also:

Appendix A for information about attribute mappings between Oracle Identity Manager and Oracle E-Business Employee Reconciliation.

1.3 Multilanguage Support

The connector supports the following languages:

See Also:

Oracle Identity Manager Globalization Guide for information about supported special characters

1.4 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 Employee Reconciliation-CI.xml

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

config/attributemapping_recon.properties

This file contains values for the attributes required for reconciliation.

config/query.properties

This file contains the queries used for reconciliation.

lib/xlReconOraHREmp.jar

This JAR 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 Administrative and User Console. These text strings include GUI element labels and messages.

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.sh
scripts/OIM.bat

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

xml/oracleHRResAdp.xml

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

  • IT resource type

  • IT resource

  • Provisioning process

  • Resource object

  • Scheduled tasks for user and lookup fields reconciliation

xml/XellOraEmp.xml

This XML file contains definitions of the resource object and scheduled task for trusted source reconciliation.


1.5 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/xlReconOralHREmp.jar
    
  2. Open the manifest.mf file in a text editor. The manifest.mf file is one of the files bundled inside the xlReconOralHREmp.jar file.

    In the manifest.mf file, the release number of the connector is displayed as the value of the Version property.