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. The JD Edwards EnterpriseOne Connector is used to integrate Oracle Identity Manager with JD Edwards EnterpriseOne.

Note:

Oracle Identity Manager Connectors were referred to as resource adapters prior to the acquisition of Thor Technologies by Oracle.

This chapter contains the following sections:

• Supported Functionality

• Multilanguage Support

• Reconciliation Module

• Provisioning Module

• Files and Directories That Comprise the Connector

• Determining the Release Number of the Connector

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	Provisioning	Lists the roles of a user in the JD Edwards system
List All Roles	Provisioning	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

Multilanguage Support

This release of the connector supports the following languages:

• English

• French

• German

• Italian

• Japanese

• Korean

• Simplified Chinese

• Spanish

• Traditional Chinese

See Also:

Oracle Identity Manager Globalization Guide for information about supported special characters

Reconciliation Module

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, Xellerate type, and Role.

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

  • Event Linked (for successful reconciliation)

  • No Match Found (for failed reconciliation)

The reconciliation module reconciles the fields listed in the following sections:

• Lookup Fields Reconciliation

• User Reconciliation

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

User Reconciliation

User reconciliation can be divided into the following:

• Reconciled JD Edwards EnterpriseOne Object Fields

• Reconciled Xellerate User Fields

Reconciled JD Edwards EnterpriseOne Object Fields

The following fields are reconciled:

• User ID

• Password

• Language

• Date Format

• Date Separation Character

• Localization Country Code

• Universal Time

• Time Format

• IT Resource Type

• Decimal Format Character

• Fast Path Create

• Disable User

• Roles

Reconciled Xellerate User Fields

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

• User ID

• Password

• First Name

• Last Name

• Organization

• Xellerate Type

• Role

Provisioning Module

The following fields must be specified for a provisioning task to work for JD Edwards resource objects:

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

Files and Directories That Comprise the Connector

The files and directories that comprise this connector are located in the following directory on the installation media:

Enterprise Applications\JDEdwards\JDE

These files and directories are listed in the following table.

File in the Installation Media Directory	Description
xml\JDEResourceObject.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\JDEXLResourceObject.xml	This XML file contains the configuration for the Xellerate User. You must import this file only if you plan to use the connector in trusted source reconciliation mode.
lib\JDEConnector.jar	This is the connector code JAR file. This file contains all the classes and definitions required for provisioning and reconciliation.
Files in the resources directory	This directory contains files for locale-specific information that is used by the connector. Note: In this release, the JD Edwards connector supports only the English language.
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.

Note:

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

The "Step 2: Copying the Connector Files and External Code" section provides instructions to copy these files into the required directories.

Determining the Release Number of the Connector

To determine the release number of the connector that you have deployed:

1. Extract the contents of the JDEConnector.jar file. For a connector that has been deployed, this file is in the following directory:

   OIM_home\xellerate\JavaTasks
   
   

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

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

See Also:

Oracle Identity Manager Design Console Guide