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 IBM Lotus Notes and Domino is used to integrate Oracle Identity Manager with IBM Lotus Notes and Domino.

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

• Provisioning Module

• Files and Directories That Comprise the Connector

• Determining the Release Number of the Connector

• Converting Existing Date Values While Upgrading the Connector

Supported Functionality

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

Function	Type	Description
Add User	Provisioning	Creates a user
Delete User	Provisioning	Deletes a user
Update User Last Name	Provisioning	Updates the last name of a user
Update User First Name	Provisioning	Updates the first name of a user
Update User Middle Name	Provisioning	Updates the middle name of a user
Update User Organization Unit	Provisioning	Updates the organization unit of a user
Update User Short Name	Provisioning	Updates the short name of a user
Update User Mail Internet Address	Provisioning	Updates the e-mail address of a user
Update User Location	Provisioning	Updates the location of a user
Update User Comment	Provisioning	Updates the comment of a user
Update User Forward Domain	Provisioning	Updates the e-mail address to which e-mail for the user must be forwarded
Update User Password	Provisioning	Updates the user password and resets the ID file
Disable User	Provisioning	Disables a user
Enable User	Provisioning	Enables a user
Reconcile lookup field	Reconciliation	Reconciles the lookup fields
Reconcile User Data	Reconciliation	Trusted mode: Reconciles user data from IBM Lotus Notes and Domino to Oracle Identity Manager. A corresponding user is created in Oracle Identity Manager. If the user already exists in Oracle Identity Manager, then this user is updated. Nontrusted mode: Reconciles user data from IBM Lotus Notes and Domino to Oracle Identity Manager. A user is not created in Oracle Identity Manager.

Note: The Delete User provisioning function is implemented by using the DeleteUser Administration Process (AdminP) function of IBM Lotus Notes and Domino. Similarly, the RenameNotesUser AdminP function is used to implement the following provisioning functions: Update User Last Name Update User First Name Update User Middle Name Update User Organization Unit

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.

Reconciliation can be divided into the following types:

• Lookup Fields Reconciliation

• User Reconciliation

Lookup Fields Reconciliation

Lookup fields reconciliation involves reconciling the Group lookup field.

User Reconciliation

User reconciliation involves reconciling the following fields:

• FirstName

• MiddleName

• LastName

• ShortName

• OrgUnit

• MailInternetAddress

• Location

• Comment

• ForwardDomain

• SecurityType

• GrpName

• OldLastName

• OldFirstName

• OldMiddleName

• OldOrgUnit

Provisioning Module

The following fields of IBM Lotus Notes and Domino are provisioned:

• FirstName

• MiddleName

• LastName

• ShortName

• Password

• OrgUnit

• MailInternetAddress

• Location

• Comment

• ForwardDomain

• EndDate

• SecurityType

• Grp

Files and Directories That Comprise the Connector

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

Collaboration and Messaging Applications\IBM Lotus Notes Domino\IBM Lotus Notes Domino Rev 1.2.0.zip

These files and directories are listed in the following table.

File in the Installation Media Directory	Description
xml\xlLotusNotesConnector.xml	This XML file contains definitions for the following components of the connector: IT resource type Process form Process task and rule-generator adapters (along with their mappings) Resource object
xml\xlLotusNotes_XellerateUser.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\JavaTask\xlLotusNotesProvision.jar	This JAR file contains the class files that are used to implement provisioning.
lib\ScheduleTask\xlLotusNotesRecon.jar	This JAR file contains the class files that are used to implement reconciliation.
Files in the resources directory	Each of these files contains locale-specific information that is used by the connector.
docs\B32156_01.pdf	This guide, which provides instructions to deploy the connector.

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:

1. Extract the contents of the xlLotusNotesRecon.jar file. This file is in the lib\ScheduleTask 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 xlLotusNotesRecon.jar file.

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

Converting Existing Date Values While Upgrading the Connector

If you are upgrading from release 9.0.1 to release 9.0.2 of the connector and you want to migrate user data, then you must ensure that the migration scripts convert values stored in the UD_LOTUS_ENDDATE column from VARCHAR2 to DATE format. In the earlier release, values were stored in the DD/MM/YY format as a string literal in this column.