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:

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.

  • In this section, the term attribute refers to the identity data fields that store Ticket data.

By default, the attributes listed in Section 1.6.1, "Tickets Attributes for Target Resource Reconciliation and Provisioning" are mapped for reconciliation between Oracle Identity Manager and the target system. User is required to add custom attributes specific to the target application. These fields will provide information on Target Application Name, Access information for target application modules, and Ticket specific details. 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.0.1 through 9.0.3.x or 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 HPD:Help Desk 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/BMCTICKET/config directory.

    Add the new attribute in this file. The format that you must use is as follows:

    OimAttributeName=Database_ID_in_BMC_Remedy

    For example:

    Ticket.EmailAddress=260000002

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

  3. Log in to the Design Console.

  4. 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. Search for and open the BMCTicketRO resource object.

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

    4. 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 add while performing Step 2.

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

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

      For example: String

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

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

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

  5. Add a new field on the process form as follows:

    1. Open the Process Forms form. This form is in the Development Tools folder.

    2. Search for and open the UD_BMCTKT process form.

    3. Click Create New Version.

    4. In the Label field of the Create a New Version dialog box, specify a version for the form.

    5. Save the changes, and then close the dialog box.

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

    7. On the Additional Columns tab, click Add.

    8. Specify a name and other values for the field. For the example described in Step 4, enter UD_BMCTKT_EMAIL in the Name column and then enter other values for the field.

    9. Click the Save icon.

  6. 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. Search for and open the BMCTicketProcess process definition.

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

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

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

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

Note:

In this section, the term attribute refers to the identity data fields that store Ticket data.

By default, the attributes listed in Section 1.6.1, "Tickets Attributes for Target Resource Reconciliation and Provisioning" are mapped for provisioning between Oracle Identity Manager and the target system. You needs to map additional target application specific 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.0.1 through 9.0.3.x or 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. Modify the attributemapping_prov.properties file, which is in the OIM_HOME/xellerate/XLIntegrations/BMCTICKET/config directory. You must add target application specific attributes in this file. The format that you must use is as follows:

    OimAttributeName=BMCFieldID

    Note:

    BMCFieldID is the Database ID for the field on the BMC Server.

  2. Add a new column in the process form.

    Note:

    If you have already performed Step 5 of Section 4.1, "Adding Custom Attributes for Reconciliation," then directly proceed to Step 3.

    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 a name and other values for the field. For the example described in Step 4, enter UD_BMCTKT_EMAIL.

    7. Click the Save icon.

  3. 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 adpBMCCREATETICKET adapter from the list.

    4. On the Variable List tab, click Add.

    5. In the Add a Variable dialog box, specify the required values (for example, Status) and then save and close the dialog box.

  4. Define an additional adapter task for the newly added variable in the adpBMCCREATETICKET 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 New Object 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 Adapter variables.

      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 the field that you added in the attributemapping_prov.properties file. For example, 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 the field that you added in the attributemapping_prov.properties file. For example, select Status.

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

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

  6. 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 BMCTicketProcess process.

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

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

    6. On the Integration tab of the Editing Task Columns Create Ticket 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.

  7. Update the request datasets.

    Note:

    Perform steps 7 through 9 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 2 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_BMCTKT_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 2.

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

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

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

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

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

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

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

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

You can create tickets for multiple target applications on BMC Remedy Ticket Management. To extend this feature to provisioning operations performed through Oracle Identity Manager, you can apply one of the following approaches:

To configure the connector for a specific target application of BMC Remedy Ticket Management:

See Also:

One of the for detailed information about each step of the following procedure

  • For Oracle Identity Manager release 9.0.1 through 9.0.3.x or 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 the target application. The Resource Objects form is in the Resource Management folder.

    The BMCTicketRO 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. For example, if Lotus Notes is the target application, then you can create a resource object with the name BMCTicketLotusRO.

  2. Create and configure one IT resource for each resource object. The IT Resources form is in the Resource Management folder. The BMCTicket IT resource is created when you import the connector XML file. You can use this IT resource as the template for creating a new IT resource, of the BMCRemedyTicket IT resource type.

  3. Design one process form for each resource object. The Form Designer form is in the Development Tools folder. The UD_BMCTKT process form is created when you import the connector XML file. You can use this process form as the template for creating a new form for adding target application specific attributes.

  4. Create and configure one process definition for each resource object. The Process Definition form is in the Process Management folder. The BMCTicketProcess process definition is created when you import the connector XML file. You can use this process definition as the template for creating for a new process definition.

    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.

  5. To add custom attributes for provisioning, perform the procedure described in the Section 4.2, "Adding Custom Attributes for Provisioning."