| Oracle® Identity Manager Connector Guide for BMC Ticket Management Release 9.0.4 Part Number E10393-01 |
|
|
View PDF |
| Oracle® Identity Manager Connector Guide for BMC Ticket Management Release 9.0.4 Part Number E10393-01 |
|
|
View PDF |
After you deploy the connector, you must configure it to meet your requirements. This chapter discusses the following connector configuration procedures:
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.As mentioned earlier in this guide, reconciliation involves duplicating in Oracle Identity Manager additions of and modifications to user accounts on the target system. This section discusses the following topics related to configuring reconciliation:
When you perform the procedure described in the "Step 5: Importing the Connector XML File" section, the scheduled tasks for lookup fields and nontrusted user reconciliations are automatically created in Oracle Identity Manager. To configure these scheduled tasks:
Expand the Xellerate Administration folder.
Select Task Scheduler.
Click Find. The details of the predefined scheduled tasks are displayed on two different tabs.
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 ERROR status to the task.
Ensure that the Disabled and Stop Execution check boxes are not selected.
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.
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.
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 attributesClick 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.
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.
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.
You must specify values for the following attributes of the BMC 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.After you specify values for these scheduled task attributes, proceed to Step 10 of the procedure to create scheduled tasks.
Note:
Attribute values are predefined in the connector XML file that you import. Specify values only for those attributes that you want to change.After you specify values for these scheduled task attributes, proceed to Step 10 of the procedure to create scheduled tasks.
Note:
In this section, the term "attribute" refers to the identity data fields that store user 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 User 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 stepsDetermine the Database ID for the attribute that you want to add:
Open the Remedy Administrator Console.
Expand Servers.
Double-click Forms.
Double-click the SHR:HPD:HelpDesk form.
Double-click the field whose Database ID you want to determine.
On the Database tab, the Database ID of the field is displayed as the value of the ID field.
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:
OimAttributeName=Database_ID_in_BMC_Remedy
For example:
Ticket.EmailAddress=260000002
In this example, EmailAddress is the reconciliation field and 261000010 is the equivalent Database ID in BMC Remedy System.
In the resource object definition, add a reconciliation field corresponding to the new attribute as follows:
Open the Resource Objects form. This form is in the Resource Management folder.
Click Query for Records.
On the Resource Objects Table tab, double-click the BMCTicketRO resource object to open it for editing.
On the Object Reconciliation tab, click Add Field to open the Add Reconciliation Field dialog box.
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 Ticket.EmailAddress=260000002 line in Step 2, then you must specify Ticket.EmailAddress as the attribute name.
From the Field Type list, select a data type for the field.
For example: String
Save the values that you enter, and then close the dialog box.
If required, repeat Steps d through g to map more fields.
Modify the process definition to include the mapping between the newly added attribute and the corresponding reconciliation field as follows:
Open the Process Definition form. This form is in the Process Management folder.
On the Reconciliation Field Mappings tab, click Add Field Map to open the Add Reconciliation Field Mapping dialog box.
Enter the required values, save the values that you enter, and then close the dialog box.
If required, repeat Steps b and c to map more fields.
Note:
In this section, the term "attribute" refers to the identity data fields that store user data.As mentioned earlier in this guide, provisioning involves creating or modifying a Ticket information on the target system through Oracle Identity Manager. Refer to the "Supported Functionality" section for a listing of the provisioning functions that are available with this connector.
This section discusses the following topics related to configuring provisioning:
Note:
You must perform this procedure if you want to use the provisioning features of Oracle Identity Manager for this target system.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 connectoradpBMCCREATETICKET
adpBMCUPDATETICKET
You must compile these adapters before they can be used in provisioning operations.
To compile adapters by using the Adapter Manager form:
Open the Adapter Manager form.
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.Click Start. Oracle Identity Manager compiles the selected adapters.
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 formsTo view detailed information about an adapter:
Highlight the adapter in the Adapter Manager form.
Double-click the row header of the adapter, or right-click the adapter.
Select Launch Adapter from the shortcut menu that is displayed. Details of the adapter are displayed.
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 GuideModify 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.Add a new column in the process form.
Open the process form. This form is in the Development Tools folder of the Oracle Identity Manager Design Console.
Click Create New Version.
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.
From the Current Version list, select the newly created version.
On the Additional Columns tab, click Add.
Specify the new field name and other values.
Add a new variable in the variable list.
Open the Adapter Factory form. This form is in the Development Tools folder of the Oracle Identity Manager Design Console.
Click the Query for Records icon.
On the Adapter Factory Table tab, double-click the adpBMCCREATETICKET adapter from the list.
On the Variable List tab, click Add.
In the Add a Variable dialog box, specify the required values and then save and close the dialog box.
Define an additional adapter task for the newly added variable in the adpBMCCREATETICKETadapter.
On the Adapter Tasks tab of the Adapter Factory form, click Add.
In the Adapter Task Selection dialog box, select Functional Task, select Java from the list of functional task types, and then click Continue.
In the Object Instance Selection dialog box, select Persistent Instance and then click Continue.
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.
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.
Repeat Steps b through g to create more adapter tasks.
Create an additional adapter task to set the input variable.
Open the Adapter Factory form. This form is in the Development Tools folder in the Oracle Identity Manager Design Console.
On the Adapter Tasks tab, click Add.
In the Adapter Task Selection dialog box, select Logic Task, select SET VARIABLE from the list, and then click Continue.
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.
Map the process form columns and adapter variables for the Create User process task as follows:
Open the Process Definition form. This form is in the Process Management folder of the Design Console.
Click the Query for Records icon.
On the Process Definition Table tab, double-click the BMCTicketProcess process.
On the Tasks tab, double-click the Create User task.
In the Closing Form dialog box, click Yes.
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.
You can create tickets for multiple target applications on BMC Ticket Management. To extend this feature to provisioning operations performed through Oracle Identity Manager, you can create a resource object, process form, IT resource, and Process definition for each target application.
To configure the connector for a specific target application of BMC Ticket Management:
See Also:
Oracle Identity Manager Design Console Guide for detailed information about each step of the following procedureCreate 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.
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.
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.
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.
To add custom attributes for provisioning, perform the procedure described in the "Adding Custom Attributes for Provisioning" section.
Note:
Perform this procedure only if you want to configure the connector for multiple installations of Sun Java System Directory.You may want to configure the connector for multiple installations of Sun Java System Directory. The following example illustrates this requirement:
The Tokyo, London, and New York offices of Acme Multinational Inc. have their own installations of Sun Java System Directory. The company has recently installed Oracle Identity Manager, and they want to configure Oracle Identity Manager to link all the installations of Sun Java System Directory.
To meet the requirement posed by such a scenario, you must configure the connector for multiple installations of Sun Java System Directory.
To configure the connector for multiple installations of the target system:
See Also:
Oracle Identity Manager Design Console Guide for detailed instructions on performing each step of this procedureCreate and configure one IT resource for each target system installation.
The IT Resources form is in the Resource Management folder. An 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 IT resource type.
Configure reconciliation for each target system installation. Refer to the "Configuring Reconciliation" section for instructions. Note that you only need to modify the attributes that are used to specify the IT resource and to specify whether or not the target system installation is to be set up as a trusted source.
If required, modify the fields to be reconciled for the Xellerate User resource object.
