Skip Headers
Oracle® Identity Manager Connector Guide for JD Edwards EnterpriseOne User Management
Release 9.0.4

E10453-09
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
PDF · Mobi · ePub

4 Extending the Functionality of the Connector

The following section describes procedures that you can perform to extend the functionality of the connector for addressing your specific business requirements:

4.1 Adding New Attributes for Target Resource Reconciliation

Note:

This section describes an optional procedure. You need not perform this procedure if you do not want to add new attributes for reconciliation.

By default, the attributes listed in Section 1.6, "Connector Objects Used During Target Resource Reconciliation and Provisioning" 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:

Note:

You must ensure the new attributes that you add for reconciliation contain data in string-format only. Binary attributes must not be introduced into Oracle Identity Manager natively.

  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 and then close the dialog box.

    6. If you are using Oracle Identity Manager release 11.1.1, then click Create Reconciliation Profile. This copies changes made to the resource object into the MDS.

  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.

4.2 Adding New Attributes for Provisioning

Note:

  • This section describes an optional procedure. You need not perform this procedure if you do not want to add new attributes for provisioning.

  • Before starting the following procedure, perform Steps 1 and 2 as described in Section 4.1, "Adding New Attributes for Target Resource Reconciliation." If these steps have been performed while adding new attributes for target resource reconciliation, then you need not repeat the steps.

By default, the attributes listed in Section 1.6, "Connector Objects Used During Target Resource Reconciliation and Provisioning" 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:

  1. Create an entry for the attribute in the lookup definition for provisioning as follows:

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

    2. Expand Administration.

    3. Double-click Lookup Definition.

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

    5. 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.

    6. Click the Save icon.

    Note:

    Perform steps 2 through 4 only if you want to perform request-based provisioning.

  2. Update the request dataset.

    When you add an attribute on the process form, you also update the XML file containing the request dataset definitions. To update a request dataset:

    1. In a text editor, open the XML file located in the OIM_HOME/DataSet/file directory for editing.

    2. Add the AttributeReference element and specify values for the mandatory attributes of this element.

      See Also:

      The "Configuring Requests" chapter of the Oracle Fusion Middleware Developer's Guide for Oracle Identity Manager guide for more information about creating and updating request datasets

      For example, if you added Address Number as an attribute on the process form, then enter the following line:

      <AttributeReference
      name = "Address Number"
      attr-ref = "Address Number"
      type = "String"
      widget = "text"
      length = "50"
      available-in-bulk = "false"/>
      

      In this AttributeReference element:

      • For the name attribute, enter the value in the Name column of the process form without the tablename prefix.

        For example, if UD_JDE_ADDRESS_NUMBER is the value in the Name column of the process form, then you must specify Address Number as the value of the name attribute in the AttributeReference element.

      • For the attr-ref attribute, enter the value that you entered in the Field Label column of the process form.

      • For the type attribute, enter the value that you entered in the Variant Type column of the process form.

      • For the widget attribute, enter the value that you entered in the Field Type column of the process form.

      • For the length attribute, enter the value that you entered in the Length column of the process form.

      • For the available-in-bulk attribute, specify true if the attribute must be available during bulk request creation or modification. Otherwise, specify false.

      If you added more than one attribute on the process form, then repeat this step for each attribute added.

    3. Save and close the XML file.

  3. Run the PurgeCache utility to clear content related to request datasets from the server cache.

    See Oracle Fusion Middleware System Administrator's Guide for Oracle Identity Manager for more information about the PurgeCache utility.

  4. Import into MDS the request dataset definitions in XML format.

    See Section 2.6.5.2, "Importing Request Datasets into MDS" for detailed information about the procedure.

4.2.1 Enabling Update of New Attributes for Provisioning

After you add an attribute for provisioning, you must enable update operations on the attribute. If you do not perform this procedure, then you will not be able to modify the value of the attribute after you set a value for it during the Create User provisioning operation.

To enable the update of a new attribute for provisioning a user:

  1. Expand Process Management.

  2. Double-click Process Definition and open the JDE Process process definition.

  3. In the process definition, add a new task for updating the field as follows:

    1. Click Add and enter the task name, for example, AddressNumber Updated and the task description.

    2. In the Task Properties section, select the following fields:

      • Conditional

      • Required for Completion

      • Allow Cancellation while Pending

      • Allow Multiple Instances

    3. Click on the Save icon.

  4. On the Integration tab, click Add, and then click Adapter.

  5. Select the adpJDEMODIFYUSER adapter, click Save, and then click OK in the message that is displayed.

  6. To map the adapter variables listed in this table, select the adapter, click Map, and then specify the data given in the following table:

    Note:

    Some of the values in this table are specific to Address Number (mnAddressNumber value in the target system). These values must be replaced with values relevant to the attributes that you require.

    Variable Name Data Type Map To Qualifier Literal Value

    sPropertyName

    String

    Literal

    String

    mnAddressNumber

    processKeyInstance

    String

    Process Data

    Process Instance

    NA

    Adapter return value

    Object

    Response Code

    NA

    NA

    JDEITResource

    IT Resource

    Process Data

    IT Resource Type

    NA

    userID

    String

    Process Data

    User ID

    NA


  7. Click the Save icon and then close the dialog box.