3 Configuring the Connector

3.1.1 Configuring Trusted Source Reconciliation

While configuring the connector, the target system can be designated as a trusted source or target resource. If you designate the target system as a trusted source, then during a reconciliation run:

• For each newly created user on the target system, an OIM User is created.

• Updates made to each user on the target system are propagated to the corresponding OIM User.

If you designate the target system as a target resource, then during a reconciliation run:

• For each account created on the target system, a resource is assigned to the corresponding OIM User.

• Updates made to each account on the target system are propagated to the corresponding resource.

Enabling trusted source reconciliation involves the following steps:

1. Import the XML file for trusted source reconciliation, JDEConnectorXLResourceObject.xml, by using the Deployment Manager. This section describes the procedure to import the XML file.

2. Set the isTrustedSource scheduled task attribute to True. You specify a value for this attribute while configuring the user reconciliation scheduled task, which is described later in this guide.

To import the XML file for trusted source reconciliation:

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 JDEConnectorXLResourceObject.xml file, which is in the OIM_HOME/xellerate/JDE/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 Import.

8. In the message that is displayed, click Import to confirm that you want to import the XML file and then click OK.

After you import the XML file for trusted source reconciliation, you must set the value of the isTrustedSource reconciliation scheduled task attribute to True. This procedure is described in the "Configuring the Reconciliation Scheduled Tasks" section.

3.1.2 Configuring the Reconciliation Scheduled Tasks

When you perform the procedure described in the "Importing the Connector XML File" section, the scheduled tasks for lookup fields and user reconciliations are automatically created in Oracle Identity Manager. To configure 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. For the first scheduled task, enter a number in the Max Retries field. This number represents the number of times Oracle Identity Manager must attempt to complete the task before assigning the FAILED status to the task.

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

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 "Specifying Values for the Scheduled Task Attributes" section for information about the values to be specified.

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.

3.1.3 Adding New Attributes for Target Resource Reconciliation

By default, the attributes listed in the "Reconciled Target System Fields" section are mapped for reconciliation between Oracle Identity Manager and the target system. If required, you can add new attributes for target resource reconciliation.

To add a new attribute for target resource reconciliation, perform the following procedure:

1. Log in to the Oracle Identity Manager Design Console.

2. Add the new attribute on the OIM User process form as follows:

   1. Expand Development Tools.

   2. Double-click Form Designer.

   3. Search for and open the UD_JDE process form.

   4. Click Create New Version.

   5. In the Label field, enter the version name. For example, version#1.

   6. Click the Save icon.

   7. Select the current version created in Step e from the Current Version list.

   8. Click Add to create a new attribute, and provide the values for that attribute.

      For example, if you are adding the organization attribute, then enter the following values in the Additional Columns tab:

      Field	Value
      Name	AddressNumber
      Variant Type	String
      Length	100
      Field Label	AddressNumber
      Order	14

      
      

   9. Click the Save icon.

   10. Click Make Version Active.

3. Add the new attribute to the list of reconciliation fields in the resource object as follows:

   1. Expand Resource Management.

   2. Double-click Resource Objects.

   3. Search for and open the JDE Resource Object resource object.

   4. On the Object Reconciliation tab, click Add Field, and then enter the following values:

      Field Name: AddressNumber

      Field Type: String

   5. Click the Save icon.

4. Create a reconciliation field mapping for the new attribute in the process definition form as follows:

   1. Expand Process Management.

   2. Double-click Process Definition.

   3. Search for and open the JDE Process process definition.

   4. On the Reconciliation Field Mappings tab, click Add Field Map, and then select the following values:

      Field Name: AddressNumber

      Field Type: String

      Process Data Field: AddressNumber

   5. Click the Save icon.

5. Create an entry for the attribute in the lookup definition for reconciliation as follows:

   1. Expand Administration.

   2. Double-click Lookup Definition.

   3. Search for and open the Lookup.JDEReconciliation.FieldMap lookup definition.

   4. Click Add and enter the Code Key and Decode values for the attribute. The Code Key value must be the name of the attribute given in the resource object. The Decode value is the name of the attribute in the target system.

      For example, enter AN8 in the Code Key field and then enter AddressNumber in the Decode field.

   5. Click the Save icon.

6. Add the new attribute to the Lookup.JDE.Configuration lookup definition as follows:

   1. Expand Administration.

   2. Double-click Lookup Definition.

   3. Search for and open the Lookup.JDE.Configuration lookup definition.

   4. Every attribute that you add belongs to a JDE database table. If the name of this JDE database table is already listed as the Code Key value, then enter the column name as Decode value.

      Note:

      If you have more than one value in the Decode column, then each value must be separated by a comma (,).

   5. If the name of this JDE database table is not listed as a Code Key value, then:

      1. Click Add.

      2. Enter the name of the JDE table as the Code Key value. For example, TF0092.

      3. Enter the JDE table column name as the Decode value. For example, Email.

   6. Click the Save icon.

3.2.1 Compiling Adapters

Adapters are used to implement provisioning functions. The following adapters are imported into Oracle Identity Manager when you import the connector XML file:

• Enable and Disable User

• JDE Delete User

• Modify Password

• PrePopulate JDE Form

• JDE Remove Role

• JDE Modify User

• JDE Create User

• JDE Add Role

You must compile these adapters before they can be used in provisioning operations.

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 Compile All.

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

   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 selected adapters.

4. If Oracle Identity Manager is installed in a clustered environment, then copy the compiled adapters from the OIM_HOME/xellerate/Adapter directory to the same directory on each of the other nodes of the cluster. If required, overwrite the adapter files on the other nodes.

If you want to compile one adapter at a time, then use the Adapter Factory form.

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.

3.2.2 Adding New Attributes for Provisioning

By default, the attributes listed in the "Provisioning Module" section are mapped for provisioning between Oracle Identity Manager and the target system. If required, you can map additional attributes for provisioning.

To add a new attribute for provisioning, create an entry for the attribute in the lookup definition for provisioning as follows:

1. Expand Administration.

2. Double-click Lookup Definition.

3. Search for and open the Lookup.JDEProvisioning.FieldMap lookup definition.

4. Click Add and enter the Code Key and Decode values for the attribute. The Code Key value must be the name of the attribute given in the resource object. The Decode value is the name of the attribute in the target system.

   For example, enter UD_JDE_ADDRESSNUMBER in the Code Key field and then enter mnAddressNumber in the Decode field.

5. Click the Save icon.