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.First-time reconciliation involves synchronizing lookup definitions in Oracle Identity Manager with the lookup fields of the target system, and performing full reconciliation. In full reconciliation, all existing tickets (of closed status) from the target system are brought into Oracle Identity Manager.
The following is the sequence of steps involved in reconciling all existing tickets:
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.
Perform lookup field synchronization by running the scheduled task provided for this operation.
See Section 3.2, "Scheduled Task for Lookup Field Synchronization" for information about the attributes of the scheduled task for lookup field synchronization.
See Section 3.4, "Configuring Scheduled Tasks" for information about running scheduled tasks.
Perform ticket reconciliation by running the scheduled task for ticket reconciliation.
See Section 3.3.4, "Reconciliation Scheduled Task" for information about the attributes of this scheduled task.
See Section 3.4, "Configuring Scheduled Tasks" for information about running scheduled tasks.
After first-time reconciliation, the LastReconTime parameter of the BMCTicket IT resource is automatically set to the time stamp at which the reconciliation run began.
See Also:
Section 2.4.3, "Configuring the IT Resource" for information about the parameters of the IT resourceFrom the next reconciliation run onward, only target system tickets that are closed after the time stamp stored in the IT resource are considered for incremental reconciliation. These records are brought to Oracle Identity Manager when you configure and run the scheduled task for ticket reconciliation.
The BMCTicket Lookup Reconciliation scheduled task is used for lookup field synchronization.
Table 3-1 describes the attributes of this scheduled task. See Section 3.4, "Configuring Scheduled Tasks" for information about configuring 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.Table 3-1 Attributes of the Scheduled Task for Lookup Field Synchronization
| Attribute | Description |
|---|---|
|
Server |
Enter the name of the target system IT resource. Default value: |
|
LookupCode |
Enter the name of the lookup definition with which values are to be synchronized. You can enter one of the following values:
There is no default value for this attribute. |
|
LookUpName |
Enter the name of the lookup field whose values have to be populated. You can enter one of the following values:
There is no default value for this attribute. |
As mentioned earlier in this guide, reconciliation involves duplicating in Oracle Identity Manager the creation of and modifications to tickets on the target system. This section discusses the following topics related to configuring reconciliation:
Full reconciliation involves reconciling all closed tickets from the target system into Oracle Identity Manager. After you deploy the connector, you must first perform full reconciliation. In addition, you can switch from incremental reconciliation to full reconciliation whenever you want to ensure that all target system tickets are reconciled in Oracle Identity Manager.
To perform a full reconciliation run:
Ensure that the LastReconTime parameter of the BMCTicket IT resource does not contain a value.
Specify 5 as the value of the Status attribute of the ticket reconciliation scheduled task.
Specify All as the value of the NumberOfBatches attribute of the ticket reconciliation scheduled task.
At the end of the reconciliation run, the LastReconTime parameter of the BMCTicket IT resource is automatically set to the time stamp at which the run started. From the next reconciliation run onward, only tickets created or modified after this time stamp are considered for reconciliation. This is incremental reconciliation.
By default, all target system tickets that have been closed after the last reconciliation run are reconciled during the current reconciliation run. In other words, target system tickets that have a status of 5 (closed) are reconciled. You can customize this process by specifying the status of tickets that must be reconciled. You do this by creating filters for the reconciliation module.
For this connector, you create a filter by specifying a value for the Status attribute of the BMCTicket Reconciliation scheduled task while performing the procedure described in Section 3.4, "Configuring Scheduled Tasks."
For example, if you specify 4 as the value of the Status attribute, then all tickets on the target system that have the status Pending are reconciled.
During a reconciliation run, all changes in the target system records (tickets) are reconciled into Oracle Identity Manager. Depending on the number of records to be reconciled, this process may require a large amount of time. In addition, if the connection breaks during reconciliation, then the process would take longer to complete. You can configure batched reconciliation to avoid such problems.
To configure batched reconciliation, you must specify values for the following attributes of the reconciliation scheduled task:
BatchSize: Use this attribute to specify the number of records that must be included in each batch.
NumberOfBatches: Use this attribute to specify the total number of batches that must be reconciled. If you do not want to use batched reconciliation, specify All as the value of this attribute.
Note:
If you specifyAll as the value of this attribute, then the values of the BatchSize attribute is ignored.You specify values for these attributes by following the instructions described in Section 3.3.4, "Reconciliation Scheduled Task."
After you configure batched reconciliation, if reconciliation fails during a batched reconciliation run, then refer to the log file for information about the batch at which reconciliation has failed. The log file provides the following information about batched reconciliation:
Serial numbers of the batches that have been successfully reconciled
User IDs associated with the records with each batch that has been successfully reconciled
If the batched reconciliation run fails, then the serial number of the batch that has failed
When you run the Connector Installer or import the connector XML file, the BMCTicket Reconciliation scheduled task is automatically created in Oracle Identity Manager. This scheduled task is used to reconcile ticket data from the target system.
You must specify values for the following attributes of the BMCTicket Reconciliation scheduled task. Table 3-2 describes the attributes of this scheduled task. See Section 3.4, "Configuring Scheduled Tasks" for information about configuring 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.Table 3-2 Attributes of the Reconciliation Scheduled Task
| Attribute | Description |
|---|---|
|
ServerName |
Enter the name of the IT resource. Default value: |
|
TargetRO |
Enter the name of the resource object against which reconciliation runs must be performed. Default value: |
|
BatchSize |
Enter the number of records that must be included in each batch fetched from the target system. Default value: This attribute is used in conjunction with the NumberOfBatches attribute. All three attributes are discussed in Section 3.3.3, "Batched Reconciliation." |
|
NumberOfBatches |
Enter the number of batches that must be reconciled. Default value: Sample value: This attribute is used in conjunction with the BatchSize attribute. All three attributes are discussed in detail in Section 3.3.3, "Batched Reconciliation." If you accept the default value ( |
|
Status |
Specifies the ticket status for which you want to reconcile tickets. Default value: |
You can apply this procedure to configure the scheduled tasks for lookup field synchronization and reconciliation.
Table 3-3 lists the scheduled tasks that form part of the connector.
Table 3-3 Scheduled Tasks for Lookup Field Synchronization and Reconciliation
| Scheduled Task | Description |
|---|---|
|
BMCTicket Lookup Reconciliation |
This scheduled task is used to synchronize the values of the Category, Item, and Type lookup fields between Oracle Identity Manager and the target system. See Section 3.2, "Scheduled Task for Lookup Field Synchronization" for information about this scheduled task. |
|
BMCTicket Reconciliation |
This scheduled task is used for ticket reconciliation. See Section 3.3.4, "Reconciliation Scheduled Task" for information about this scheduled task. |
Depending on the Oracle Identity Manager release that you are using, perform the procedure described in one of the following sections:
To configure a scheduled task:
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 FAILED 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.
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.
Suppose the reconciliation scheduled task for the connector is running and records are being reconciled. If you want to stop the reconciliation process:
To configure a scheduled task:
Log in to the Administrative and User Console.
Perform one of the following:
If you are using Oracle Identity Manager release 9.1.0.x, expand Resource Management, and then click Manage Scheduled Task.
If you are using Oracle Identity Manager release 11.1.1, then on the Welcome to Oracle Identity Manager Self Service page, click Advanced in the upper-right corner of the page.
Search for and open the scheduled task as follows:
If you are using Oracle Identity Manager release 9.1.0.x, then:
On the Scheduled Task Management page, enter the name of the scheduled task as the search criteria and then click Search.
In the search results table, click the edit icon in the Edit column for the scheduled task.
On the Scheduled Task Details page where the details of the scheduled task that you selected is displayed, click Edit.
If you are using Oracle Identity Manager release 11.1.1, then:
On the Welcome to Oracle Identity Manager Advanced Administration page, in the System Management region, click Search Scheduled Jobs.
On the left pane, in the Search field, enter the name of the scheduled job as the search criterion. Alternatively, you can click Advanced Search and specify the search criterion.
In the search results table on the left pane, click the scheduled job in the Job Name column.
Modify the details of the scheduled task. To do so:
If you are using Oracle Identity Manager release 9.1.0.x, then on the Edit Scheduled Task Details page, modify the following parameters, and then click Continue:
Status: Specify whether you want to leave the task in the enabled state. In the enabled state, the task is ready for use.
Max Retries: Enter an integer value in this 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. The default value is 1.
Next Start: Use the date editor to specify the date when you want the task to run. After you select a date value in the date editor, you can modify the time value that is automatically displayed in the Next Start field.
Frequency: Specify the frequency at which you want the task to run.
If you are using Oracle Identity Manager release 11.1.1, then on the Job Details tab, you can modify the following parameters:
Retries: Enter an integer value in this field. This number represents the number of times the scheduler tries to start the job before assigning the Stopped status to the job.
Schedule Type: Depending on the frequency at which you want the job to run, select the appropriate schedule type.
Note:
See Oracle Fusion Middleware System Administrator's Guide for Oracle Identity Manager for detailed information about schedule types.In addition to modifying the job details, you can enable or disable a job.
Specify values for the attributes of the scheduled task. To do so:
Note:
Attribute values are predefined in the connector XML file that you import. Specify values only for those attributes that you want to change.If you are using Oracle Identity Manager release 9.1.0.x, then on the Attributes page, select the attribute from the Attribute list, specify a value in the field provided, and then click Update.
If you are using Oracle Identity Manager release 11.1.1, then on the Job Details tab, in the Parameters region, specify values for the attributes of the scheduled task.
After specifying the attributes, perform one of the following:
If you are using Oracle Identity Manager release 9.1.0.x, then click Save Changes to save the changes.
Note:
The Stop Execution option is not available in the Administrative and User Console. If you want to stop a task, then click Stop Execution on the Task Scheduler form of the Design Console.If you are using Oracle Identity Manager release 11.1.1, then click Apply to save the changes.
Note:
The Stop Execution option is available in the Administrative and User Console. You can use the Scheduler Status page to either start, stop, or reinitialize the scheduler.Provisioning a resource for an OIM User involves using Oracle Identity Manager to create a ticket on the target system for the user.
When you install the connector on Oracle Identity Manager release 11.1.1, the direct provisioning feature is automatically enabled. This means that the process form is enabled when you install the connector.
If you have configured the connector for request-based provisioning, then the process form is suppressed and the object form is displayed. In other words, direct provisioning is disabled when you configure the connector for request-based provisioning. If you want to revert to direct provisioning, then perform the steps described in Section 3.6, "Switching Between Request-Based Provisioning and Direct Provisioning on Oracle Identity Manager Release 11.1.1."
The following are types of provisioning operations:
See Also:
One of the following guides for information about the types of provisioningFor Oracle Identity Manager release 9.0.1 through 9.0.3.x and release 9.1.0.x: Oracle Identity Manager Connector Concepts
For Oracle Identity Manager release 11.1.1: Oracle Fusion Middleware User's Guide for Oracle Identity Manager
This section discusses the following topics:
To provision a resource by using the direct provisioning approach:
Log in to the Administrative and User Console.
If you want to first create an OIM User and then provision a ticket on the target system, then:
If you are using Oracle Identity Manager release 9.0.1 through 9.0.3.x or release 9.1.0.x, then:
From the Users menu, select Create.
On the Create User page, enter values for the OIM User fields and then click Create User.
If you are using Oracle Identity Manager release 11.1.1, then:
On the Welcome to Identity Administration page, in the Users region, click Create User.
On the Create User page, enter values for the OIM User fields, and then click Save.
If you want to provision a ticket to an existing OIM User, then:
If you are using Oracle Identity Manager release 9.0.1 through 9.0.3.x or release 9.1.0.x, then:
From the Users menu, select Manage.
Search for the OIM User and select the link for the user from the list of users displayed in the search results.
If you are using Oracle Identity Manager release 11.1.1, then:
On the Welcome to Identity Administration page, search for the OIM User by selecting Users from the list on the left pane.
From the list of users displayed in the search results, select the OIM User. The user details page is displayed on the right pane.
Depending on the Oracle Identity Manager release you are using, perform one of the following steps:
If you are using Oracle Identity Manager release 9.0.1 through 9.0.3.x or release 9.1.0.x, then:
On the User Detail page, select Resource Profile from the list at the top of the page.
On the Resource Profile page, click Provision New Resource.
If you are using Oracle Identity Manager release 11.1.1, then:
On the user details page, click the Resources tab.
From the Action menu, select Add Resource. Alternatively, you can click the add resource icon with the plus (+) sign. The Provision Resource to User page is displayed in a new window.
On the Step 1: Select a Resource page, select BMCTicketRO from the list and then click Continue.
On the Step 2: Verify Resource Selection page, click Continue.
On the Step 5: Provide Process Data for BMC Remedy Ticket page, specify the required values, and then click Continue.
On the Step 6: Verify Process Data page, verify the data that you have provided and then click Continue.
The "Provisioning has been initiated" message is displayed. Perform one of the following steps:
If you are using Oracle Identity Manager release 9.0.1 through 9.0.3.x or release 9.1.0.x, click Back to User Resource Profile. The Resource Profile page shows that the resource has been provisioned to the user.
If you are using Oracle Identity Manager release 11.1.1, then:
Close the window displaying the "Provisioning has been initiated" message.
On the Resources tab, click Refresh to view the newly provisioned resource.
Note:
The information provided in this section is applicable only if you are using Oracle Identity Manager release 11.1.1.A request-based provisioning operation involves both end users and approvers. Typically, these approvers are in the management chain of the requesters. The following sections discuss the steps to be performed by end users and approvers during a request-based provisioning operation:
Note:
The procedures described in these sections are built on an example in which the end user raises or creates a request for provisioning a ticket on the target system. This request is then approved by the approver.Section 3.5.2.1, "End User's Role in Request-Based Provisioning"
Section 3.5.2.2, "Approver's Role in Request-Based Provisioning"
The following steps are performed by the end user in a request-based provisioning operation:
See Also:
Oracle Fusion Middleware User's Guide for Oracle Identity Manager for detailed information about these stepsLog in to the Administrative and User Console.
On the Welcome page, click Advanced in the upper-right corner of the page.
On the Welcome to Identity Administration page, click the Administration tab, and then click the Requests tab.
From the Actions menu on the left pane, select Create Request.
The Select Request Template page is displayed.
From the Request Template list, select Provision Resource and click Next.
On the Select Users page, specify a search criterion in the fields to search for the user that you want to provision the resource (ticket), and then click Search. A list of users that match the search criterion you specify is displayed in the Available Users list.
From the Available Users list, select the user to whom you want to provision the resource.
If you want to create a provisioning request for more than one user, then from the Available Users list, select users to whom you want to provision the account.
Click Move or Move All to include your selection in the Selected Users list, and then click Next.
On the Select Resources page, click the arrow button next to the Resource Name field to display the list of all available resources.
From the Available Resources list, select BMCTicketRO, move it to the Selected Resources list, and then click Next.
On the Resource Details page, enter details of the ticket that must be created on the target system, and then click Next.
On the Justification page, you can specify values for the following fields, and then click Finish.
Effective Date
Justification
On the resulting page, a message confirming that your request has been sent successfully is displayed along with the Request ID.
If you click the request ID, then the Request Details page is displayed.
To view details of the approval, on the Request Details page, click the Request History tab.
The following are steps performed by the approver in a request-based provisioning operation:
The following are steps that the approver can perform:
Log in to the Administrative and User Console.
On the Welcome page, click Self-Service in the upper-right corner of the page.
On the Welcome to Identity Manager Self Service page, click the Tasks tab.
On the Approvals tab, in the first section, you can specify a search criterion for request task that is assigned to you.
From the search results table, select the row containing the request you want to approve, and then click Approve Task.
A message confirming that the task was approved is displayed.
Note:
It is assumed that you have performed the procedure described in Section 2.7.4, "Configuring Oracle Identity Manager for Request-Based Provisioning."On Oracle Identity Manager release 11.1.1, if you want to switch from request-based provisioning to direct provisioning, then:
Log in to the Design Console.
Disable the Auto Save Form feature as follows:
Expand Process Management, and then double-click Process Definition.
Search for and open the BMCTicketProcess process definition.
Deselect the Auto Save Form check box.
Click the Save icon.
If the Self Request Allowed feature is enabled, then:
Expand Resource Management, and then double-click Resource Objects.
Search for and open the BMCTicketRO resource object.
Deselect the Self Request Allowed check box.
Click the Save icon.
On Oracle Identity Manager release 11.1.1, if you want to switch from direct provisioning back to request-based provisioning, then:
Log in to the Design Console.
Enable the Auto Save Form feature as follows:
Expand Process Management, and then double-click Process Definition.
Search for and open the BMCTicketProcess process definition.
Select the Auto Save Form check box.
Click the Save icon.
If you want to enable end users to raise requests for themselves, then:
Expand Resource Management, and then double-click Resource Objects.
Search for and open the BMCTicketRO resource object.
Select the Self Request Allowed check box.
Click the Save icon.