| Oracle® Identity Manager Connector Guide for JD Edwards EnterpriseOne Release 9.0.4 Part Number E10182-01 |
|
|
View PDF |
| Oracle® Identity Manager Connector Guide for JD Edwards EnterpriseOne Release 9.0.4 Part Number E10182-01 |
|
|
View PDF |
Deploying the connector involves the following steps:
The following table lists the deployment requirements for the connector.
| Item | Requirement |
|---|---|
| Oracle Identity Manager | Oracle Identity Manager release 8.5.3 or later |
| Target system | JD Edwards EnterpriseOne Tools release 8.9 |
| Target system user account | JD Edwards EnterpriseOne user account to which the SYSADMIN and PKGBLD rights have been assigned.
You provide the credentials of this user account while performing the procedure in the "Defining IT Resources" section. If this user account were not assigned the required rights, then a connection error would be thrown when Oracle Identity Manager tries to communicate with the target system. |
The connector files to be copied and the directories to which you must copy them are given in the following table.
Note:
The directory paths given in the first column of this table correspond to the location of the connector files at the following location on the installation media:Enterprise Applications/JDEdwards/JDE
Refer to the "Files and Directories That Comprise the Connector" section for more information about these files.
The target system files to be copied and the directories to which you must copy them are given in the following table.
| File on the Target System Server | Destination Directory |
|---|---|
The following JAR files from the JDE_installation_dir/E812/DDP/system/classes directory on the JD Edwards EnterpriseOne server:
|
OIM_home/Xellerate/JavaTasks
|
Extract the following template files from the JDE_installation_dir/E812/DDP/system/classes/ConnectorSamples.zip file:
Rename Then, copy all three files to the specified destination directory. |
OIM_home/Xellerate/JDE/Properties
|
If the EnterpriseOne server is running on Oracle Database, then copy the tnsnames.ora file to the specified destination directory. |
OIM_home/Xellerate/JDE/Properties
|
Note:
While installing Oracle Identity Manager in a clustered environment, you copy the contents of the installation directory to each node of the cluster. Similarly, you must copy the JAR files listed in this table to the corresponding directories on each node of the cluster.You must modify the following property files to suit your deployment requirements:
Note:
The lists of configuration properties included in the following subsections are not comprehensive and include only those properties that are essential for the functioning of the connector. The files allow further customization of the connector functionality with other optional properties. Explicit descriptions and instructions to use the other configuration properties are included in the configuration files.You need to modify the jdbj.ini file based on you requirements. This file contains configuration information for JDBj, which provides general database access capabilities for JD Edwards EnterpriseOne.
Note:
All property values in this file are case-sensitive.In the [JDBj-BOOTSTRAP SESSION] section of this file, specify values for the parameters described in the following table:
| Property | Sample Value | Description |
|---|---|---|
user |
user=JDE |
User ID to connect to the target system
This is an optional parameter. |
password |
password=jDPass |
Password of the user
This is an optional parameter. |
environment |
environment=PY812 |
Environment in which the user connects to the JD Edwards EnterpriseOne server
The is a required parameter and must be specified in the JD Edwards EnterpriseOne provides the following environments in which a user can access the system:
To access the system in a particular environment, the user needs privileges for that environment. |
role |
role=*ALL |
Role of the connecting user
This is an optional parameter. |
In the [JDBj-BOOTSTRAP DATA SOURCE] section of this file, specify values for the properties specified in the following table.
| Property | Description |
|---|---|
name |
Name of the data source
This property is not important for bootstrap connections. However, it shows up in error messages and logs. Sample value: |
databaseType |
Type of database used by the target system
This value depends on the database used by the system. It can be any of the following:
Sample value: |
server |
Name of the EnterpriseOne host server.
Applicable for IBM AS/400 and SQL Server. Sample value: |
serverPort |
EnterpriseOne host server port number.
Applicable only for Microsoft SQL Server |
database |
Database instance name
Applicable only for Oracle Database and IBM DB2 UDB Sample value: |
physicalDatabase |
The physical database (used as library qualifier for IBM AS/400).
This is applicable for Microsoft SQL Server and IBM AS/400 |
owner |
Owner of the data source
This is applicable for Oracle Database, Microsoft SQL Server, and IBM DB2 UDB. Sample value: |
lob |
Boolean value that indicates support for LOBs.
This is applicable for Oracle Database and IBM AS/400. Sample value: |
unicode |
Boolean value that indicates support for Unicode conversion is supported.
This is applicable for Microsoft SQL Server. Sample value: |
Note:
A client of the EnterpriseOne server, also known as the Fat Client, has settings that correspond with the settings in the
[JDBj-BOOTSTRAP DATA SOURCE] section in the jdbj.ini file. The values in this file must match those specified on the Fat Client. On the Fat Client, these settings are in the [DB SYSTEM SETTINGS] section of the jde.ini file.In the [JDBj-JDBC DRIVERS] section of this file, specify the JDBC driver to connect to EnterpriseOne server. To do this, uncomment the line that specifies the driver for the database you are using. For example, if you are using Oracle Database, uncomment the line that specifies the driver for Oracle Database.
ORACLE=oracle.jdbc.driver.OracleDriver
In the [JDBj-ORACLE] section of this file, specify the location of the tnsnames.ora that you copy from the EnterpriseOne server. The following setting is required only when you use Oracle Database:
tns=OIM_home/Xellerate/JDE/Properties/tnsnames.ora
The jdeinterop.ini file is a configuration file that is used by the JD Edwards connector to enable interoperability between the Oracle Identity Manager and JD Edwards system.Modify the jdeinterop.ini file and specify values for the properties described in the following table:
| Section in the File | Property/Sample Value | Description |
|---|---|---|
[OCM] |
OCMEnabled=false |
Boolean value that specifies whether the connector uses Object Configuration Mapping (OCM) to find the EnterpriseOne server |
[JDENET] |
serviceNameConnect=6014 |
Port number to connect to EnterpriseOne server from Oracle Identity Manager |
[SERVER] |
glossaryTextServer=ibm1:6014 |
Name and port number to connect to glossary Text server |
codePage=1252 |
Code page number for a particular language | |
[SECURITY] |
SecurityServer=ibm1 |
Name of the security server
Note: The security server is the same as the EnterpriseOne server. |
[INTEROP] |
enterpriseServer=ibm1 |
Name of the EnterpriseOne server |
port=6014 |
Port number to connect to EnterpriseOne server |
You can customize this file to enable logging at different levels. To enable logging, you need to specify the properties described in the following table:
| Property | Description | Sample Value |
|---|---|---|
FILE |
Location of the log file | FILE=//jderoot.log |
LEVEL |
Logging level
You can specify any of the following values:
These values are in decreasing order of priority. |
LEVEL=WARN |
FORMAT |
Logging format
This property can be set to:
In a production environment, this must be set to |
FORMAT=APPS |
MAXFILESIZE |
Maximum size of the log file in MB | MAXFILESIZE=10MB |
MAXBACKUPINDEX |
Maximum number of log file backups to be maintained | MAXBACKUPINDEX=20 |
COMPONENTS |
Components for which events are logged in the log file
You can specify other components as well. A list of all the components is specified in the template for this file. |
COMPONENT=RUNTIME|JAS|JDBJ |
APPEND |
Boolean value that specifies that log entries must be appended at the end of the file
The value can be |
APPEND=TRUE |
Note:
In this guide, the term Oracle Identity Manager server refers to the computer on which Oracle Identity Manager is installed.Configuring the Oracle Identity Manager server involves performing the following procedures:
Changing to the required input locale (language and country setting) involves installing the required fonts and setting the required input locale.
You may require the assistance of the system administrator to change to the required input locale.
While performing the instructions described in the "Step 2: Copying the Connector Files and External Code Files" section, you copy files from the resources directory on the installation media into the OIM_home/xellerate/connectorResources directory. Whenever you add a new resource bundle in the connectorResources directory or make a change in an existing resource bundle, you must clear content related to connector resource bundles from the server cache.
To clear content related to connector resource bundles from the server cache:
In a command window, change to the OIM_home/xellerate/bin directory.
Note:
You must perform Step 1 before you perform Step 2. If you run the command described in Step 2 as follows, then an exception is thrown:OIM_home/xellerate/bin/batch_file_name
Enter one of the following commands:
On Microsoft Windows:
PurgeCache.bat ConnectorResourceBundle
On UNIX:
PurgeCache.sh ConnectorResourceBundle
Note:
You can ignore the exception that is thrown when you perform Step 2.In this command, ConnectorResourceBundle is one of the content categories that you can remove from the server cache. Refer to the following file for information about the other content categories:
OIM_home/xellerate/config/xlConfig.xml
When you enable logging, Oracle Identity Manager automatically stores in a log file information about events that occur during the course of provisioning and reconciliation operations. To specify the type of event for which you want logging to take place, you can set the log level to one of the following:
ALL
This level enables logging for all events.
DEBUG
This level enables logging of information about fine-grained events that are useful for debugging.
INFO
This level enables logging of informational messages that highlight the progress of the application at coarse-grained level.
WARN
This level enables logging of information about potentially harmful situations.
ERROR
This level enables logging of information about error events that may still allow the application to continue running.
FATAL
This level enables logging of information about very severe error events that could cause the application to stop functioning.
OFF
This level disables logging for all events.
The file in which you set the log level and the log file path depend on the application server that you use:
BEA WebLogic
To enable logging:
Add the following lines in the OIM_home/xellerate/config/log.properties file:
log4j.logger.XELLERATE=log_level log4j.logger.XL_INTG.JDECONNECTOR=log_level
In these lines, replace log_level with the log level that you want to set.
For example:
log4j.logger.XELLERATE=INFO log4j.logger.XL_INTG.JDECONNECTOR=INFO
After you enable logging, the log information is written to the following file:
WebLogic_home/user_projects/domains/domain_name/server_name/server_name.log
IBM WebSphere
To enable logging:
Add the following lines in the OIM_home/xellerate/config/log.properties file:
log4j.logger.XELLERATE=log_level log4j.logger.XL_INTG.JDECONNECTOR=log_level
In these lines, replace log_level with the log level that you want to set.
For example:
log4j.logger.XELLERATE=INFO log4j.logger.XL_INTG.JDECONNECTOR=INFO
After you enable logging, the log information is written to the following file:
WebSphere_home/AppServer/logs/server_name/startServer.log
JBoss Application Server
To enable logging:
In the JBoss_home/server/default/conf/log4j.xml file, locate or add the following lines:
<category name="XELLERATE">
<priority value="log_level"/>
</category>
<category name="XL_INTG.JDECONNECTOR">
<priority value="log_level"/>
</category>
In the second XML code line of each set, replace log_level with the log level that you want to set. For example:
<category name="XELLERATE"> <priority value="INFO"/> </category>
<category name="XL_INTG.JDECONNECTOR"> <priority value="INFO"/> </category>
After you enable logging, the log information is written to the following file:
JBoss_home/server/default/log/server.log
OC4J
To enable logging:
Add the following lines in the OIM_home/xellerate/config/log.properties file:
log4j.logger.XELLERATE=log_level log4j.logger.XL_INTG.JDECONNECTOR=log_level
In these lines, replace log_level with the log level that you want to set.
For example:
log4j.logger.XELLERATE=INFO log4j.logger.XL_INTG.JDECONNECTOR=INFO
After you enable logging, the log information is written to the following file:
OC4J_home/opmn/logs/default_group~home~default_group~1.log
As mentioned in the "Files and Directories That Comprise the Connector" section, the connector XML file contains definitions of the components of the connector. By importing the connector XML file, you create these components in Oracle Identity Manager.
To import the connector XML file into Oracle Identity Manager:
Open the Oracle Identity Manager Administrative and User Console.
Click the Deployment Management link on the left navigation bar.
Click the Import link under Deployment Management. A dialog box for locating files is displayed.
Locate and open the JDEResourceObject.xml file, which is in the OIM_home/Xellerate/JDE/xml directory. Details of this XML file are shown on the File Preview page.
Click Add File. The Substitutions page is displayed.
Click Next. The Confirmation page is displayed.
Click Next. The Provide IT Resource Instance Data page for the JDE IT Resource IT resource is displayed.
Specify values for the parameters of the JDE IT Resource IT resource. Refer to the table in the "Defining IT Resources" section for information about the values to be specified.
Click Next. The Provide IT Resource Instance Data page for a new instance of the JDE IT Resource type is displayed.
Click Skip to specify that you do not want to define another IT resource. The Confirmation page is displayed.
Click View Selections.
The contents of the XML file are displayed on the Import page. You may see a cross-shaped icon along with some nodes. These nodes represent Oracle Identity Manager entities that are redundant. Before you import the connector XML file, you must remove these entities by right-clicking each node and then selecting Remove.
Click Import. The connector XML file is imported into Oracle Identity Manager.
After you import the connector XML files, proceed to the next chapter.
You must specify values for the JDE IT Resource IT resource parameters listed in the following table:
| Parameter | Description |
|---|---|
User |
User ID of the user connecting to EnterpriseOne server |
Password |
Password of the user connecting to EnterpriseOne Server |
Environment |
Environment of the connecting user
Sample value: |
Role |
Role of the user connecting to EnterpriseOne Server
Sample value: |
ProxyUser |
User ID of the system user in EnterpriseOne server |
ProxyUserPassword |
Password of the system user in EnterpriseOne server |
TimeStamp |
Timestamp for the first reconciliation run, the timestamp value is not set. For subsequent rounds of reconciliation, the time at which the previous round of reconciliation was completed is stored in this parameter.
The following is sample timestamp value:
|
After you specify values for these IT resource parameters, proceed to Step 9 of the procedure to import connector XML files.
