Skip Headers
Oracle® Identity Manager Connector Guide for IBM Lotus Notes and Domino
Release 9.0.4

Part Number E10428-07
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
View PDF

2 Deploying the Connector

Deploying the connector involves the following steps:

2.1 Verifying Deployment Requirements

The following table lists the deployment requirements for the connector.

Item Requirement
Oracle Identity Manager Oracle Identity Manager release 8.5.3.1 or later
Target systems IBM Lotus Notes/Domino 6.5, 7.x, 8.0.x, 8.5
External code
NCSO.jar
Notes.jar
Refer to the "Copying the Connector Files" section for more information about these files.
Target system user account Domino Server administrator

You must ensure that full administrative access has been assigned to this administrator account. In other words, this administrator must belong to the Full Access Administrator list.

You provide the credentials of this user account while configuring the IT resource. The procedure is described later in this guide.

If this user account is not assigned the specified privileges, then the following error message is displayed when Oracle Identity Manager tries to exchange data with the target system:

Invalid User Name


2.2 Using External Code Files

Note:

While installing Oracle Identity Manager in a clustered environment, you copy the contents of the installation directory to each node of the cluster. Similarly, you must copy the contents of the connectorResources directory and the JAR files to the corresponding directories on each node of the cluster.

Copy the following files into the java_installation/jre/lib/ext directory:

Here, java_installation is the JDK directory used for Oracle Identity Manager and LOTUS_HOME is the directory in which IBM Lotus Notes and Domino is installed.

You must also copy the NCSO.jar and the Notes.jar files into the OIM_HOME/xellerate/ThirdParty directory before running the testing utility of the connector. The "Testing the Connector" section describes the procedure to use the testing utility.

2.3 Configuring the Target System

Configuring the target system involves performing the following steps:

2.3.1 Creating a Deny Access Group

When you disable a user account in IBM Lotus Notes and Domino, that user automatically becomes a member of a Deny Access group. When you reenable the user account, the user is removed from the Deny Access group. The same process is followed when you disable a user account through Oracle Identity Manager. For the Disable User operation to work, there must be at least one Deny Access group in the target system.

If there is no Deny Access group on the IBM Lotus Notes and Domino installation, then you must create one as follows:

  1. Log in to the Lotus Notes client as the administrator.

  2. On the People & Groups tab, click the Groups folder on the left pane.

  3. Click Add Group.

  4. On the New Group tab, provide the following values:

    • Group name: Specify a name for the group, for example, noaccess.

    • Group type: Select Multi-purpose.

  5. Click Save & Close.

  6. On the Configuration tab, click All Server Documents on the left pane.

  7. On the right pane, double-click the row for the server that you are using.

  8. Open the Security tab.

  9. In the Server Access section, double-click Not Access Server.

  10. In the Select Names dialog box, use the Add button to add the group that you create in Step 4 and then click OK.

  11. Click Save & Close.

The Deny Access group that you create can be viewed by performing Steps 6 through 9.

While configuring the IT resource, you specify the name of the Deny Access group (for example, noaccess) that you create in Step 4 as the value of the DenyAccessGroupName IT resource parameter.

2.3.2 Enabling Modification of ID Files

Note:

If you do not want to support encrypted e-mail on the target system, then you can skip this section.

When you create a user account in IBM Lotus Notes and Domino, an ID file is automatically generated for the user account. This ID file holds the encryption key for the user, and it is automatically used when encrypted e-mail is sent or received.

If an administrator changes the user's password in Oracle Identity Manager, then a new ID file is created. This new ID file cannot be used to open existing sent and received encrypted e-mail. From this point onward, existing encrypted e-mail becomes inaccessible.

To avoid this situation, you must:

  1. Configure an agent on IBM Lotus Notes and Domino that modifies existing ID files when the password is updated. This section describes the procedure to configure an agent.

  2. Set the value of the isAgentInstalled IT resource parameter to Yes to indicate that an agent has been configured on IBM Lotus Notes and Domino. This parameter is described later in this guide.

To configure the agent on IBM Lotus Notes and Domino:

  1. Log in to the Lotus Domino Administrator client.

  2. Depending on the target system version that you use, perform one of the following steps:

    • For IBM Lotus Notes and Domino Server 6.5, 7.x:

      From the File menu, select Database and then select Open.

    • For IBM Lotus Domino Server 8.0.x, and 8.5:

      From the File menu, select Application and then select Open.

  3. In the Open Database dialog box, select the name of the Domino server from the Server list.

  4. In the FileName field, enter names.nsf and then click Open.

    Note:

    The IBM Lotus Notes Domino connector does not support multiple Notes Address Books. Only the default address book (names.nsf) is supported.
  5. From the View menu, select Agents.

  6. Click New Agent.

  7. On the first tab of the Agent dialog box (indicated by a bulb icon), enter the following values:

    Name: Enter changePassword.

    Comment: Enter Change password of the ID file.

    Target: Select All documents in database.

  8. On the second tab of the Agent dialog box (indicated by a key icon), select Allow restricted operations from the Set runtime security level list.

  9. Close the dialog box.

  10. On the changePassword-Agent tab, select LotusScript from the second list.

  11. From the menu on the Objects pane, select the [Options] method.

  12. Open the following file in the installation media directory:

    script/lotusagent.txt
    
  13. Copy the LotusScript code from the lotusagent.txt file to the right pane of the Lotus Notes client window.

  14. From the File menu, select Save.

You specify the credentials of a Lotus Notes administrator account in the IT resource definition. After you configure the agent on IBM Lotus Notes and Domino, you must ensure that this Lotus Notes administrator account has the permissions required to update the ID files as follows:

  1. Log in to the Lotus Domino Administrator client.

  2. Depending on the target system version that you use, perform one of the following steps:

    • For IBM Lotus Notes and Domino Server 6.5, 7.x:

      From the File menu, select Database and then select Open.

    • For IBM Lotus Domino Server 8.0.x, 8.5:

      From the File menu, select Application and then select Open.

  3. Select the Lotus Notes administrator account that you are using to connect to the Domino server.

  4. In the Access Control List dialog box, select Manager from the Access list and then select the Delete documents check box.

  5. Click OK.

2.3.2.1 Additional Functionality Changes Related to the ID Files

The following fields have been added on the user process form:

  • ID File Name

    You can use the ID File Name field to specify a name for the ID file while creating a user account.

  • Old Password

    The Old Password field stores the latest password of the user in encrypted form. The value of this field is changed automatically during Create Password and Update Password provisioning operations.

    Note:

    After reconciliation, for user accounts for which the password has been changed on the target system, the users must manually enter the new password in this field on Oracle Identity Manager.

2.3.3 Ensuring That the Domino IIOP (DIIOP) Task Is Running

To ensure that the Domino IIOP (DIIOP) task is running, open the IBM Lotus Notes and Domino console and run the Load DIIOP command.

If the DIIOP task was not running, then it is started after you run the command. If it was running, then a message that the task has already been started is displayed.

2.4 Installing the Connector on Oracle Identity Manager Release 9.1.0 or Later

Note:

In this guide, the term Connector Installer has been used to refer to the Connector Installer feature of the Oracle Identity Manager Administrative and User Console.

Installing the connector on Oracle Identity Manager release 9.1.0 or later involves the following procedures:

2.4.1 Running the Connector Installer

To run the Connector Installer:

  1. Copy the contents of the connector installation media into the following directory:

    OIM_HOME/xellerate/ConnectorDefaultDirectory
    
  2. Log in to the Administrative and User Console by using the user account described in the "Creating the User Account for Installing Connectors" section of Oracle Identity Manager Administrative and User Console.

  3. Click Deployment Management, and then click Install Connector.

  4. From the Connector List list, select IBM Lotus Notes Domino RELEASE_NUMBER. This list displays the names and release numbers of connectors whose installation files you copy into the default connector installation directory:

    OIM_HOME/xellerate/ConnectorDefaultDirectory 
    

    If you have copied the installation files into a different directory, then:

    1. In the Alternative Directory field, enter the full path and name of that directory.

    2. To repopulate the list of connectors in the Connector List list, click Refresh.

    3. From the Connector List list, select IBM Lotus Notes Domino RELEASE_NUMBER.

  5. Click Load.

  6. To start the installation process, click Continue.

    The following tasks are performed in sequence:

    1. Configuration of connector libraries

    2. Import of the connector Target Resource user configuration XML file (by using the Deployment Manager). If you want to import the target system as a trusted source for reconciliation, then see "Configuring the Target System As a Trusted Source".

    3. Compilation of adapters

    On successful completion of a task, a check mark is displayed for the task. If a task fails, then an X mark and a message stating the reason for failure are displayed. Depending on the reason for the failure, make the required correction and then perform one of the following steps:

    • Retry the installation by clicking Retry.

    • Cancel the installation and begin again from Step 0.

  7. If all three tasks of the connector installation process are successful, then a message indicating successful installation is displayed. In addition, a list of the steps that you must perform after the installation is displayed. These steps are as follows:

    1. Ensuring that the prerequisites for using the connector are addressed

      Note:

      At this stage, run the PurgeCache utility to load the server cache with content from the connector resource bundle in order to view the list of prerequisites. Refer to "Clearing Content Related to Connector Resource Bundles from the Server Cache" for information about running the PurgeCache utility.

      There are no prerequisites for some predefined connectors.

    2. Configuring the IT resource for the connector

      Record the name of the IT resource displayed on this page. The procedure to configure the IT resource is described later in this guide.

    3. Configuring the scheduled tasks that are created when you installed the connector

      Record the names of the scheduled tasks displayed on this page. The procedure to configure these scheduled tasks is described later in this guide.

  8. Copy the files in the config directory on the installation media to the OIM_HOME/xellerate/XLIntegrations/LotusNotes/config directory.

When you run the Connector Installer, it copies the connector files and external code files to destination directories on the Oracle Identity Manager host computer. These files are listed in Table 1-1.

Installing the Connector in an Oracle Identity Manager Cluster

While installing Oracle Identity Manager in a clustered environment, you must copy all the JAR files and the contents of the connectorResources directory into the corresponding directories on each node of the cluster. See Table 1-1 for information about the files that you must copy and their destination locations on the Oracle Identity Manager server.

2.4.2 Configuring the IT Resource

Note:

Perform this procedure if you are installing the connector on Oracle Identity Manager release 9.1.0 or later.

You must specify values for the parameters of the Lotus Notes IT resource as follows:

  1. Log in to the Administrative and User Console.

  2. Expand Resource Management.

  3. Click Manage IT Resource.

  4. In the IT Resource Name field on the Manage IT Resource page, enter LotusNotes and then click Search.

  5. Click the edit icon for the IT resource.

  6. From the list at the top of the page, select Details and Parameters.

  7. Specify values for the parameters of the IT resource. The following table describes each parameter:

    Parameter Description
    AddBook Specifies whether or not the server entry in the Domino Directory is updated when the ID file is created

    The value can be True or False. The default value is True.

    Domino Directory is the database that contains user personal documents, connection documents, server documents, and cross-certification files. This directory is also known as the public address book or names.nsf.

    Admin User ID of the IBM Lotus Notes and Domino server administrator

    This administrator must belong to the Full Access Administrator list on IBM Lotus Notes and Domino.

    AdminPwd Password of the administrator
    certifierOU Specifies the OU of the certifier to be used when creating user accounts

    If you use a certifier on the target system, then you must specify the certifier OU value. If you do not have a certifier on the target system, then leave this parameter field empty.

    If there are multiple certifiers on the target system, then you must create one IT resource (of the Lotus Notes IT resource type) for each certifier. Refer to Oracle Identity Manager Design Console Guide for information about creating IT resources.

    If you specify a value for the certifierOU parameter, then the user OU value that you specify on the process form is ignored during the creation of a DN for a new user account. If you do not specify a value for the certifierOU parameter, then the user OU value that you specify on the process form is used in the DN. This feature ensures that only one OU value is included in the DN.

    If you specify a value for the certifierOU IT resource parameter, then user records for which the certifier OU value in the DN does not match the certifierOU parameter value are not reconciled. This is because the user DN is used to match records in the target system and Oracle Identity Manager, and a difference in the certifier OU value would lead to a mismatch in DN values. The following example illustrates this type of scenario:

    Suppose a user account on Lotus Notes has the following DN:

    CN=John Doe/OU=testcertou/O=test/C=US
    

    If testcertou has not been assigned as the value of the certifierOU parameter for any of the IT resources created on this Oracle Identity Manager installation, then the records of this user cannot be reconciled into Oracle Identity Manager.

    Sample value: NY

    CertPath Complete file specification of the certifier ID to be used when creating certifier ID files

    Sample value: C:\Lotus\Domino\Data\cert.id

    CertPwd Password of the certifier ID file
    Create Mail ID File Specifies whether or not a mail database is created with the ID file when calling the Register New User function of IBM Lotus Notes and Domino

    The value can be True or False. The default value is True.

    Host Host name or IP address of the IBM Lotus Notes and Domino server
    Port TCP/IP port at which the IBM Lotus Notes and Domino server is listening

    The default value is 63148.

    IDFilePath Path for storing the ID files
    IDType Type of ID files to be created

    The value can be HIERARCHICAL or CERTIFIER.

    The default is 172 (HIERARCHICAL). The numeric value for CERTIFIER is 173.

    MailDBPath Mail file path
    MailOwnerAccess Mail database ACL setting for the owner

    The value can be one of the following:

    • 0: MANAGER

    • 1: DESIGNER

    • 2: EDITOR

    The default value is 0.

    MailQuotaLimit Maximum size of the user's e-mail database, in megabytes

    The default value is 50.

    MailQuotaWarning Size, in megabytes, at which the user's mail database issues a warning that the size limit may be exceeded

    The default value is 40.

    MailServer Canonical name of the server containing the user's mail file

    Sample value: CN=ServerName/O=OrgName

    Note: You must enter a value for this parameter.

    MailSystem User's mail system

    The value can be any one of the following:

    • 0: NOTES

    • 3: INOTES

    • 4: INTERNET

    The default value is 0.

    MailTemplateName Name of the template for the mail file
    PasswordLength Minimum number of characters that can be used in the password

    The value can be any number. The default minimum length is 5 characters.

    RegLog Name of the log file to be used when creating IDs

    The default value is log.nsf.

    RegServer Name of the server to be used when creating IDs and performing other registration functions
    StoreAddBook Indicates whether or not the ID file is stored in the Domino Directory of the server

    The value can be True or False. The default value is True.

    Sync Internet Password Specifies whether or not the user can use the same password for both local client-based access and Web-based access to IBM Lotus Notes and Domino

    The value can be True or False. The default value is True.

    IsSecure Specifies whether or not the SSL feature is enabled

    The value can be Yes or No. The default value is Yes.

    Note: It is recommended that you enable SSL to secure communication with the target system.

    DenyAccessGroupName Name of the group for users whose accounts have been disabled

    Note: If there is no Deny Access group on the IBM Lotus Notes and Domino installation, then you must create one by performing the procedure described in the "Creating a Deny Access Group" section.

    triggerAdminp Specifies whether or not the Trigger AdminP feature is enabled

    The value can be Yes or No. The default value is Yes.

    isAgentInstalled Specify Yes as the value of this parameter if you want to enable support for encrypted e-mail on the target system. Otherwise, specify No.

    See Also: The "Enabling Modification of ID Files" section for more information about this parameter.

    TrustedTimeStamp This parameter is used for trusted source reconciliation.

    Starting with the first reconciliation run, this parameter stores the time-stamp value at which the reconciliation run ends.

    The default value is None. Do not change it.

    NonTrustedTimeStamp This parameter is used for target resource reconciliation.

    Starting with the first reconciliation run, this parameter stores the time-stamp value at which the reconciliation run ends.

    The default value is None. Do not change it.

    Max Retries Number of times that the Lotus Notes Connector should retry connecting to the target server if the connection fails

    The default value is 2.

    Delay Delay (in milliseconds) before the connector attempts to retry connecting to the target system, in case the connection fails

    The default value is 10000.

    TerminatedGroupName Specifies the Terminated User group to which users who are deleted must be assigned
    ImmediateDelete Use this parameter to specify how the Delete User provisioning operation must be performed. You can specify one of the following values:
    • Enter Yes if you want all references to the user in the Domino Directory to be deleted before an administration process request is issued.

    • Enter No if you want to let the administration process make all required deletions.

    MailFileActionForDelete Use this parameter to specify how mail file deletion must be performed when a user is deleted.

    You can specify one of the following values:

    • Enter Delete All if you want the mail file on the user's home server and all replicas of the mail file to be deleted.

    • Enter Delete Home if you want the mail file on the user's home server to be deleted.

    • Enter Delete None if you do not want the user's mail file to be deleted.


  8. To save the values, click Update.

2.5 Installing the Connector on Oracle Identity Manager Release 8.5.3.1 Through 9.0.3.x

Installing the connector on any Oracle Identity Manager release between releases 8.5.3.1 and 9.0.3.x involves the following procedures:

2.5.1 Copying the Connector Files

The connector files to be copied and the directories to which you must copy them are given in the following table.

See Also:

"Files and Directories on the Installation Media" section for more information about these files
File in the Installation Media Directory Destination Directory
Files in the config directory
OIM_HOME/xellerate/XLIntegrations/LotusNotes/config
lib/xlLotusNotesProvision.jar
OIM_HOME/xellerate/JavaTasks
lib/xlLotusNotesRecon.jar
OIM_HOME/xellerate/ScheduleTask
Files in the resources directory
OIM_HOME/xellerate/connectorResources
Files in the test/config directory
OIM_HOME/xellerate/XLIntegrations/LotusNotes/config
Files in the test/scripts directory
OIM_HOME/xellerate/XLIntegrations/LotusNotes/scripts
Files in the xml directory
OIM_HOME/xellerate/XLIntegrations/LotusNotes/xml

Note:

In a clustered environment, copy the JAR files and the contents of the connectorResources directory to the corresponding directories on each node of the cluster.

2.5.2 Importing the Connector XML File

To import the connector XML file into Oracle Identity Manager:

  1. Open the Oracle Identity Manager Administrative and User Console.

  2. Click the Deployment Management link on the left navigation bar.

  3. Click the Import link under Deployment Management. A dialog box for opening files is displayed.

  4. Locate and open the xlLotusNotesConnector.xml file, which is in the OIM_HOME/xellerate/XLIntegrations/LotusNotes/xml directory. Details of this XML file are shown on the File Preview page.

  5. Click Add File. The Substitutions page is displayed.

  6. Click Next. The Confirmation page is displayed.

  7. Click Next. The Provide IT Resource Instance Data page for the LotusNotes IT resource is displayed.

  8. Specify values for the parameters of the LotusNotes IT resource. Refer to the following table for information about the values to be specified:

    Parameter Description
    AddBook Specifies whether or not the server entry in the Domino Directory is updated when the ID file is created

    The value can be True or False. The default value is True.

    Domino Directory is the database that contains user personal documents, connection documents, server documents, and cross-certification files. This directory is also known as the public address book or names.nsf.

    Admin User ID of the IBM Lotus Notes and Domino server administrator

    This administrator must belong to the Full Access Administrator list on IBM Lotus Notes and Domino.

    AdminPwd Password of the administrator
    certifierOU Specifies the OU of the certifier to be used when creating user accounts

    If you use a certifier on the target system, then you must specify the certifier OU value. If you do not have a certifier on the target system, then leave this parameter field empty.

    If there are multiple certifiers on the target system, then you must create one IT resource (of the Lotus Notes IT resource type) for each certifier. Refer to Oracle Identity Manager Design Console Guide for information about creating IT resources.

    If you specify a value for the certifierOU parameter, then the user OU value that you specify on the process form is ignored during the creation of a DN for a new user account. If you do not specify a value for the certifierOU parameter, then the user OU value that you specify on the process form is used in the DN. This feature ensures that only one OU value is included in the DN.

    If you specify a value for the certifierOU IT resource parameter, then user records for which the certifier OU value in the DN does not match the certifierOU parameter value are not reconciled. This is because the user DN is used to match records in the target system and Oracle Identity Manager, and a difference in the certifier OU value would lead to a mismatch in DN values. The following example illustrates this type of scenario:

    Suppose a user account on Lotus Notes has the following DN:

    CN=John Doe/OU=testcertou/O=test/C=US
    

    If testcertou has not been assigned as the value of the certifierOU parameter for any of the IT resources created on this Oracle Identity Manager installation, then the records of this user cannot be reconciled into Oracle Identity Manager.

    Sample value: NY

    CertPath Complete file specification of the certifier ID to be used when creating certifier ID files

    Sample value: C:\Lotus\Domino\Data\cert.id

    CertPwd Password of the certifier ID file
    Create Mail ID File Specifies whether or not a mail database is created with the ID file when calling the Register New User function of IBM Lotus Notes and Domino

    The value can be True or False. The default value is True.

    Host Host name or IP address of the IBM Lotus Notes and Domino server
    Port TCP/IP port at which the IBM Lotus Notes and Domino server is listening

    The default value is 63148.

    IDFilePath Path for storing the ID files
    IDType Type of ID files to be created

    The value can be HIERARCHICAL or CERTIFIER.

    The default is 172 (HIERARCHICAL). The numeric value for CERTIFIER is 173.

    MailDBPath Mail file path
    MailOwnerAccess Mail database ACL setting for the owner

    The value can be one of the following:

    • 0: MANAGER

    • 1: DESIGNER

    • 2: EDITOR

    The default value is 0.

    MailQuotaLimit Maximum size of the user's e-mail database, in megabytes

    The default value is 50.

    MailQuotaWarning Size, in megabytes, at which the user's mail database issues a warning that the size limit may be exceeded

    The default value is 40.

    MailServer Canonical name of the server containing the user's mail file

    Sample value: CN=ServerName/O=OrgName

    Note: You must enter a value for this parameter.

    MailSystem User's mail system

    The value can be any one of the following:

    • 0: NOTES

    • 3: INOTES

    • 4: INTERNET

    The default value is 0.

    MailTemplateName Name of the template for the mail file
    PasswordLength Minimum number of characters that can be used in the password

    The value can be any number. The default minimum length is 5 characters.

    RegLog Name of the log file to be used when creating IDs

    The default value is log.nsf.

    RegServer Name of the server to be used when creating IDs and performing other registration functions
    StoreAddBook Indicates whether or not the ID file is stored in the Domino Directory of the server

    The value can be True or False. The default value is True.

    Sync Internet Password Specifies whether or not the user can use the same password for both local client-based access and Web-based access to IBM Lotus Notes and Domino

    The value can be True or False. The default value is True.

    IsSecure Specifies whether or not the SSL feature is enabled

    The value can be Yes or No. The default value is Yes.

    Note: It is recommended that you enable SSL to secure communication with the target system.

    DenyAccessGroupName Name of the group for users whose accounts have been disabled

    Note: If there is no Deny Access group on the IBM Lotus Notes and Domino installation, then you must create one by performing the procedure described in the "Creating a Deny Access Group" section.

    triggerAdminp Specifies whether or not the Trigger AdminP feature is enabled

    The value can be Yes or No. The default value is Yes.

    isAgentInstalled Specify Yes as the value of this parameter if you want to enable support for encrypted e-mail on the target system. Otherwise, specify No.

    See Also: The "Enabling Modification of ID Files" section for more information about this parameter.

    TrustedTimeStamp This parameter is used for trusted source reconciliation.

    Starting with the first reconciliation run, this parameter stores the time-stamp value at which the reconciliation run ends.

    The default value is None. Do not change it.

    NonTrustedTimeStamp This parameter is used for target resource reconciliation.

    Starting with the first reconciliation run, this parameter stores the time-stamp value at which the reconciliation run ends.

    The default value is None. Do not change it.

    Max Retries Number of times that the Lotus Notes Connector should retry connecting to the target server if the connection fails

    The default value is 2.

    Delay Delay (in milliseconds) before the connector attempts to retry connecting to the target system, in case the connection fails

    The default value is 10000.

    TerminatedGroupName Specifies the Terminated User group to which users who are deleted must be assigned
    ImmediateDelete Use this parameter to specify how the Delete User provisioning operation must be performed. You can specify one of the following values:
    • Enter Yes if you want all references to the user in the Domino Directory to be deleted before an administration process request is issued.

    • Enter No if you want to let the administration process make all required deletions.

    MailFileActionForDelete Use this parameter to specify how mail file deletion must be performed when a user is deleted.

    You can specify one of the following values:

    • Enter Delete All if you want the mail file on the user's home server and all replicas of the mail file to be deleted.

    • Enter Delete Home if you want the mail file on the user's home server to be deleted.

    • Enter Delete None if you do not want the user's mail file to be deleted.


    Note:

    If there are multiple certifiers on the target system, then you must create one IT resource (of the Lotus Notes IT resource type) for each certifier. Refer to Oracle Identity Manager Design Console Guide for information about creating IT resources.
  9. Click Next. The Provide IT Resource Instance Data page for a new instance of the Lotus Notes IT resource type is displayed.

  10. Click Skip to specify that you do not want to define another IT resource. The Confirmation page is displayed.

    See Also:

    If you want to define another IT resource, then refer to Oracle Identity Manager Administrative and User Console Guide for instructions.
  11. Click View Selections.

    The contents of the XML file are displayed on the Import page. You might see a cross-shaped icon along with some nodes. These nodes represent Oracle Identity Manager entities that are redundant. Before you import the connector XML file, you must remove these entities by right-clicking each node and then selecting Remove.

  12. Click Import. The connector XML file is imported into Oracle Identity Manager.

2.6 Configuring Oracle Identity Manager

Configuring Oracle Identity Manager involves the following procedures:

Note:

In a clustered environment, you must perform this step on each node of the cluster.

2.6.1 Changing to the Required Input Locale

Changing to the required input locale (language and country setting) involves installing the required fonts and setting the required input locale.

You may require the assistance of the system administrator to change to the required input locale.

2.6.2 Clearing Content Related to Connector Resource Bundles from the Server Cache

While performing the instructions described in the "Copying the Connector Files" section, you copy files from the resources directory on the installation media into the OIM_HOME/xellerate/connectorResources directory. Whenever you add a new resource bundle in the connectorResources directory or make a change in an existing resource bundle, you must clear content related to connector resource bundles from the server cache.

To clear content related to connector resource bundles from the server cache:

  1. In a command window, change to the OIM_HOME/xellerate/bin directory.

    Note:

    You must perform Step 1 before you perform Step 2. An exception is thrown if you run the command described in Step 2 as follows:
    OIM_HOME\xellerate\bin\batch_file_name
    
  2. Enter one of the following commands:

    • On Microsoft Windows:

      PurgeCache.bat ConnectorResourceBundle
      
    • On UNIX:

      PurgeCache.sh ConnectorResourceBundle
      

    Note:

    You can ignore the exception that is thrown when you perform Step 2.

    In this command, ConnectorResourceBundle is one of the content categories that you can remove from the server cache. Refer to the following file for information about the other content categories:

    OIM_HOME/xellerate/config/xlConfig.xml
    

2.6.3 Enabling Logging

When you enable logging, Oracle Identity Manager automatically stores in a log file information about events that occur during the course of provisioning and reconciliation operations. To specify the type of event for which you want logging to take place, you can set the log level to one of the following:

  • ALL

    This level enables logging for all events.

  • DEBUG

    This level enables logging of information about fine-grained events that are useful for debugging.

  • INFO

    This level enables logging of messages that highlight the progress of the application at a coarse-grained level.

  • WARN

    This level enables logging of information about potentially harmful situations.

  • ERROR

    This level enables logging of information about error events that may allow the application to continue running.

  • FATAL

    This level enables logging of information about very severe error events that could cause the application to stop functioning.

  • OFF

    This level disables logging for all events.

The file in which you set the log level depends on the application server that you use:

  • Oracle WebLogic Server

    To enable logging:

    1. Add the following line in the OIM_HOME/xellerate/config/log.properties file:

      log4j.logger.ADAPTER.LOTUSNOTES=log_level
      
    2. In this line, replace log_level with the log level that you want to set.

      For example:

      log4j.logger.ADAPTER.LOTUSNOTES=INFO
      

    After you enable logging, log information is displayed on the server console.

  • IBM WebSphere Application Server

    To enable logging:

    1. Add the following line in the OIM_HOME/xellerate/config/log.properties file:

      log4j.logger.ADAPTER.LOTUSNOTES=log_level 
      
    2. In this line, replace log_level with the log level that you want to set.

      For example:

      log4j.logger.ADAPTER.LOTUSNOTES=INFO
      

    After you enable logging, log information is written to the following file:

    WEBSPHERE_HOME/AppServer/logs/SERVER_NAME/SystemOut.log
    
  • JBoss Application Server

    To enable logging:

    1. In the JBOSS_HOME/server/default/conf/log4j.xml file, add the following lines if they are not already present in the file:

      <category name="ADAPTER.LOTUSNOTES">
         <priority value="log_level"/>
      </category>
      
    2. In the second XML code line, replace log_level with the log level that you want to set. For example:

      <category name="ADAPTER.LOTUSNOTES">
         <priority value="INFO"/>
      </category>
      

    After you enable logging, log information is written to the following file:

    JBOSS_HOME/server/default/log/server.log
    
  • Oracle Application Server

    To enable logging:

    1. Add the following line in the OIM_HOME/xellerate/config/log.properties file:

      log4j.logger.ADAPTER.LOTUSNOTES=log_level 
      
    2. In this line, replace log_level with the log level that you want to set.

      For example:

      log4j.logger.ADAPTER.LOTUSNOTES=INFO
      

    After you enable logging, log information is written to the following file:

    ORACLE_HOME/opmn/logs/default_group~home~default_group~1.log
    

2.7 Configuring SSL

Note:

To set up SSL connectivity between Oracle Identity Manager and the IBM Lotus Notes and Domino server:

  1. Ensure that the DIIOP and HTTP tasks are running on the IBM Lotus Notes and Domino server for SSL communication.

    Note:

    If you have already performed the procedure described in the "Configuring the Target System" section, then the DIIOP task is already running.
  2. On the IBM Lotus Notes and Domino server, create a key ring using the Server Certificate Admin (certsrv.nsf) database. Move the two key ring files, keyfile.kyr and keyfile.sth, to the data directory of the server.

  3. Restart the DIIOP task to generate a file named TrustedCerts.class in the IBM Lotus Notes and Domino data directory. The following is the typical path where this file may be found:

    LOTUS_HOME/Domino/data/domino/java
    

    Here, LOTUS_HOME is the directory in which IBM Lotus Notes and Domino is installed.

  4. Package the TrustedCerts.class file in the TrustedCerts.jar file.

  5. Move the TrustedCerts.jar file to the JAVA_HOME\jre\lib\ext directory on Oracle Identity Manager host. Here, JAVA_HOME is the JDK installation directory that is used by Oracle Identity Manager.