1. Configuring the Oracle E-Business HRMS Application
  2. Using the Oracle E-Business Suite HRMS Connectors

6 Using the Oracle E-Business Suite HRMS Connectors

You can use the Oracle E-Business Suits HRMS Connectors for performing reconciliation and provisioning operations after configuring your application to meet your requirements.

This chapter contains the following sections:

Note:

Perform sections Configuring Reconciliation Jobs and Performing Provisioning Operations if you are using the EBS HRMS connector only.

6.1 Configuring Reconciliation

You can configure the connector to specify the type of reconciliation and its schedule.

6.1.1 Performing Full and Incremental Reconciliation

Full reconciliation involves reconciling all existing user records from the target system into Oracle Identity Governance. During incremental reconciliation, only records that are added or modified after the last reconciliation run are fetched into Oracle Identity Governance.

After you create the application, 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 Governance.

To perform a full reconciliation, remove (delete) any value assigned to the Latest Token and Filter parameters and run one of the following reconciliation jobs:
  • For an Oracle EBS HRMS application: Oracle EBS HRMS Target User Reconciliation
  • For an Oracle EBS Employee Reconciliation application: Oracle EBS HRMS Trusted User Reconciliation
To perform an incremental reconciliation run for the first time, remove (delete) any value assigned to the Sync Token parameter and run of the following reconciliation jobs:
  • For an Oracle EBS HRMS application: Oracle EBS HRMS Target Incremental User Reconciliation
  • For an Oracle EBS Employee Reconciliation application: Oracle EBS HRMS Trusted Incremental User Reconciliation
This ensures that the connector fetches data about all records from the target system into Oracle Identity Governance. From the next run onward, only records created or modified after the value in the Sync Token attribute are considered for reconciliation.

See Reconciliation Jobs for the EBS HRMS Connector and Reconciliation Jobs for the EBS ER Connector for information about the jobs for full and incremental reconciliation.

6.1.2 Performing Limited Reconciliation

You can perform limited reconciliation by creating filters for the reconciliation module, and reconcile records from the target system based on a specified filter criterion.

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 can perform limited reconciliation by creating filters for the reconciliation module. This connector provides a Filter parameter (a reconciliation job parameter) that allows you to use any of the Oracle EBS HRMS User resource attributes to filter the target system records.

When you specify a value for the Filter parameter, the connector reconciles only the target system records that match the filter criterion into Oracle Identity Governance. If you do not specify a value for the Filter parameter, then the connector reconciles all the records in the target system into Oracle Identity Governance.

You specify a value for the Filter attribute while configuring the user reconciliation scheduled job.

The following is an example of a filter for a search where you want to filter only those accounts whose first name is "John":

equalTo('FIRST_NAME','JOHN')

For detailed information about ICF Filters, see ICF Filter Syntax in Oracle Fusion Middleware Developing and Customizing Applications for Oracle Identity Governance.

6.1.3 Performing Batched Reconciliation

You can perform batched reconciliation to reconcile a specific number of records from the target system into Oracle Identity Governance.

During a reconciliation run, all changes in the target system records are reconciled into Oracle Identity Governance. 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 a value for the Batch Size parameter of the Basic Configuration section. Use this parameter to specify the number of records that the connector must include in each batch. By default, this value is set to 1000.

When you specify All as the value of this parameter, the connector fetches all the records into Oracle Identity Governance. 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 Batch Size value as 200. Now 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.

6.2 Configuring Reconciliation Jobs

Configure reconciliation jobs to perform reconciliation runs that check for new information on your target system periodically and replicates the data in Oracle Identity Governance.

You can apply this procedure to configure the reconciliation jobs for users and entitlements.

To configure a reconciliation job:
  1. Log in to Identity System Administration.
  2. In the left pane, under System Management, click Scheduler.
  3. Search for and open the scheduled job as follows:
    1. 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.
    2. In the search results table on the left pane, click the scheduled job in the Job Name column.
  4. On the Job Details tab, you can modify the parameters of the scheduled task:
    • 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. See Creating Jobs in Oracle Fusion Middleware Administering Oracle Identity Governance.

    In addition to modifying the job details, you can enable or disable a job.

  5. On the Job Details tab, in the Parameters region, specify values for the attributes of the scheduled task.

    Note:

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

  6. Click Apply to save the changes.

    Note:

    You can use the Scheduler Status page in Identity System Administration to either start, stop, or reinitialize the scheduler.

6.3 Performing Provisioning Operations

You create a new user in Identity Self Service by using the Create User page. You provision or request for accounts on the Accounts tab of the User Details page.

To perform provisioning operations in Oracle Identity Governance:

  1. Log in to Identity Self Service.
  2. Create a user as follows:
    1. In Identity Self Service, click Manage. The Home tab displays the different Manage option. Click Users. The Manage Users page is displayed.
    2. From the Actions menu, select Create. Alternatively, you can click Create on the toolbar. The Create User page is displayed with input fields for user profile attributes.
    3. Enter details of the user in the Create User page.
  3. On the Account tab, click Request Accounts.
  4. In the Catalog page, search for and add to cart the application instance for the connector that you configured earlier, and then click Checkout.
  5. Specify value for fields in the application form and then click Ready to Submit.
  6. Click Submit.

See Also:

Creating a User in Oracle Fusion Middleware Performing Self Service Tasks with Oracle Identity Governance for details about the fields on the Create User page

6.4 Uninstalling the Connector

Uninstalling the connector deletes all the account-related data associated with its resource objects.

If you want to uninstall the connector for any reason, then run the Uninstall Connector utility. Before you run this utility, ensure that you set values for ObjectType and ObjectValues properties in the ConnectorUninstall.properties file. For example, if you want to delete resource objects, scheduled tasks, and scheduled jobs associated with the connector, then enter "ResourceObject", "ScheduleTask", "ScheduleJob" as the value of the ObjectType property and a semicolon-separated list of object values corresponding to your connector (for example, GoogleApps User; GoogleApps Group) as the value of the ObjectValues property.

Note:

If you set values for the ConnectorName and Release properties along with the ObjectTypeand ObjectValue properties, then the deletion of objects listed in the ObjectValues property is performed by the utility and the Connector information is skipped.

For more information, see Uninstalling Connectors in Oracle Fusion Middleware Administering Oracle Identity Governance.