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:

• Reconciliation Module

• Supported Functionality

• Multilanguage Support

• Files and Directories That Comprise the Connector

• Determining the Release Number of the Connector

Reconciliation Module

Reconciliation involves duplicating in Oracle Identity Manager additions 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 Framework Guide for conceptual information about reconciliation configurations

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 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, "Configuring the Connector" describes procedures that you can perform to customize the reconciliation module. These procedures involve making changes in the configuration XML file.

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

The connector supports the following languages:

• 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

Files and Directories That Comprise the Connector

The files and directories that comprise this connector are 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.
test/config/config.properties	This file is used to specify the parameters and settings required to connect to the target system by using the testing utility.
test/config/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.
test/scripts/DBTable.bat test/scripts/DBTable.sh	This BAT file or UNIX shell script calls the testing utility when the Oracle Identity Manager server is running Microsoft Windows or UNIX, respectively.
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/DBApp2.xml	For an IBM DB2 UDB 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/MSSQL2005App2.xml	For a Microsoft SQL Server 2005 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/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/DBTable_nonTrusted.xml	This XML file contains definitions for the following connector components: IT resource type Process form Process task and task adapter Resource object
xml/Xellerate Config/DBTable_trusted.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.

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

Determining the Release Number of the Connector

You can use any one of the following methods to determine the release number of the connector.

Before Deployment

To determine the release number of a connector:

1. Extract the contents of the dbadapter.jar file. This file is in the following directory on the installation media:

   Database Servers/Database Application Table/jar
   
   

2. 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.

Note:

If you maintain a copy of the dbadapter.jar file after deployment, you can use this method to determine the release number of the connector at any stage. After you deploy the connector, it is recommended that you use the "After Deployment" method, which is described in the following section.

After Deployment

To determine the release number of a connector that has already been deployed:

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.