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 deployment procedure for the connector that is used to integrate Oracle Identity Manager with database application tables.

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 functions that are available with this connector.

Function	Type	Description
Create User	Provisioning	Creates a user
Delete User	Provisioning	Deletes a user
Enable User or Disable User	Provisioning	Enables or disables a user
Reset User's Password	Provisioning	Resets a user's password
Update User's First Name	Provisioning	Updates a user's first name
Update User's Last Name	Provisioning	Updates a user's last name
Update User's Group	Provisioning	Updates a user's group
Update User's Title	Provisioning	Updates a user's title
Update User's Department	Provisioning	Updates a user's department
Update User's Communication Language	Provisioning	Updates a user's communication language preference
Update User's Logon Language	Provisioning	Updates a user's logon language preference
Update User's Email Address	Provisioning	Updates a user's e-mail address
Update User's Telephone Number	Provisioning	Updates a user's telephone number
Update User's Time Zone	Provisioning	Updates a user's time zone
Update User's Date Format	Provisioning	Updates a user's date format
Update User's Role	Provisioning	Updates a user's role
Create User (Account Discovery)	Reconciliation	Reconciles new user accounts
Delete User	Reconciliation	Reconciles user accounts that are deleted from the target system
Enable User or Disable User	Reconciliation	Reconciles user accounts that are enabled or disabled
Reset User's Password	Reconciliation	Reconciles user accounts with modified password
Update User's First name	Reconciliation	Reconciles user accounts with modified first name
Update User's Last Name	Reconciliation	Reconciles user accounts with modified last name
Update User's Group	Reconciliation	Reconciles user accounts with modified group
Update User's Title	Reconciliation	Reconciles user accounts with modified title
Update User's Department	Reconciliation	Reconciles user accounts with modified department
Update User's Communication Language	Reconciliation	Reconciles user accounts with modified communication language preference
Update User's Logon Language	Reconciliation	Reconciles user accounts with modified logon language preference
Update User's Email Address	Reconciliation	Reconciles user accounts with modified e-mail address
Update User's Telephone Number	Reconciliation	Reconciles user accounts with modified telephone number
Update User's Time Zone	Reconciliation	Reconciles user accounts with modified time zone
Update User's Date Format	Reconciliation	Reconciles user accounts with modified date format
Update User's Decimal Notation	Reconciliation	Reconciles user accounts with modified decimal notation
Update User's Role	Reconciliation	Reconciles user accounts with modified role

Multilanguage Support

This release of the connector supports the following languages:

English
Brazilian Portuguese
French
German
Italian
Japanese
Korean
Simplified Chinese
Spanish
Traditional Chinese

Reconciliation Module

The reconciliation module handles the reconciliation of new, updated, and deleted user profiles in the target database application. A reconciliation event is created for each user profile to be reconciled.

You can use a configuration XML file to enable or disable the reconciliation of created, updated, and deleted users. The default data fields of each reconciliation event record are taken from this XML file.

The various configuration XML files that are shipped with this connector are introduced in the "Files and Directories That Comprise the Connector" section. Chapter 3, "Customizing the Connector" describes procedures that you can perform to customize the reconciliation module. These procedures involve making changes in the configuration XML file.

Files and Directories That Comprise the Connector

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

Database Servers\Database Application Table

These files and directories are listed in the following table.

File in the Installation Media Directory	Description
jar\dbadapter.jar	This JAR file contains the class files that are used to implement provisioning and reconciliation.
Files in the `resources` directory	Each of these resource bundle files contains language-specific information that is used by the connector. 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.
Files in the `xml\DB Schema XML` directory	These files contain information about the configuration of the target database schema mapping.
xml\DB Schema XML\OraApp1.xml	For an Oracle Database installation, you must use this configuration XML file if all the user attributes are stored in a single table. If you use this file, then you cannot update the attributes of users you disable during provisioning.
xml\DB Schema XML\OraApp2.xml	For an Oracle Database installation, you must use this configuration XML file if all the user attributes are stored in two tables, a parent table and a child table. Note: In this guide, the `OraApp2.xml` file has been used to illustrate some of the procedures described in this guide.
xml\DB Schema XML\OraPerf1.xml	For an Oracle Database installation, you must use this configuration XML file if all the user attributes are stored in a single table. If you use this file, then you can update the attributes of users, regardless of whether or not the user accounts are disabled.
xml\DB Schema XML\SybApp1.xml	For a Sybase installation, you must use this configuration XML file if all the user attributes are stored in a single table.
xml\DB Schema XML\SybApp2.xml	For a Sybase installation, you must use this configuration XML file if all the user attributes are stored in two tables, a parent table and a child table.
xml\DB Schema XML\xdb_app_map.xsd	This XML file contains information about the validation rules of the configuration XML files that are placed in the same directory.
xml\Xellerate Config\DBTablesresadp.xml	This XML file contains definitions for the following connector components: IT resource type Process form Process task and task adapter Resource object

The "Step 3: 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

To determine the release number of the connector that you have deployed:

Extract the contents of the dbadapter.jar file. For a connector that has been deployed, this file is in the following directory:
```
OIM_home\xellerate\JavaTasks
```
Open the manifest.mf file in a text editor. The manifest.mf file is one of the files bundled inside the dbadapter.jar file.

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