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:

Reconciliation Module
Provisioning 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

Based on the type of data reconciled from the target system, 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:

Reconciled Resource Object Fields

The following target system fields are reconciled:

FirstName
MiddleName
LastName
ShortName
OrgUnit
MailInternetAddress
Location
Comment
ForwardDomain
SecurityType
GrpName
OldLastName
OldFirstName
OldMiddleName
OldOrgUnit

Reconciled Xellerate User Fields

The following target system fields are reconciled only if trusted source reconciliation is implemented:

User ID
First Name
Last Name
Organization
User Type
Employee Type

Provisioning Module

Provisioning involves creating or modifying a user's account information on the target system through Oracle Identity Manager. You use the Administrative and User Console to perform provisioning operations.

See Also:

The "Deployment Configurations of Oracle Identity Manager" section in Oracle Identity Manager Connector Framework Guide for conceptual information about provisioning

For this target system, the following fields are provisioned:

FirstName
MiddleName
LastName
ShortName
Password
OrgUnit
MailInternetAddress
Location
Comment
ForwardDomain
EndDate
SecurityType
Grp
ID File Name

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 Organizational Unit	Provisioning	Updates the organizational 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 (or updates) 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 Organizational Unit

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:

Collaboration and Messaging Applications/IBM Lotus Notes Domino

These files and directories are listed in the following table.

File in the Installation Media Directory	Description
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 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/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/config/attributemapping_prov.properties	This file contains the parameters required for provisioning.
test/config/attributemapping_recon.properties	This file contains the parameters required for reconciliation.
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/adminP.properties	This file is used to specify a value for an AdminP command that is run on the Domino server.
test/scripts/lotusNotes.bat	This file contains the script required for running test calls from the Oracle Identity Manager server.
test/scripts/lotusNotes.sh	This file contains the script required for running test calls from the Oracle Identity Manager server.
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.
xml/xlLotusNotesConnector.xml	This XML file contains definitions for the following components of the connector: IT resource type IT resource Resource object Process definition Process tasks Adapters Process form

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:

Extract the contents of the xlLotusNotesRecon.jar file. This file is in the following directory on the installation media:
```
Collaboration and Messaging Applications/IBM Lotus Notes Domino/lib/ScheduleTask
```
Open the manifest.mf file in a text editor. The manifest.mf file 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.

Note:

If you maintain a copy of the xlLotusNotesRecon.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

Open the Oracle Identity Manager Design Console.
In the Form Designer, open the process form. The release number of the connector is the value of the Version field.