Skip Headers
Oracle® Identity Manager Connector Guide for BMC Remedy User Management
Release 9.0.4

E10422-12
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

After you deploy the connector, you must configure it to meet your requirements. This chapter discusses the following connector configuration procedures:

Note:

In the following sections, the term attribute refers to the identity data fields that store user data.

4.1 Adding Custom Attributes for Reconciliation

Note:

You need not perform this procedure if you do not want to add custom attributes for reconciliation.

By default, the attributes listed in Section 1.7, "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 map additional attributes for reconciliation as follows:

See Also:

One of the following guides for detailed instructions on performing the steps in this section:

  • For Oracle Identity Manager release 9.1.0.x:

    Oracle Identity Manager Design Console Guide

  • For Oracle Identity Manager release 11.1.1:

    Oracle Fusion Middleware Developer's Guide

  1. Determine the Database ID for the attribute that you want to add:

    1. Open the Remedy Administrator Console.

    2. Expand Servers.

    3. Double-click Forms.

    4. Double-click the CTM:People form.

    5. Double-click the field whose Database ID you want to determine.

    6. On the Database tab, the Database ID of the field is displayed as the value of the ID field.

  2. Modify the attributemapping_recon.properties file, which is in the OIM_HOME/xellerate/XLIntegrations/BMC/config directory.

    At the end of this file, some of the attribute definitions are preceded by comment characters. You can uncomment the definition of an attribute to make it a part of the list of reconciliation attributes. If required, you can also add new attributes in this file. The format that you must use is as follows:

    OIM_ATTRIBUTE_NAME=DATABASE_ID_IN_BMC_REMEDY
    

    For example:

    Users.EmailAddress=260000002
    

    In this example, EmailAddress is the reconciliation field and 260000002 is the equivalent Database ID in BMC Remedy System. As a standard, the prefix "Users." is added at the start of all reconciliation field names.

  3. In the resource object definition, add a reconciliation field corresponding to the new attribute as follows:

    1. Open the Resource Objects form. This form is in the Resource Management folder.

    2. Click Query for Records.

    3. On the Resource Objects Table tab, double-click the BMCRO resource object to open it for editing.

    4. On the Object Reconciliation tab, click Add Field to open the Add Reconciliation Field dialog box.

    5. Specify a value for the field name.

      You must specify the name that is to the left of the equal sign in the line that you uncomment or add while performing Step 2.

      For example, if you uncomment the Users.EmailAddress=260000002 line in Step 2, then you must specify Users.EmailAddress as the attribute name.

    6. From the Field Type list, select a data type for the field.

      For example: String

    7. Save the values that you enter, and then close the dialog box.

    8. If required, repeat Steps d through g to map more fields.

    9. 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. Modify the process definition to include the mapping between the newly added attribute and the corresponding reconciliation field as follows:

    1. Open the Process Definition form. This form is in the Process Management folder.

    2. On the Reconciliation Field Mappings tab, click Add Field Map to open the Add Reconciliation Field Mapping dialog box.

    3. Enter the required values, save the values that you enter, and then close the dialog box.

    4. If required, repeat Steps b and c to map more fields.

  5. Add the attribute for provisioning. See Section 4.2, "Adding Custom Attributes for Provisioning" for detailed information about the procedure.

4.2 Adding Custom Attributes for Provisioning

By default, the attributes listed in Section 1.7, "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 as follows:

See Also:

One of the following guides for detailed instructions on performing the steps in this section:

  • For Oracle Identity Manager release 9.1.0.x:

    Oracle Identity Manager Design Console Guide

  • For Oracle Identity Manager release 11.1.1:

    Oracle Fusion Middleware Developer's Guide

  1. Determine the Database ID for the attribute that you want to add:

    1. Open the Remedy Administrator Console.

    2. Expand Servers.

    3. Double-click Forms.

    4. Double-click the CTM:People form.

    5. Double-click the field whose Database ID you want to determine.

    6. On the Database tab, the Database ID of the field is displayed as the value of the ID field.

  2. Modify the attributemapping_prov.properties file, which is in the OIM_HOME/xellerate/XLIntegrations/BMC/config directory.

    At the end of this file, some of the attribute definitions are preceded by comment characters. You can uncomment the definition of an attribute to make it a part of the list of reconciliation attributes. If required, you can also add new attributes in this file. The format that you must use is as follows:

    OIM_ATTRIBUTE_NAME=DATABASE_ID_IN_BMC_REMEDY
    

    For example:

    EmailAddress=260000002
    

    In this example, EmailAddress is the reconciliation field and 260000002 is the equivalent Database ID in BMC Remedy System.

  3. Add a new column in the process form.

    1. Open the process form. This form is in the Development Tools folder of the Oracle Identity Manager Design Console.

    2. Click Create New Version.

    3. In the Create a New Version dialog box, specify the version name in the Label field, save the changes, and then close the dialog box.

    4. From the Current Version list, select the newly created version.

    5. On the Additional Columns tab, click Add.

    6. Specify the new field name and other values. For the example described in Step 3 of Section 4.1, "Adding Custom Attributes for Reconciliation," enter UB_BMC_EMAIL.

  4. Add a new variable in the variable list.

    1. Open the Adapter Factory form. This form is in the Development Tools folder of the Oracle Identity Manager Design Console.

    2. Click the Query for Records icon.

    3. On the Adapter Factory Table tab, double-click the adpBMCCREATEUSER adapter from the list.

    4. On the Variable List tab, click Add.

    5. In the Add a Variable dialog box, specify the required values and then save and close the dialog box.

  5. Define an additional adapter task for the newly added variable in the adpBMCCREATEUSER adapter.

    1. On the Adapter Tasks tab of the Adapter Factory form, click Add.

    2. In the Adapter Task Selection dialog box, select Functional Task, select Java from the list of functional task types, and then click Continue.

    3. In the Object Instance Selection dialog box, select Persistent Instance and then click Continue.

    4. In the Add an Adapter Factory Task dialog box, specify the task name, select the setProperty method from the Method list, and then click Save.

    5. Map the application method parameters, and then save and close the dialog box. To map the application method parameters:

      For the "Output: String Return variable (Adapter Variable)" parameter:

      i. From the Map to list, select Literal.

      ii. From the Name list, select Return variable.

      For the "Input: String input (Adapter Variable)" parameter:

      i. From the Map to list, select Adapter Variables.

      ii. From the Name list, select Input.

      For the "Input: String Status (Literal)" parameter:

      i. From the Map to list, select Literal.

      ii. From the Name list, select String.

      iii. In the Value field, enter Status.

      For the "Input: String Status (Adapter Variable)" parameter:

      i. From the Map to list, select Adapter Variables.

      ii. From the Name list, select Status.

    6. Repeat Steps b through g to create more adapter tasks.

  6. Create an additional adapter task to set the input variable.

    1. Open the Adapter Factory form. This form is in the Development Tools folder in the Oracle Identity Manager Design Console.

    2. On the Adapter Tasks tab, click Add.

    3. In the Adapter Task Selection dialog box, select Logic Task, select SET VARIABLE from the list, and then click Continue.

    4. In the Edit Set Variable Task Parameters dialog box, select input from the Variable Name list, select Adapter Task from the Operand Type list, and the Operand Qualifier as the Adapter Task that you have created in the previous step. Then, click Save.

  7. Map the process form columns and adapter variables for the Create User process task as follows:

    1. Open the Process Definition form. This form is in the Process Management folder of the Design Console.

    2. Click the Query for Records icon.

    3. On the Process Definition Table tab, double-click the BMCPROCESS process.

    4. On the Tasks tab, double-click the Create User task.

    5. In the Closing Form dialog box, click Yes.

    6. On the Integration tab of the Editing Task Columns Create User dialog box, map the unmapped variables, and then save and close the dialog box. To map an unmapped variable:

      i. Double-click the row in which N is displayed in the Status column. The value N signifies that the variable is not mapped.

      ii. From the Map to list in the Edit Data Mapping for Variables dialog box, select Process Data.

      iii. From the Qualifier list, select the name of the variable.

      Repeat Steps i through iii for all unmapped variables.

    Repeat Steps 1 through 6 if you want to add more attributes.

  8. Update the request datasets.

    Note:

    Perform steps 8 through 10 only if you want to perform request-based provisioning.

    When you add an attribute on the process form, you also update the XML files 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, while performing Step 3 of this procedure, if you added E-mail address as an attribute on the process form, then enter the following line:

      <AttributeReference
      name = "E-mail address"
      attr-ref = "E-mail address"
      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_BMC_EMAIL is the value in the Name column of the process form, then you must specify E-mail address 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 while performing Step 3.

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

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

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

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

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

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

  11. If you have not added the attribute for reconciliation, then perform the procedure described in Section 4.1, "Adding Custom Attributes for Reconciliation."

4.3 Configuring the Connector for Multiple Installations of the Target System

Note:

Perform this procedure only if you want to configure the connector for multiple installations of BMC Remedy User Management.

You may want to configure the connector for multiple installations of BMC Remedy User Management. The following example illustrates this requirement:

The Tokyo, London, and New York offices of Example Multinational Inc. have their own installations of BMC Remedy User Management. The company has recently installed Oracle Identity Manager, and they want to configure Oracle Identity Manager to link all the installations of BMC Remedy User Management.

To meet the requirement posed by such a scenario, you must configure the connector for multiple installations of BMC Remedy User Management.

To configure the connector for multiple installations of the target system:

See Also:

One of the following guides for detailed instructions on performing each step of this procedure:

  • For Oracle Identity Manager release 9.1.0.x:

    Oracle Identity Manager Design Console Guide

  • For Oracle Identity Manager release 11.1.1:

    Oracle Fusion Middleware Developer's Guide

  1. Create and configure one resource object for each target system installation.

    The Resource Objects form is in the Resource Management folder. The BMCRO resource object is created when you import the connector XML file. You can use this resource object as the template for creating the remaining resource objects.

  2. Create and configure one IT resource for each resource object.

    The IT Resources form is in the Resource Management folder. The BMCRO IT resource is created when you import the connector XML file. You can use this IT resource as the template for creating the remaining IT resources, of the same resource type.

  3. Design one process form for each resource object.

    The Form Designer form is in the Development Tools folder. The UD_BMC process form is created when you import the connector XML file. You can use this process form as the template for creating the remaining process forms.

  4. Create and configure one process definition for each resource object.

    The Process Definition form is in the Process Management folder. The BMCPROCESS process definition is created when you import the connector XML file. You can use this process definition as the template for creating the remaining process definitions.

    While creating process definitions for each target system installation, the following steps that you must perform are specific to the creation of each process definition:

    • From the Object Name lookup field, select the resource object that you create in Step 1.

    • From the Table Name lookup field, select the process form that you create in Step 3.

    • While mapping the adapter variables for the IT Resource data type, ensure that you select the IT resource that you create in Step 2 from the Qualifier list.

  5. Configure reconciliation for each target system installation. See Section 3.4, "Configuring the Reconciliation Scheduled Tasks" for instructions.

    Note:

    In Oracle Identity Manager release 11.1.1, a scheduled job is an instance of a scheduled task. In this guide, the term scheduled task used in the context of Oracle Identity Manager release 9.1.0.x is the same as the term scheduled job in the context of Oracle Identity Manager release 11.1.1.

    See Oracle Fusion Middleware System Administrator's Guide for Oracle Identity Manager for more information about scheduled tasks and scheduled jobs.

    For each target system installation, only the values of the following attributes of the scheduled task must be changed:

    • TargetRO

    • ServerName

    • IsTrusted

    Set the IsTrusted attribute to YES for the BMC Remedy User Management installation that you want to designate as a trusted source.

  6. If required, modify the fields to be reconciled for the Xellerate User resource object.

When you use the Administrative and User Console to perform provisioning, you can specify the IT resource corresponding to the BMC Remedy User Management installation to which you want to provision the user.