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.
Reconciliation involves duplicating in Oracle Identity Manager the creation of and modifications to user accounts on the target system, designated as a target resource.
By default, user accounts are reconciled in batches of 50 records. The maximum batch size permitted by Oracle CRM On Demand is 100. To change the batch size, you can specify a value for the Batch Size attribute of the reconciliation scheduled job. If you provide a batch size greater than 100, then the connector considers the Batch Size as 100. See Configuring Scheduled Jobs for instructions to specify a value for this attribute.
During a reconciliation run:
For each account created on the target system, a resource is assigned to the corresponding OIM User.
Updates made to each account on the target system are propagated to the corresponding resource.
This section discusses the following topics related to configuring 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.
To perform a full reconciliation run, remove (delete) any values currently assigned to the Filter and the Latest Token attributes of the CRM On Demand User Target Reconciliation scheduled job. See Scheduled Job for Reconciliation for information about this scheduled job.
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.
The connector provides a Filter attribute that allows you to use any of the Oracle CRM On Demand resource attributes to filter the target system records. You can use any of the values specified in the Decode column of the Lookup.CRMOD.UM.ReconAttrMap lookup definition. See Lookup.CRMOD.UM.ReconAttrMap for more information.
You can perform limited reconciliation by creating filters for the reconciliation module. This connector provides a Filter attribute (a scheduled task attribute) that allows you to use Oracle CRM On Demand resource attributes to filter the target system records.
For detailed information about ICF Filters, see ICF Filter Syntax in Oracle Fusion Middleware Developing and Customizing Applications for Oracle Identity Manager.
While deploying the connector, follow the instructions in Configuring Scheduled Jobs to specify attribute values.
Learn about the reconciliation rule for this connector and how to view it.
The following is the process-matching rule:
Rule name: CRMOD Recon Rule
Rule element: User Login Equals User Login Id
In this rule:
User Login is the User Login for Oracle Identity Manager:
User Login Id is the User Login for the target system.
Learn about the reconciliation action rules for this connector and how to view them.
Table 3-1 lists the action rules for target resource reconciliation.
Table 3-1 Action Rules for Target Resource Reconciliation
Rule Condition | Action |
---|---|
No Matches Found |
None |
One Entity Match Found |
Establish Link |
One Process Match Found |
Establish Link |
Note:
No action is performed for rule conditions that are not predefined for this connector. You can define your own action rule for such rule conditions.
After you deploy the connector, you can view the reconciliation action rules for target resource reconciliation by performing the following steps:
When you run the Connector Installer or import the connector XML file, the following reconciliation scheduled jobs are automatically created in Oracle Identity Manager:
This section discusses the following topics related to scheduled jobs:
The CRM On Demand Role Lookup Recon scheduled job is used for lookup field synchronization. This scheduled job is used to synchronize the roles available on the target system into the Lookup.CRMOD.Roles lookup definition.
You must specify values for the attributes described in Table 3-2 for this scheduled jobs. The procedure to configure a scheduled job is described later in the guide.
Table 3-2 Attributes of the Scheduled Job for Lookup Field Synchronization
Attribute | Description |
---|---|
Code Key Attribute |
Name of the connector or target system attribute that is used to populate the Code Key column of the lookup definition (specified as the value of the Lookup Name attribute) Default value: Note: You must not change the value of this attribute. |
Decode Attribute |
Name of the connector or target system attribute that is used to populate the Decode column of the lookup definition (specified as the value of the Lookup Name attribute) Default value: |
Filter |
Expression for filtering records that must be reconciled by the scheduled job By default, the value of this attribute is empty. Sample value: See Performing Limited Reconciliation for the syntax of this expression. |
IT Resource Name |
Name of the IT resource for the target system installation from which you want to reconcile user records Default value: |
Lookup Name |
Name of the lookup definition that maps each lookup definition with the data source from which values must be fetched Default value: |
Object Type |
Type of object whose values must be synchronized Default value: Note: You must not change the value of this attribute. |
The CRM On Demand User Target Reconciliation scheduled task is used to reconcile user data in the target resource (account management) mode of the connector.
Note:
The scheduled job does not support reconciliation of deleted records.
Table 3-3 describes the attributes of the scheduled job.
Table 3-3 Attributes of the Scheduled Job for Reconciliation
Attribute | Description |
---|---|
Batch Size |
Number of records that must be included in each batch Default value: |
Filter |
Expression for filtering records that must be reconciled by the scheduled job By default, the value of this attribute is empty. Sample value: See Performing Limited Reconciliation for the syntax of this expression. |
IT Resource Name |
Name of the IT resource for the target system installation from which you want to reconcile user records Default value: |
Latest Token |
Time stamp in the long format of the maximum value for the ModifiedDate attribute of the user records on the target system Note: Do not enter a value for this attribute. The reconciliation engine automatically enters a value for this attribute. If you set this attribute to an empty value, then incremental reconciliation operations fetch all the records (perform full reconciliation). |
Object Type |
Type of object you want to reconcile Default value: Note: Do not modify the value of this attribute. |
Resource Object Name |
Name of the resource object that is used for reconciliation Default value: |
Scheduled Job Name |
Name of the scheduled job Default value: Note: For the scheduled job shipped with this connector, you must not change the value of this attribute. However, if you create a copy of the job, then you can enter the unique name for that scheduled job as the value of this attribute. |
To configure a scheduled job:
If you are using Oracle Identity Manager release 11.1.1, then:
Log in to the Administrative and User Console.
On the Welcome to Oracle Identity Manager Self Service page, click Advanced in the upper-right corner of the page.
If you are using Oracle Identity Manager release 11.1.2.x, then:
Log in to Oracle Identity System Administration.
Create and activate a sandbox. For detailed instructions on creating and activating a sandbox, see Managing Sandboxes in Oracle Fusion Middleware Developing and Customizing Applications for Oracle Identity Manager.
In the left pane, under System Management, click Scheduler.
Search for and open the scheduled job as follows:
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.
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.
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 Creating Jobs in Oracle Fusion Middleware Administering Oracle Identity Manager for detailed information about schedule types.
In addition to modifying the job details, you can enable or disable a job.
On the Job Details tab, in the Parameters region, specify values for the attributes of the scheduled job.
Note:
Attribute values are predefined in the connector XML file that you import. Specify values only for those attributes that you want to change.
Attributes of the scheduled job are discussed in Scheduled Job for Reconciliation.
After specifying the attributes, 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 target system account for the user.
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 Switching Between Request-Based Provisioning and Direct Provisioning.
The following are types of provisioning operations:
Direct provisioning
Request-based provisioning
Provisioning triggered by policy changes
This section discusses the following topics:
The following are guidelines that you must apply while performing provisioning operations:
Before you perform provisioning operations, lookup definitions must be synchronized with the lookup fields of the target system. In other words, run the scheduled jobs for lookup field synchronization before provisioning operations.
The Reports To field on the process form expects values in the FirstName LastName format.
Passwords for user accounts provisioned from Oracle Identity Manager must adhere to the password policy set in the target system.
The character length of target system fields must be taken into account when specifying values for the corresponding Oracle Identity Manager fields.
The connector uses the SetPasswordAPI method for provisioning user passwords. On Oracle CRM On Demand target system, suppose users A and B have the ability to set passwords. Then, user A does not have the ability to update the password of user B.
When you install the connector on Oracle Identity Manager, the direct provisioning feature is automatically enabled. This means that the process form is enabled when you install the connector.
In direct provisioning, the Oracle Identity Manager administrator uses the Administrative and User Console to create a target system account for a user.
To provision a resource by using the direct provisioning approach:
In request-based provisioning, an end user creates a request for a resource by using the Administrative and User Console. Administrators or other users can also create requests for a particular user. Requests for a particular resource on the resource can be viewed and approved by approvers designated in Oracle Identity Manager.
The following are features of request-based provisioning:
A user can be provisioned only one resource (account) on the target system.
Note:
Direct provisioning allows the provisioning of multiple target system accounts on the target system.
Direct provisioning cannot be used if you enable request-based provisioning.
The following sections discuss the steps to be performed to enable request-based provisioning:
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.
The following steps are performed by the end user in a request-based provisioning operation:
The following are steps performed by the approver in a request-based provisioning operation:
The following are steps that the approver can perform:
See Also:
Importing Using the Deployment Manager and Sandbox in Oracle Fusion Middleware Administering Oracle Identity Manager for detailed information about importing objects from an XML file using the Deployment Manager
A request dataset is an XML file that specifies the information to be submitted by the requester during a provisioning operation. These request datasets specify information about the default set of attributes for which the requester must submit information during a request-based provisioning operation.
To import a request dataset XML file by using the Deployment Manager:
To enable the Auto Save Form feature:
Run the PurgeCache utility to clear content belonging to the Metadata category from the server cache. See Clearing Content Related to Connector Resource Bundles from the Server Cache for instructions.
The procedure to configure request-based provisioning ends with this step.
If you have configured the connector for request-based provisioning, you can always switch to direct provisioning. Similarly, you can always switch back to request-based provisioning any time.
Note:
It is assumed that you have performed the procedure described in Configuring Request-Based Provisioning.
This section discusses the following topics:
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 CRM On Demand 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 CRM On Demand resource object.
Deselect the Self Request Allowed check box.
Click the save icon.
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 CRM On Demand 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 CRM On Demand resource object.
Select the Self Request Allowed check box.
Click the save icon.
To configure provisioning operations in Oracle Identity Manager release 11.1.2.x:
Note:
The time required to complete a provisioning operation that you perform the first time by using this connector takes longer than usual.
Log in to Oracle Identity Administrative and User console.
Create a user. See Creating a User in Oracle Fusion Middleware Performing Self Service Tasks with Oracle Identity Manager for more information about creating a user.
On the Account tab, click Request Accounts.
In the Catalog page, search for and add to cart the application instance, and then click Checkout.
See Configuring Oracle Identity Manager 11.1.2 or Later for related procedures.
Specify values for fields in the application form and then click Ready to Submit.
Click Submit.
If you want to provision a CRM On Demand User, then:
On the Users page, search for the required user.
On the user details page, click Accounts.
Click the Request Accounts button.
Search for the CRM On Demand application instance in the catalog search box and select it.
Click Add to Cart.
Click Checkout.
Specify values for fields in the application form and then click Ready to Submit.
Click Submit.