2 Deploying the Connector

Deploying the connector involves the following steps:

• Step 1: Verifying Deployment Requirements

• Step 2: Copying the Connector Files and External Code

• Step 3: Importing the Connector XML Files

• Step 4: Configuring Reconciliation

• Step 5: Compiling Adapters

• Step 6: Configuring SSL

Step 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.2 or later
Target systems	Sun ONE Directory Server 5.2
Target system host platforms	Microsoft Windows 2000

Step 2: Copying the Connector Files and External Code

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

Note:

The directory paths given in the first column of this table correspond to the location of the connector files in the following ZIP file on the installation media:

Directory Servers\Sun Java System Directory Server\Sun Java System Directory Server Rev 4.1.0.zip

Refer to "Files and Directories That Comprise the Connector" for more information about these files.

Files in the Installation Media Directory	Destination Directory
xml\iPlanetResourceObject.xml	xellerate_home\xellerate\iPlanet-versionno\xml
xml\iPlanetXLResourceObject.xml	xellerate_home\xellerate\iPlanet-versionno\xml
lib\xliIPlanet.jar	xellerate_home\xellerate\JavaTasks
The following files in the troubleshoot directory: log.properties TroubleShootingUtilityIPlanet.class TroubleShootIPlanet.properties	xellerate_home\xellerate\troubleshoot
docs\B31139_01.pdf docs\html	xellerate_home\xellerate\docs

Note:

In the destination directory path, the version number specified in the directory name iPlanet-versionno would change depending on the actual version number of the software.

Step 3: Importing the Connector XML Files

To import the connector XML files 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 locating files is displayed.

4. Locate and open the iPlanetXLResourceObject.xml file, which is in the xellerate_home\xellerate\iPlanet-versionno\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 iPlanet User IT resource is displayed.

8. Specify values for the parameters of the iPlanet User IT resource. Refer to the table in the "Defining IT Resources" section information about the values to be specified.

9. Click Next. The Provide IT Resource Instance Data page for a new instance of the LDAP Server 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 Tools Reference Guide for instructions.

11. Click View Selections.

    The contents of the XML file are displayed in the Deployment Manager – Import window. You may see a cross-shaped icon along with some nodes. You must remove these nodes. To do this, right-click each such node and then select Remove.

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

13. If you plan to use the connector in trusted source reconciliation mode, then perform the same procedure to import the iPlanetResourceObject.xml file. This file is in the xellerate_home\xellerate\iPlanet-versionno\xml directory.

    Caution:

    Only one connector can be configured as a trusted source. If you import the iPlanetResourceObject.xml file while you have another trusted source configured, then both connector reconciliations would stop working.

    After you import the connector XML files, proceed to the "Step 4: Configuring Reconciliation" section.

Defining IT Resources

You must specify values for the iPlanet User IT resource parameters listed in the following table.

Parameter Name	Parameter Description
Admin Id	DN value of the user who has administrator rights on the target Sun Java System Directory server The default value is uid=admin,ou=administrators,ou=topologymanagement,o=netscaperootAdmin
Admin Password	Password of the administrator
Server Address	Server address of the target Sun Java System Directory server The value can be 164.164.164.164.
Port	Port number to connect to the target Sun Java System Directory server The default value is 389.
Root DN	Base DN where all the user operations are to be carried out The value can be o=xyz
SSL	Specifies whether or not an SSL connection is used for communication between Oracle Identity Manager and the target Sun Java System Directory server The value can be true or false.
Last Recon TimeStamp	The value is empty the first time the reconciliation process is run. From then onward, this parameter stores the time at which the last reconciliation process was completed.
Prov Attribute Lookup Code	Name of the lookup definition that has the target attribute mappings required for provisioning The default value of this parameter is AttrName.Prov.Map.iPlanet
Recon Attribute Lookup Code	Name of the lookup definition that has the target attribute mappings required for reconciliation The default value of this parameter is AttrName.Recon.Map.iPlanet
Use XL Org Structure	A configurable option for the user If set to true, then the provisioned user is created under the Organization structure of Oracle Identity Manager. If set to false, then the value of the Organization field in the process form is used and the provisioned user is created under the Organization structure that is specified in the process form while provisioning.

After you specify values for these IT resource parameters, go to Step 9 of the procedure to import connector XML files.

Step 4: Configuring Reconciliation

Configuring reconciliation involves creating scheduled tasks for lookup fields and user reconciliations. To create these scheduled tasks:

1. Open the Oracle Identity Manager Design Console.

2. Expand the Xellerate Administration folder.

3. Select Task Scheduler.

4. Click Find. The details of the predefined scheduled tasks are displayed on two different tabs.

5. Enter a number in the Max Retries field. This number represents the number of times Oracle Identity Manager should attempt to complete the task before assigning the ERROR status to the task.

6. Ensure that the Disabled and Stop Execution check boxes are cleared.

7. In the Start region, double-click the Start Time field. From the date-time editor that is displayed, select the date and time at which you want the task to run.

8. In the Interval region, set the following schedule parameters:

   • To set the task to run on a recurring basis, select the Daily, Weekly, Recurring Intervals, Monthly, or Yearly option.

     If you select the Recurring Intervals option, then you must also specify the time interval at which you want the task to run on a recurring basis.

   • To set the task to run only once, select the Once option.

9. Provide values for the attributes of the scheduled task. Refer to the appropriate table in the "Specifying Values for the Scheduled Task Attributes"section for information about the values to be specified.

   See Also:

   Oracle Identity Manager Design Console Guide for information about adding and removing task attributes

10. Click Save. The scheduled task is created. The INACTIVE status is displayed in the Status field, because the task is not currently running. The task is run at the date and time that you set in Step 7.

11. Repeat Steps 5 through 10 to create the second scheduled task.

After you create both scheduled tasks, proceed to the "Step 5: Compiling Adapters" section.

Specifying Values for the Scheduled Task Attributes

This section provides information about the attribute values to be specified for the following scheduled tasks:

• Lookup Fields Reconciliation Scheduled Task

• User Reconciliation Scheduled Task

Lookup Fields Reconciliation Scheduled Task

You must specify values for the following attributes of the lookup fields reconciliation scheduled task.

Note:

Attribute values are predefined in the connector XML file that you import. Specify values only for those attributes that you want to change.

Attribute Name	Description	Default/Sample Value
LookupCodeName	Name of the lookup definition to which the values are to be reconciled	Lookup.IPNT.UserGroup
ITResourceName	Name of the IT resource for setting up a connection to the Sun Java System Directory server	iPlanet User
SearchContext	Search context to be used for searching for users	DC=mycompany,DC=com
ObjectClass	Name of the group object class For example, groupOfUniqueNames and ldapsubentry.	groupOfUniqueNames (for Group reconciliation) ldapsubentry (for Role reconciliation)
CodeKeyLTrimStr	String value for left-trimming the value obtained from the search For example: cn= or uid= If there is nothing to be trimmed, then specify the value [NONE].	[NONE]
CodeKeyRTrimStr	String value for right-trimming the value obtained from the search For example: ,DC=mycompany,DC=com If there is nothing to be trimmed, then specify the value [NONE].	,DC=mycompany,DC=com
ReconMode	Specify REFRESH to completely refresh the existing lookup. Specify UPDATE to update the lookup with the new values.	REFRESH or UPDATE (specified in uppercase)

After you specify values for these scheduled task attributes, go to Step 10 of the procedure to create scheduled tasks.

User Reconciliation Scheduled Task

You must specify values for the following attributes of the user reconciliation scheduled task.

Note:

Attribute values are predefined in the connector XML file that you import. Specify values only for those attributes that you want to change.

Attribute Name	Description	Default/Sample Value
ITResourceName	Name of the IT resource for setting up a connection to the Sun Java System Directory server	iPlanet User
ResourceObjectName	Name of the resource object in which users are reconciled	iPlanet User
XLDeleteUsersAllowed	If this attribute is set to true, then the Delete reconciliation event is started. Users who are deleted from the target system are removed from Oracle Identity Manager. This requires all the users on the target system to be compared with all the users in Oracle Identity Manager. Note: This process affects performance.	true
UserContainer	DN value from where the users are reconciled from the target system to Oracle Identity Manager	ou=user
TrustedSource	Configurable option for trusted reconciliation	True
Xellerate Type	Default Xellerate Type for the Xellerate User	End-User Administrator
Password	Default password for the Xellerate User	Dummy123
Organization	Default organization of the Xellerate User	Xellerate Users
Role	Default role for the Xellerate User	Consultant

After you specify values for these scheduled task attributes, go to Step 10 of the procedure to create scheduled tasks.

Step 5: Compiling Adapters

The following table lists the adapters that are imported into Oracle Identity Manager when you import the connector XML file. You must compile these adapters before you can use them to provision accounts on your target system.

• iPlanet Create User

• iPlanet Delete User

• iPlanet Modify User

• iPlanet Move User

• iPlanet Add User to Group

• iPlanet Remove User from Group

• iPlanet Add Role to User

• iPlanet Remove Role from User

• iPlanet PP String

To compile adapters by using the Adapter Manager form:

1. Open the Adapter Manager form.

2. To compile all the adapters that you import into the current database, select the Compile All option.

   To compile multiple (but not all) adapters, select the adapters you want to compile. Then, select the Compile Selected option.

   Note:

   Click Compile Previously Failed to recompile only those adapters that were not compiled successfully. Such adapters do not have an OK compilation status.

3. Click Start. Oracle Identity Manager compiles the adapters that you specify.

To view detailed information about an adapter:

1. Highlight the adapter in the Adapter Manager form.

2. Double-click the row header of the adapter, or right-click the adapter.

3. Select Launch Adapter from the shortcut menu that is displayed. Details of the adapter are displayed.

Note:

To compile multiple adapters simultaneously, use the Adapter Manager form. To compile one adapter at a time, use the Adapter Factory form. Refer to Oracle Identity Manager Tools Reference Guide for information about how to use these forms.

Step 6: Configuring SSL

Note:

This is an optional step of the deployment procedure.

To enable SSL connectivity between the connector and the target Sun Java System Directory server:

1. Import the certificate from the target system into the JSDK (the JSDK that is used during installation of Oracle Identity Manager) cacerts keystore as follows:

   keytool -import -file certificate_file_name -alias iplanetcert -keystore java_home\jre\lib\security\cacerts
   
   

   Here, java_home is the directory in which JDK is installed.

2. Restart the Oracle Identity Manager server.

3. In the iPlanet User IT Resource:

   • Set the SSL parameter value to true.

   • Change the Port parameter value to the SSL port number. Typically, this number is 636.