1 About the Connector

Oracle Identity Manager automates access rights management, security, and Provisioning of IT resources. Oracle Identity Manager connectors are used to integrate Oracle Identity Manager with third-party applications. This guide discusses the procedure to deploy the connector that is used to integrate Oracle Identity Manager with JD Edwards EnterpriseOne.

This chapter contains the following sections:

• Reconciliation Module

• Provisioning Module

• Supported Functionality

• Multilanguage Support

• Files and Directories on the Installation Media

• Determining the Release Number of the Connector

Note:

In this guide, the term Oracle Identity Manager server refers to the computer on which Oracle Identity Manager is installed.

At some places in this guide, JD Edwards EnterpriseOne has been referred to as the target system.

1.1 Reconciliation Module

Reconciliation involves duplicating in Oracle Identity Manager the creation of and modifications to user accounts on the target system. It is an automated process initiated by a scheduled task that you configure.

See Also:

The "Deployment Configurations of Oracle Identity Manager" section in Oracle Identity Manager Connector Concepts Guide for conceptual information about reconciliation configurations

This section discusses the elements that the reconciliation module extracts from the target system to construct reconciliation event records. The following are features of these records:

• The default data elements of each reconciliation event record are Organization, User Type, and Employee Type.

• The default labels for the data elements in each reconciliation event record are:

  • Event Linked (for successful reconciliation)

  • No Match Found (for failed reconciliation)

Based on the type of data reconciled from the target system, reconciliation can be divided into the following types:

• Lookup Fields Reconciliation

• User Reconciliation

1.1.1 Lookup Fields Reconciliation

For user reconciliation to work, the following lookup definitions must be available and the lookup values must be reconciled:

• Lookup.JDE.DateSeparationCharacter

• Lookup.JDE.Language

• Lookup.JDE.Roles

• Lookup.JDE.LocalizationCountryCode

• Lookup.JDE.DateFormat

• Lookup.JDE.FastPathCreate

• Lookup.JDE.UniversalTime

• Lookup.JDE.TimeFormat

• Lookup.JDE.DecimalFormatCharector

1.1.2 User Reconciliation

User reconciliation can be divided into the following:

• Reconciled Target System Fields

• Reconciled Xellerate User (OIM User) Fields

1.1.2.1 Reconciled Target System Fields

The following target system fields are reconciled:

• User ID

• Language

• Date Format

• Date Separation Character

• Localization Country Code

• Universal Time

• Time Format

• Decimal Format Character

• Fast Path Create

• Disable User

• Roles

1.1.2.2 Reconciled Xellerate User (OIM User) Fields

If trusted source reconciliation is implemented, then the following additional fields are reconciled:

• User ID

• First Name

• Last Name

• Organization

• User Type

• Employee Type

1.2 Provisioning Module

Provisioning involves creating or modifying a user's account on the target system through Oracle Identity Manager. You use the Oracle Identity Manager Administrative and User Console to perform provisioning operations.

See Also:

The "Deployment Configurations of Oracle Identity Manager" section in Oracle Identity Manager Connector Concepts Guide for conceptual information about provisioning

For this target system, the following fields are provisioned:

• User ID

• Password

Note:

If you create a user in Oracle Identity Manager and do not assign a role to the user, then the user would not be able to log in to the JD Edwards system.

1.3 Supported Functionality

The following table lists the functions that are available with this connector.

Function	Type	Description
Create User	Provisioning	Creates a user in the JD Edwards system
Update User	Provisioning	Updates a user in the JD Edwards system
Reset Password	Provisioning	Updates the user password in the JD Edwards system
Enable User	Provisioning	Enables a user in the JD Edwards system
Disable User	Provisioning	Disables a user in the JD Edwards system
Delete User	Provisioning	Deletes a user from the JD Edwards system
Add User Role	Provisioning	Adds a role to a user in the JD Edwards system
Remove User Role	Provisioning	Removes the Role from a user in the JD Edwards system
List Roles of User	Reconciliation	Lists the roles of a user in the JD Edwards system
List All Roles	Reconciliation	Lists all the roles present in the JD Edwards system
Reconciliation Insert Received	Reconciliation	Inserts information in Oracle Identity Manager about a user that is created in the JD Edwards system
Reconciliation Update Received	Reconciliation	Updates Oracle Identity Manager with information about a user that is updated in the JD Edwards system
Reconciliation Delete Received	Reconciliation	Deletes information in Oracle Identity Manager about a user that is deleted from the JD Edwards system

1.4 Multilanguage Support

This release of the connector supports the following languages:

• Arabic

• Chinese Simplified

• Chinese Traditional

• Danish

• English

• French

• German

• Italian

• Japanese

• Korean

• Portuguese (Brazilian)

• Spanish

See Also:

Oracle Identity Manager Globalization Guide for information about supported special characters

1.5 Files and Directories on the Installation Media

The files and directories on the installation media are listed and described in Table 1-1.

Table 1-1 Files and Directories On the Connector Installation Media

File in the Installation Media Directory	Description
configuration/JDEdwards-CI.xml	This XML file contains configuration information that is used during connector installation.
lib/JDEConnectorProv.jar	This JAR file contains all the classes and definitions required for provisioning. During connector deployment, this file is copied into the following directory: OIM_HOME/xellerate/JavaTasks
lib/JDEConnectorRecon.jar	This JAR file contains all the classes and definitions required for reconciliation. During connector deployment, this file is copied into the following directory: OIM_HOME/xellerate/ScheduleTask
Files in the resources directory	Each of these resource bundles contains language-specific information that is used by the connector. During connector deployment, these resource bundles are copied into the following directory: OIM_HOME/xellerate/connectorResources Note: A resource bundle is a file containing localized versions of the text strings that are displayed on the user interface of Oracle Identity Manager. These text strings include GUI element labels and messages displayed on the Administrative and User Console.
test/TroubleShootUtility.class	This utility is used to test connector functionality.
test/global.properties	This file is used to specify the parameters and settings required to connect to the target system by using the Troubleshoot utility.
test/log.properties	This file is used to specify the log level and the directory in which the log file is to be created when you run the Troubleshoot utility.
xml/JDEConnectorResourceObject.xml	This XML file contains definitions for the following components of the connector: IT resource definition JD Edwards User form Lookup definitions Adapters Resource object Process definition Reconciliation scheduled tasks
xml/JDEConnectorXLResourceObject.xml	This XML file contains the configuration for the Xellerate User (OIM User). You must import this file only if you plan to use the connector in trusted source reconciliation mode.

Note:

The files in the test directory are used only to run tests on the connector.

1.6 Determining the Release Number of the Connector

You might have a deployment of an earlier release of the connector. While deploying the latest release, you might want to know the release number of the earlier release. To determine the release number of the connector that has already been deployed:

1. In a temporary directory, extract the contents of the following JAR file:

   OIM_HOME/xellerate/JavaTasks/JDEConnectorProv.jar
   

2. Open the manifest.mf file in a text editor. The manifest.mf file is one of the files bundled inside the JDEConnectorProv.jar file.

   In the manifest.mf file, the release number of the connector is displayed as the value of the Version property.