Skip Headers
Oracle® Identity Manager Connector Guide for JD Edwards EnterpriseOne User Management
Release 9.0.4

E10453-09
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

This chapter is divided into the following sections:

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 Scheduled Tasks" for information about running scheduled tasks.

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

    See Section 3.3.2, "User 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, depending on the mode in which you configure the connector, the TimeStamp parameter of the JDE IT Resource IT resource is automatically set to the time stamp at which the reconciliation run began.

See Also:

Section 2.4.2, "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

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.0.1 through 9.0.3.2 and 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.

The JDE LookUp Recon 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 JDE LookUp Recon Scheduled Task

Attribute Description

Language

Enter the code of the language to be used in the lookup reconciliation.

Default value: en

Country

Enter the code of the country to be used in the lookup reconciliation.

Default value: us

ITResource

Enter the name of the IT resource for setting up a connection to JD Edwards.

Default value: JDE IT Resource

isRoleLookup

Enter true if you want to synchronize the Lookup.JDE.Roles lookup definition in Oracle Identity Manager with the target system.

Enter false if you do not want to synchronize the Lookup.JDE.Roles lookup definition in Oracle Identity Manager with the target system.

Default Value: true

isDateSeparationCharacterLookup

Enter true if you want to synchronize the Lookup.JDE.DateSeparationCharacter lookup definition in Oracle Identity Manager with the target system.

Enter false if you do not want to synchronize the Lookup.JDE.DateSeparationCharacter lookup definition in Oracle Identity Manager with the target system.

Default Value: true

isLanguageLookup

Enter true if you want to synchronize the Lookup.JDE.Language lookup definition in Oracle Identity Manager with the target system.

Enter false if you do not want to synchronize the Lookup.JDE.Language lookup definition in Oracle Identity Manager with the target system.

Default Value: true

isLocalizationCountryCodeLookup

Enter true if you want to synchronize the Lookup.JDE.LocalizationCountryCode lookup definition in Oracle Identity Manager with the target system.

Enter false if you do not want to synchronize the Lookup.JDE.LocalizationCountryCode lookup definition in Oracle Identity Manager with the target system.

Default Value: true

isDateFormatLookup

Enter true if you want to synchronize the Lookup.JDE.DateFormat lookup definition in Oracle Identity Manager with the target system.

Enter false if you do not want to synchronize the Lookup.JDE.DateFormat lookup definition in Oracle Identity Manager with the target system.

Default Value: true

isUniversalTimeLookup

Enter true if you want to synchronize the Lookup.JDE.UniversalTime lookup definition in Oracle Identity Manager with the target system.

Enter false if you do not want to synchronize the Lookup.JDE.UniversalTime lookup definition in Oracle Identity Manager with the target system.

Default Value: true

isDecimalFormatCharacterLookup

Enter true if you want to synchronize the Lookup.JDE.DecimalFormatCharacter lookup definition in Oracle Identity Manager with the target system.

Enter false if you do not want to synchronize the Lookup.JDE.DecimalFormatCharacter lookup definition in Oracle Identity Manager with the target system.

Default Value: true

isTimeFormatLookup

Enter true if you want to synchronize the Lookup.JDE.TimeFormat lookup definition in Oracle Identity Manager with the target system.

Enter false if you do not want to synchronize the Lookup.JDE.TimeFormat lookup definition in Oracle Identity Manager with the target system.

Default Value: true

LanguagePreferenceForLookup

Enter the language setting for the lookup field entries. Depending on the language that you want to set, the value can be one of the following:

  • For English: E

  • For French: F

  • For German: G

  • For Italian: I

  • For Japanese: J

  • For Korean: KO

  • For Simplified Chinese: CS

  • For Spanish: S

  • For Traditional Chinese: CT

Default Value: E


3.3 Configuring Reconciliation

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, set the TimeStamp parameter of the JDE IT Resource IT resource to 0. At the end of the reconciliation run, this parameter 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 User Reconciliation Scheduled Task

When you run the Connector Installer or import the connector XML file, the JDE User Recon scheduled task is automatically created in Oracle Identity Manager. This scheduled task is used to reconcile user data from the target system.

You must specify values for the following attributes of the JDE User Recon user reconciliation scheduled task. Table 3-2 describes the attributes of this 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.

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

Attribute Description

Organization

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

Default value: Xellerate Users

Xellerate Type

Enter the role that must be set for OIM Users created through reconciliation. You can enter one of the following values:

  • End-User

  • End-User Administrator

Default value: End-User Administrator

Role

Enter the employee type that must be set for OIM Users created through reconciliation. You can enter one of the following values:

  • Full-Time Employee

  • Part-Time Employee

  • Temp

  • Intern

  • Consultant

Default value: Consultant

ITResource

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

Default value: JDE IT Resource

ResourceObject

Enter the name of the resource object that is used in reconciliation.

Default value: JDE Resource Object

isTrustedSource

Enter true if you want to configure the connector for trusted source reconciliation.

Enter false if you want to configure the connector for target resource reconciliation.

Default value: false

XLDeleteUsersAllowed

Enter true if you want to allow users to be deleted in Oracle Identity Manager during user reconciliation.

Enter false if you do not want to allow users to be deleted in Oracle Identity Manager during user reconciliation.

Default value: false

Configuration Lookup

This attribute contains the name of the lookup definition that stores configuration information used during connector operations.

Default value: Lookup.JDE.Configuration

Note: You must not change the value of this attribute.


3.4 Configuring Scheduled Tasks

This section describes the procedure to configure 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 you must configure.

Table 3-3 Scheduled Tasks for Lookup Field Synchronization and Reconciliation

Scheduled Task Description

JDE LookUp Recon

This scheduled task is used for lookup field synchronization. See Section 3.2, "Scheduled Task for Lookup Field Synchronization" for information about this scheduled task.

JDE User Recon

This scheduled task is used for user reconciliation. See Section 3.3.2, "User 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:

3.4.1 Configuring Scheduled Tasks on Oracle Identity Manager Release 9.0.1 through 9.0.3.2 or Release 9.1.0.x

To configure a scheduled task:

  1. Open the Oracle Identity Manager Design Console.

  2. Expand the Xellerate Administration folder, and then select Task Scheduler.

  3. Click Find. The details of the predefined scheduled tasks are displayed on two different tabs.

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

  5. Ensure that the Disabled and Stop Execution check boxes are not selected.

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

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

  8. Provide values for the attributes of the scheduled task.

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

  10. Repeat Steps 4 through 9 to create the second scheduled task.

Stopping Reconciliation

Suppose the user reconciliation scheduled task for the connector is running and user records are being reconciled. If you want to stop the reconciliation process:

  1. Perform Steps 1 through 3 of the procedure to configure reconciliation scheduled tasks.

  2. Select the Stop Execution check box in the task scheduler.

  3. Click Save.

3.4.2 Configuring Scheduled Tasks on Oracle Identity Manager Release 11.1.1

To configure a scheduled task:

  1. Log in to the Administrative and User Console.

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

    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. 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. On the Job Details tab, in the Parameters region, specify values for the attributes of the 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.

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

    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.0.1 through 9.0.3.2 or 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.0.1 through 9.0.3.2 or 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.0.1 through 9.0.3.2 or 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 JDE Resource Object 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 JDE User Details 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 User Role page, search for and select a role for the user on the target system 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.0.1 through 9.0.3.2 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:

      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 JDE Resource Object, 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 JDE Process 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 JDE Resource Object 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 JDE Process 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 JDE Resource Object resource object.

    3. Select the Self Request Allowed check box.

    4. Click the Save icon.