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

3 Using the Connector

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

Note:

These sections provide 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 Performing First-Time Reconciliation

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 user records from the target system are brought into Oracle Identity Manager.

The following is the sequence of steps involved in reconciling all existing user records:

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.

  1. Perform lookup field synchronization by running the scheduled tasks provided for this operation.

    See Section 3.2, "Scheduled Task for Lookup Field Synchronization" for information about the attributes of the scheduled tasks for lookup field synchronization.

    See Section 3.4, "Configuring the Reconciliation Scheduled Tasks" for information about running scheduled tasks.

  2. Perform user reconciliation by running the scheduled task for user reconciliation.

    See Section 3.3.4, "Reconciliation Scheduled Tasks" for information about the attributes of this scheduled task.

    See Section 3.4, "Configuring the Reconciliation Scheduled Tasks" for information about running scheduled tasks.

After first-time reconciliation, depending on the mode in which you configure the connector, one of the following parameters of the BMC 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 resource

From the next reconciliation run onward, only target system user records that are added or modified 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 user reconciliation scheduled task.

3.2 Scheduled Task for Lookup Field Synchronization

The BMC 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 the Reconciliation 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

ServerName

Enter the name of the target system IT resource.

Default value: BMC

TargetRO

This attribute holds the name of the resource object against which lookup field synchronization reconciliation runs must be performed.

Value: BMCRO

Note: For the resource object shipped with this connector, you must not change the value of this attribute. However, if you create a copy of the resource object, then you must enter the unique name of that resource object as the value of this attribute.

LookUpCodeKey

Enter the name of the lookup field whose values have to be synchronized with the corresponding lookup definitions in Oracle Identity Manager. You can enter one of the following values:

  • Region

  • Site

  • Department

  • Organization

  • SiteGroup

  • SiteID

  • SupportGroupCompany

  • SupportGroupOrganization

  • SupportGroupName

  • RelationshipRole

  • SupportGroupID

  • PrimaryCenterCode

Default value: SupportGroupID

LookUpFieldCode

Enter the name of the lookup definition corresponding to the lookup field name that you specify in LookUpCodeKey attribute. You can enter one of the following values:

  • Lookup.BMC.Region

  • Lookup.BMC.Site

  • Lookup.BMC.Department

  • Lookup.BMC.Company

  • Lookup.BMC.Organization

  • Lookup.BMC.SiteGroup

  • Lookup.BMC.SiteID

  • Lookup.BMC.SupportCompany

  • Lookup.BMC.SupportOrganization

  • Lookup.BMC.SupportGroup

  • Lookup.BMC.RelationshipRole

  • Lookup.BMC.SupportGroupID

  • Lookup.BMC.PrimaryCentercode

  • Lookup.BMC.PagerSw

For example, if you enter SupportGroupID as the LookUpCodeKey value, then you must enter Lookup.BMC.SupportGroupID as the LookUpFieldCode value.

Default value: Lookup.BMC.SupportGroupID

LookupFormName

Enter the form name on the target system corresponding to the lookup field name that you specify in LookUpCodeKey attribute. You can enter one of the following values:

  • CTM:Region

  • SIT:Site Alias Company LookUp

  • CTM:People Organization

  • CTM:People Organization

  • CTM:People Organization

  • SIT:Site Group

  • SIT:Site

  • CTM:Support Group

  • CTM:Support Group

  • CTM:Support Group

  • SYS:Menu Items

For example, if you enter SupportGroupID as the LookUpCodeKey value, then you must enter CTM:Support Group as the LookupFormName value.

Default value: CTM:Support Group


3.3 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:

3.3.1 Full Reconciliation

Full reconciliation involves reconciling all existing user records 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 records are reconciled in Oracle Identity Manager.

To perform a full reconciliation run:

  • Ensure that the TrustedTimeStamp and NonTrustedTimeStamp parameters of the BMC IT resource are set to None.

  • Specify All as the value of the NumberOfBatches attribute of the user 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 records created or modified after this time stamp are considered for reconciliation. This is incremental reconciliation.

3.3.2 Limited Reconciliation

By default, all target system records that are added or modified after the last reconciliation run are reconciled during the current reconciliation run. You can customize this process by specifying the subset of added or modified target system records that must be reconciled. You do this by creating filters for the reconciliation module.

Creating a filter involves specifying a value for a target system attribute, which will be used in the query SELECT criteria to retrieve the records to be reconciled. You can specify values for any one or a combination of the following target system attributes:

  • First Name

  • Last Name

  • Status

  • Notification Method

If you want to use multiple target system attributes to filter records, then you must also specify the logical operator (AND or OR) that you want to apply to the combination of target system attributes that you select.

For example, suppose you specify the following values for these attributes:

  • First Name: John

  • Last Name: Doe

  • Status: 1

  • Notification Method: 1

  • Operator: OR

Because you are using the OR operator, during reconciliation, only user records for which any one of these criteria is met are reconciled. If you were to use the AND operator, then only user records for which all of these criteria are met are reconciled.

See Section 3.3.4, "Reconciliation Scheduled Tasks" for information about the scheduled tasks attributes and the logical operator that you want to apply.

Adding New Filter Attributes

If you want to add a filter attribute to the predefined list of filter attributes, then:

  1. Add the filter attribute in the scheduled task or the IT resource.

    For example, if you want to add the Middle Name attribute as a filter attribute, then add Middle Name either as a scheduled task attribute or an IT resource parameter. See one of the following guides for information about adding attributes in scheduled tasks and parameters in IT resources:

    • 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

  2. Depending on whether you are adding a filter attribute for user or group reconciliation, create an entry in one of the following lookup definitions:

    • For a user attribute

      Create an entry in the Lookup.BMC.UM.QueryAttribute lookup definition. Use the following format to create the entry:

      • Code Key: Enter the name of the scheduled task attribute or IT resource parameter that you create in the preceding step.

      • Decode: Enter a value in the following format:

        CONNECTOR_OBJECT_TYPE,TARGET_SYSTEM_COLUMN_NAME,DATA_TYPE
        

        In this format:

        - CONNECTOR_OBJECT_TYPE can be either ScheduledTask or ITResource depending on whether you add the filter attribute as an attribute of the scheduled task or as a parameter of the IT resource.

        - TARGET_SYSTEM_COLUMN_NAME is the name of the target system column corresponding to the filter attribute.

        - DATA_TYPE is the data type of the target system column. It is optional to enter the data type.

      The following table shows the default entries in the Lookup.BMC.UM.QueryAttribute lookup definition:

      Note:

      In these default Decode values, Status, Default Notify Mechanism, First Name, Last Name, and Last Modified Date are the names of target system columns. If the name of any of these columns is different on your target system installation, then replace the column name in the Decode value with the actual name of the target system column. For example, if the name of the Default Notify Mechanism column is Notify Mechanism 1 on your target system installation, then use the following as the Decode value:

      ScheduledTask,Notify Mechanism 1

      Code Key Decode

      Status

      ScheduledTask,Status,number

      Notification Method

      ScheduledTask,Default Notify Mechanism

      First Name

      ScheduledTask,First Name

      Last Name

      ScheduledTask,Last Name

      NonTrustedTimeStamp

      ITResource,Last Modified Date,Date

      TrustedTimeStamp

      ITResource,Last Modified Date,Date


    • For a group attribute

      Create an entry in the Lookup.BMC.UM.Grp.QueryAttribute lookup definition. The format of the entry is the same as the format for the Lookup.BMC.UM.QueryAttribute lookup definition described earlier. The following table shows the default entries in the Lookup.BMC.UM.Grp.QueryAttribute lookup definition:

      Note:

      As mentioned in the preceding Note, modify the Decode value so that the column name is the same as the actual column name on your target system installation.

      Code Key Decode

      Status

      ScheduledTask,Status

      NonTrustedTimeStamp

      ITResource,Last Modified Date,Date

      TrustedTimeStamp

      ITResource,Last Modified Date,Date


  3. Specify a value for the scheduled task attribute or the IT resource parameter that you create in Step 1. See one of the following sections for information about the procedure:

3.3.3 Batched Reconciliation

During a reconciliation run, all changes in the target system records 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 these problems.

To configure batched reconciliation, you must specify values for the following user reconciliation scheduled task attributes:

  • BatchSize: Use this attribute to specify the number of records that must be included in each batch. The default value is 1000.

  • NumberOfBatches: Use this attribute to specify the total number of batches that must be reconciled. The default value is All.

If you specify a value other than All, then some of the newly added or modified user records may not get reconciled during the current reconciliation run. The following example illustrates this:

Suppose you specify the following values while configuring the scheduled tasks:

  • BatchSize: 20

  • NumberOfBatches: 10

Suppose that 314 user records were created or modified after the last reconciliation run. Of these 314 records, only 200 records would be reconciled during the current reconciliation run. The remaining 114 records would be reconciled during the next reconciliation run.

You specify values for the BatchSize and NumberOfBatches attributes by following the instructions described in Section 3.3.4, "Reconciliation Scheduled Tasks."

3.3.4 Reconciliation Scheduled Tasks

When you run the Connector Installer or import the connector XML file, the following reconciliation scheduled tasks are automatically created in Oracle Identity Manager:

  • BMC Trusted User Reconciliation

    This scheduled task is used to reconcile user data in the trusted source (identity management) mode of the connector.

  • BMC Non Trusted User Reconciliation

    This scheduled task is used to reconcile user data in the target resource (account management) mode of the connector.

You must specify values for the attributes of these scheduled tasks. Table 3-2 describes the attributes of both scheduled tasks. See Section 3.4, "Configuring the Reconciliation 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.

  • Values (either default or user-defined) must be assigned to all the attributes. If even a single attribute value were left empty, then reconciliation would not be performed.

Table 3-2 Attributes of the User Reconciliation Scheduled Tasks

Attribute Description

ServerName

Enter the name of the IT resource for the target system installation from which you want to reconcile user records

Default value: BMC

IsTrusted

A value of Yes implies that you want to configure the connector for trusted source reconciliation.

A value of No implies that you want to configure the connector for target resource reconciliation.

The default value of this attribute in the BMC Non Trusted User Reconciliation scheduled task is No.

The default value of this attribute in the BMC Trusted User Reconciliation scheduled task is Yes.

Note: It is recommended that you do not change the value of this attribute.

Target RO

Enter the name of the resource object against which reconciliation runs must be performed.

Default value: BMCRO

XellerateOrganisation

Enter the name of the Oracle Identity Manager organization in which users reconciled from the target system must be created.

Default value: Xellerate Users

Note: This attribute is specific to the scheduled task for trusted source reconciliation.

BatchSize

Enter the number of records that must be included in each batch fetched from the target system.

If you do not want to implement batched reconciliation, then specify nodata.

Default value: 1000

See Also: Section 3.3.3, "Batched Reconciliation"

NoOfBatches

This attribute specifies the number of batches to be reconciled. Enter All if you want to reconcile all the batches. This is the default value.

Enter an integer value if you want to reconcile only a fixed number of batches.

Default value: All

Sample value: 50

The number of records in each batch is specified by the BatchSize attribute.

See Also: Section 3.3.3, "Batched Reconciliation"

First Name

This is a filter attribute. Use this attribute to specify the first name of the user whose records you want to reconcile.

If you do not want to use this filter attribute, then specify Nodata.

Default value: Nodata

See Also: Section 3.3.2, "Limited Reconciliation"

Last Name

This is a filter attribute. Use this attribute to specify the last name of the user whose records you want to reconcile.

If you do not want to use this filter attribute, then specify Nodata.

Default value: Nodata

See Also: Section 3.3.2, "Limited Reconciliation"

Notification Method

This is a filter attribute. Use this attribute to specify the notification method for which you want to reconcile user records. The notification method value can be one of the following numbers:

  • 0 (None)

  • 1 (Alert)

  • 2 (Email)

  • 3 (User Default)

If you do not want to use this filter attribute, then specify Nodata.

Default value: Nodata

See Also: Section 3.3.2, "Limited Reconciliation"

Status

This is a filter attribute. Use this attribute to specify the user status for which you want to reconcile user records. The status can be one of the following numbers:

  • 0 (Proposed)

  • 1 (Enabled)

  • 2 (Offline)

  • 3 (Obsolete)

  • 4 (Archive)

  • 5 (Delete)

If you do not want to use this filter attribute, then specify Nodata.

Default value: Nodata

See Also: Section 3.3.2, "Limited Reconciliation"

Operator

This is a filter attribute. Enter one of the following values to specify the logical operator to be applied to the filter attribute:

  • AND

  • OR

If you do not want to use this filter attribute, then specify Nodata.

Default value: Nodata

See Also: Section 3.3.2, "Limited Reconciliation"

DateFormat

Enter the format in which date values are stored on the target system. During reconciliation, this date format is used to validate date values fetched from the target system.

Default value: MM/dd/yyyy hh:mm:ss

QueryAttribute

Enter the name of the lookup definition that stores details of the query attributes.

The default value is Lookup.BMC.UM.QueryAttribute

See Also: Section 3.3.2, "Limited Reconciliation"


3.4 Configuring the Reconciliation Scheduled Tasks

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

BMC Lookup Reconciliation

This scheduled task is used to synchronize the values of 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.

BMC Trusted User Reconciliation

This scheduled task is used for reconciling user data when the target system is configured as a trusted source. See Section 3.3.4, "Reconciliation Scheduled Tasks" for information about this scheduled task.

BMC Non Trusted User Reconciliation

This scheduled task is used for reconciling user data when the target system is configured as a target resource. See Section 3.3.4, "Reconciliation Scheduled Tasks" for information about this scheduled task.


To configure a scheduled task:

  1. Log in to the Administrative and User Console.

  2. Perform one of the following:

    1. If you are using Oracle Identity Manager release 9.1.0.x, expand Resource Management, and then click Manage Scheduled Task.

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

  3. Search for and open the scheduled task as follows:

    • If you are using Oracle Identity Manager release 9.1.0.x, then:

      1. On the Scheduled Task Management page, enter the name of the scheduled task as the search criteria and then click Search.

      2. In the search results table, click the edit icon in the Edit column for the scheduled task.

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

      1. On the Welcome to Oracle Identity Manager Advanced Administration page, in the System Management region, click Search Scheduled Jobs.

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

      3. In the search results table on the left pane, click the scheduled job in the Job Name column.

  4. Modify the details of the scheduled task. To do so:

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

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

  5. Specify values for the attributes of the scheduled task. To do so:

    Note:

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

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

3.5 Performing Provisioning Operations

Provisioning a resource for an OIM User involves using Oracle Identity Manager to create a target system account 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:

Oracle Identity Manager Connector Concepts for information about the types of provisioning

This section discusses the following topics:

3.5.1 Direct Provisioning

To provision a resource by using the direct provisioning approach:

  1. Log in to the Administrative and User Console.

  2. If you want to first create an OIM User and then provision a target system account, then:

    • If you are using Oracle Identity Manager release 9.1.0.x, then:

      1. From the Users menu, select Create.

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

      1. On the Welcome to Identity Administration page, in the Users region, click Create User.

      2. On the Create User page, enter values for the OIM User fields, and then click Save.

  3. If you want to provision a target system account to an existing OIM User, then:

    • If you are using Oracle Identity Manager release 9.1.0.x, then:

      1. From the Users menu, select Manage.

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

      1. On the Welcome to Identity Administration page, search for the OIM User by selecting Users from the list on the left pane.

      2. From the list of users displayed in the search results, select the OIM User. The user details page is displayed on the right pane.

  4. 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.1.0.x, then:

      1. On the User Detail page, select Resource Profile from the list at the top of the page.

      2. On the Resource Profile page, click Provision New Resource.

    • If you are using Oracle Identity Manager release 11.1.1, then:

      1. On the user details page, click the Resources tab.

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

  5. On the Step 1: Select a Resource page, select BMCRO from the list and then click Continue.

  6. On the Step 2: Verify Resource Selection page, click Continue.

  7. On the Step 5: Provide Process Data for BMC User page, enter the details of the account that you want to create on the target system and then click Continue.

  8. On the Step 5: Provide Process Data for BMC Update Support Groups and Roles page, if required, enter details of the support groups and roles and then click Continue.

  9. On the Step 6: Verify Process Data page, verify the data that you have provided and then click Continue.

  10. The "Provisioning has been initiated" message is displayed. Perform one of the following steps:

    • If you are using Oracle Identity Manager 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:

      1. Close the window displaying the "Provisioning has been initiated" message.

      2. On the Resources tab, click Refresh to view the newly provisioned resource.

3.5.2 Request-Based Provisioning

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 target system account. This request is then approved by the approver.

3.5.2.1 End User'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 steps

  1. Log in to the Administrative and User Console.

  2. On the Welcome page, click Advanced in the upper-right corner of the page.

  3. On the Welcome to Identity Administration page, click the Administration tab, and then click the Requests tab.

  4. From the Actions menu on the left pane, select Create Request.

    The Select Request Template page is displayed.

  5. From the Request Template list, select Provision Resource and click Next.

  6. On the Select Users page, specify a search criterion in the fields to search for the user that you want to provision the resource, and then click Search. A list of users that match the search criterion you specify is displayed in the Available Users list.

  7. From the Available Users list, select the user to whom you want to provision the account..

    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.

  8. Click Move or Move All to include your selection in the Selected Users list, and then click Next.

  9. On the Select Resources page, click the arrow button next to the Resource Name field to display the list of all available resources.

  10. From the Available Resources list, select BMCRO, move it to the Selected Resources list, and then click Next.

  11. On the Resource Details page, enter details of the account that must be created on the target system, and then click Next.

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

  13. If you click the request ID, then the Request Details page is displayed.

  14. To view details of the approval, on the Request Details page, click the Request History tab.

3.5.2.2 Approver's Role in Request-Based Provisioning

The following are steps performed by the approver in a request-based provisioning operation:

The following are steps that the approver can perform:

  1. Log in to the Administrative and User Console.

  2. On the Welcome page, click Self-Service in the upper-right corner of the page.

  3. On the Welcome to Identity Manager Self Service page, click the Tasks tab.

  4. On the Approvals tab, in the first section, you can specify a search criterion for request task that is assigned to you.

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

3.6 Switching Between Request-Based Provisioning and Direct Provisioning on Oracle Identity Manager Release 11.1.1

Note:

It is assumed that you have performed the procedure described in Section 2.6.5, "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:

  1. Log in to the Design Console.

  2. Disable the Auto Save Form feature as follows:

    1. Expand Process Management, and then double-click Process Definition.

    2. Search for and open the BMCPROCESS process definition.

    3. Deselect the Auto Save Form check box.

    4. Click the Save icon.

  3. If the Self Request Allowed feature is enabled, then:

    1. Expand Resource Management, and then double-click Resource Objects.

    2. Search for and open the BMCRO resource object.

    3. Deselect the Self Request Allowed check box.

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

  1. Log in to the Design Console.

  2. Enable the Auto Save Form feature as follows:

    1. Expand Process Management, and then double-click Process Definition.

    2. Search for and open the BMCPROCESS process definition.

    3. Select the Auto Save Form check box.

    4. Click the Save icon.

  3. If you want to enable end users to raise requests for themselves, then:

    1. Expand Resource Management, and then double-click Resource Objects.

    2. Search for and open the BMCRO resource object.

    3. Select the Self Request Allowed check box.

    4. Click the Save icon.