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 Siebel Enterprise Applications.

This chapter contains the following sections:

• Reconciliation Module

• Provisioning Module

• Supported Functionality

• Multilanguage Support

• Files and Directories on the Installation Media

• Determining the Release Number of the Connector

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, Siebel Enterprise Applications 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:

• Lookup Fields Reconciliation

• User Reconciliation

1.1.1 Lookup Fields Reconciliation

Lookup fields reconciliation involves reconciling the following lookup fields:

• Lookup.Siebel.TimeZone

• Lookup.Siebel.PreferredCommunications

• Lookup.Siebel.Position

• Lookup.Siebel.EmployeeTypeCode

• Lookup.Siebel.Responsibility

• Lookup.Siebel.PersonalTitle

• Lookup.Siebel.UserType

1.1.2 User Reconciliation

User reconciliation involves reconciling the fields discussed in this section.

1.1.2.1 Reconciled Resource Object Fields

The following fields are reconciled:

• UserID

• First Name

• Last Name

• Middle Name

• Alias

• JobTitle

• EmployeeType

• Title

• E-mail

• Fax

• Time Zone

• Position

• Responsibility

• Primary Responsibility

• Preferred Communications

• Extension

• HomePhone

• WorkPhone

• MPosition

1.1.2.2 Reconciled Xellerate User (OIM User) Fields

The following fields are reconciled only if reconciliation is implemented in trusted mode:

• UserID

• FirstName

• LastName

• Email

• Organization

• User Type

• Employee Type

1.2 Provisioning Module

Provisioning involves creating or modifying a user's account 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:

• UserID

• First Name

• Last Name

• Middle Name

• Alias

• Job Title

• EmployeeType

• PersonalTitle

• E-mail

• Fax

• Phone

• Time Zone

• Position

• Primary Responsibility

• Responsibility

• Preferred Communications

• IT Resource Type

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
Delete User	Provisioning	Deletes a user
Add Position to User	Provisioning	Adds a position to a user
Add User Responsibility	Provisioning	Adds a responsibility to a user
Delete User Position	Provisioning	Deletes the position of a user
Delete User Responsibility	Provisioning	Deletes the responsibility of a user
Primary Position Updated	Provisioning	Updates the Primary Position of a user
Primary Responsibility Updated	Provisioning	Updates the Primary Responsibility of a user
Time Zone Updated	Provisioning	Updates the time zone of a user
Email Updated	Provisioning	Updates the e-mail address of a user
Alias Updated	Provisioning	Updates the alias of a user
MI Updated	Provisioning	Updates the middle name of a user
Work Phone Updated	Provisioning	Updates the work phone number of a user
First Name Updated	Provisioning	Updates the first name of a user
Last Name Updated	Provisioning	Updates the last name of a user
Title Updated	Provisioning	Updates the title of a user
Home Phone Updated	Provisioning	Updates the home phone number of a user
Fax Updated	Provisioning	Updates the fax number of a user
Preferred Communications Updated	Provisioning	Updates the preferred communications setting of a user
Extension Updated	Provisioning	Updates the extension number of a user
Employee Type Updated	Provisioning	Updates the role of a user
Job Title Updated	Provisioning	Updates the job title of a user
Reconciliation Delete Received	Reconciliation	Deletes the user from Oracle Identity Manager if the user has been deleted from the target system
Reconciliation Insert Received	Reconciliation	Inserts a user in Oracle Identity Manager
Reconciliation Update Received	Reconciliation	Updates a user in Oracle Identity Manager

See Also:

Appendix A for information about attribute mappings between Oracle Identity Manager and the target system.

1.4 Multilanguage Support

This release of the 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 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/SeibelConnector-CI.xml	This XML file contains configuration information that is used during connector installation.
lib/xlSiebel.jar	This JAR file contains the class files that are required for provisioning. During connector deployment, this file is copied into the following directory: OIM_HOME/xellerate/JavaTasks
lib/SiebelRecon.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 bundles contains language-specific information that is used by the connector. During connector deployment, these resource bundles are 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 user interface of Oracle Identity Manager. These text strings include GUI element labels and messages displayed on the Administrative and User Console.
Troubleshoot/TroubleShootingUtility.class	This is the standalone class that interacts with the target system. This class contains the code for running the troubleshooting test cases.
Troubleshoot/global.properties	This file contains the connection details that are required to connect to the target system. It also contains details about the commands to be run.
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/SiebelEmpResourceObject.xml	This XML file contains definitions for the following connector components: IT resource type Process form Process task and rule-generator adapters (along with their mappings) Resource object Pre-populate rules
xml/SiebelEmpXLResourceObject.xml	This 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 Troubleshoot directory are used only to run tests on the connector.

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/JavaTasks/xlSiebel.jar
   

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

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