3 Configuring Connector Functionality

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

• Configuring Reconciliation

• Configuring Provisioning

• Configuring the Connector for Multiple Target Applications

Note:

This chapter provides both conceptual and procedural information about configuring the connector. It is recommended that you read the conceptual information before you perform the procedures.

3.1 Configuring Reconciliation

As mentioned earlier in this guide, reconciliation involves duplicating in Oracle Identity Manager the creation of and modifications to user accounts on the target system. This section discusses the following topics related to configuring reconciliation:

• Configuring the Reconciliation Scheduled Tasks

• Adding Custom Attributes for Reconciliation

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

   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 configure the second and third scheduled tasks.

After you configure all three scheduled tasks, proceed to the "Adding Custom Attributes for Reconciliation" section.

3.1.1.1 Specifying Values for the Scheduled Task Attributes

Refer to the following sections for information about the attribute values to be specified for the scheduled tasks:

• Lookup Fields Reconciliation Scheduled Task

  This section describes attributes of the lookup fields reconciliation scheduled task.

• BMC Ticket Reconciliation Scheduled Task

  This section describes attributes of the BMC Ticket reconciliation scheduled task.

3.1.1.1.1 Lookup Fields Reconciliation Scheduled Task

You must specify values for the following attributes of the BMCTicket Lookup Reconciliation 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	Description	Value
ServerName	Name of the IT resource	BMCTicket
LookUpCode	Name of the lookup code	The value can be any one of the following: Lookup.BMCTKT.Category Lookup.BMCTKT.Type Lookup.BMCTKT.Item
LookUpName	Name of the lookup field	The value can be any one of the following: Category Type Item

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

3.1.1.1.2 BMC Ticket Reconciliation Scheduled Task

You must specify values for the following attributes of the BMCTicket Reconciliation 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	Description	Value
ServerName	Name of the IT resource	BMCTicket
TargetRO	Name of the resource object	BMCTicketRO
BatchSize	Use this attribute to specify the number of records that must be included in each batch.	The default value is 1000.
NoOfBatches	Use this attribute to specify the total number of batches that must be reconciled. The number of records in each batch is specified by the BatchSize attribute	Specify All if you want to reconcile all the batches. This is the default value. Specify an integer value if you want to reconcile only a fixed number of batches.
Status	Use this attribute to specify the Ticket status for which you want to reconcile Tickets.	5 (closed) Note: You must not change this value.

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

3.1.2 Adding Custom Attributes for Reconciliation

Note:

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

By default, the attributes listed in the "Reconciliation Module" section 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:

Note:

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

See Also:

Oracle Identity Manager Design Console for detailed instructions on performing the following steps

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.

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.

   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.

3.2 Configuring Provisioning

Note:

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

As mentioned earlier in this guide, provisioning involves creating or modifying a Ticket information on the target system through Oracle Identity Manager.

This section discusses the following topics related to configuring provisioning:

• Compiling Adapters

• Adding Custom Attributes for Provisioning

3.2.1 Compiling Adapters

Note:

You must perform the procedure described in this section if you want to use the provisioning features of Oracle Identity Manager for this target system.

You need not perform the procedure to compile adapters if you have performed the procedure described in "Installing the Connector on Oracle Identity Manager Release 9.1.0 or Later".

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

See Also:

The "Supported Functionality" section for a listing of the provisioning functions that are available with this connector

• adpBMCCreateTicket

• adpBMCUpdateTicket

• adpBMCTKTUserId

• adpBMCUpdateLookupTicket

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.

See Also:

Oracle Identity Manager Tools Reference Guide for information about using the Adapter Factory and Adapter Manager forms

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 Custom 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. You needs to map additional target application specific attributes for provisioning as follows:

See Also:

Oracle Identity Manager Design Console 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.

   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.

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

   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.

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

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

Oracle Identity Manager Design Console Guide for detailed information about each step of the following procedure

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 for 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 "Adding Custom Attributes for Provisioning" section.