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

Note:

Oracle Identity Manager connectors were referred to as resource adapters prior to the acquisition of Thor Technologies by Oracle.

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, SAP 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:

1.1.1 Reconciled SAP Employee Reconciliation Fields

The following fields are reconciled:

  • Title

  • FirstName

  • LastName

  • City

  • State

  • Country

  • District

  • PostalCode

  • TelephoneNumber

  • Manager

  • StartDate

  • EndDate

  • Department

  • EmailAddress

  • EmplUserId

  • EmployeeId

  • MiddleName

  • SSN

  • UserLocked

  • UserLinked

1.1.2 Reconciled Xellerate User (OIM User) Fields

If trusted source reconciliation is implemented, then the following fields are reconciled:

  • User ID

  • FirstName

  • LastName

  • Middle Name

  • Organization

  • Email

  • Employee Type

  • User Type

  • LinkedUserID

  • UserFromHRMS

1.2 Supported Functionality

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

Function Description
Create User Creates a user in Oracle Identity Manager
Delete User Deletes a user in Oracle Identity Manager
Disable User Disables a user in Oracle Identity Manager
Enable User Enables a user in Oracle Identity Manager
Update User Updates a user in Oracle Identity Manager

See Also:

Appendix A for information about attribute mappings between Oracle Identity Manager and SAP Employee Reconciliation

1.3 Multilanguage Support

This release of the connector supports the following languages:

  • Arabic

  • Chinese Simplified

  • Chinese Traditional

  • English

  • French

  • German

  • Italian

  • Japanese

  • Korean

  • Portuguese (Brazilian)

  • Spanish

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 Description 
configuration/SAPHRMS-CI.xml

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

 
BAPI/xlhsapcar.sar

This file is extracted and the components are deployed on the SAP Employee Reconciliation server for the connector to work with SAP Employee Reconciliation.

 
lib/xliSAPHR.jar

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

OIM_HOME/xellerate/ScheduleTask

Files in the resources directory

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

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.

 
test/troubleshoot/troubleShootingUtility.class

This utility is used to test connector functionality.

 
test/troubleshoot/global.properties

This file is used to specify the parameters and settings required to connect to the target system by using the testing utility.

 
test/troubleshoot/log.properties

This file is used to specify the log level and the directory in which the log file is to be created when you run the testing utility.

 
xml/SAPHRResourceObject.xml

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

  • IT resource type

  • Custom process form

  • Process task and adapters (along with their mappings)

  • Resource object

  • Provisioning process

  • Pre-populate rules

  • Reconciliation process

  • Lookup definitions

 
xml/SAPHRXLResourceObject.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.

Note:

The files in the test directory are used only to run tests on the connector.

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/xliSAPHR.jar

  2. Open the manifest.mf file in a text editor. The manifest.mf file is one of the files bundled inside the xliSAPHR.jar file.

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