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. The connector for SAP Employee Reconciliation 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:

• Supported Functionality

• Multilanguage Support

• Reconciliation Module

• Files and Directories That Comprise the Connector

• Determining the Release Number of the Connector

Supported Functionality

The following table lists the reconciliation functions supported by the 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

Multilanguage Support

In addition to English, this release of the connector supports the following languages:

• French

• Japanese

Reconciliation Module

This section discusses the elements that the reconciliation module extracts from the target system to construct reconciliation event records.

Reconciled SAP Employee Reconciliation Fields

The following fields are reconciled:

• Title

• Password

• ITResourceType

• FirstName

• LastName

• City

• State

• Country

• District

• PostalCode

• TelephoneNumber

• Manager

• StartDate

• EndDate

• Department

• EmailAddress

• EmplUserId

• EmployeeId

• MiddleName

• SSN

• UserLocked

Reconciled Xellerate User Fields

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

• UserID

• Password

• Organization

• FirstName

• LastName

• Xellerate

• Role

• EmailAddress

• EmployeeId

• UserLinked

• MiddleName

Files and Directories That Comprise the Connector

The files and directories that comprise the connector are compressed in the following ZIP file on the installation media:

Enterprise Applications\SAP Enterprise Applications\SAP Employee Reconciliation Rev 3.2.0.zip

These files and directories are listed in the following table.

File in the Installation Media	Description
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. You must import this file only if you plan to use the connector in trusted source reconciliation mode.
lib\xliSAPHR.jar	This JAR file contains the class files that are required for reconciliation.
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.
Files in the resources directory	Each of these files contains locale-specific information that is used by the connector.
troubleshoot\TroubleShootingUtility.class	This utility is used to test connector functionality.
troubleshoot\global.properties	This file is used to specify the parameters and settings required to connect to the target system by using the troubleshooting utility.
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 troubleshooting utility.
docs\B32171_01.pdf	This guide, which provides instructions to deploy the connector.

Note: The files in the troubleshoot directory are used only to run tests on the connector.

The "Step 2: Copying the Connector Files and External Code" section provides instructions to copy these files into the required directories.

Determining the Release Number of the Connector

You can determine the release number of the connector at any of the following stages:

Before Deployment

To determine the release number of the connector before you deploy it:

1. Extract the contents of the xliSAPHR.jar file. This file is in the lib directory inside the installation media directory.

2. Open the manifest.mf file in a text editor, which 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.

Note: If you maintain a copy of the xliSAPHR.jar file after deployment, you can use this method to determine the release number of the connector at any stage. However, after you deploy the connector, it is recommended that you use the After Deployment method.

During Deployment

To determine the release number of the connector while deploying the connector, refer to Step 4 of the procedure described in the "Step 5: Importing the Connector XML File" section.

After Deployment

To determine the release number of the connector after deploying the connector:

See Also: Oracle Identity Manager Design Console Guide

1. Open the Oracle Identity Manager Design Console.

2. In the Form Designer, open the process form. The release number of the connector is the value of the Version field.