| Oracle® Identity Manager Connector Guide for JD Edwards EnterpriseOne User Management Release 9.0.4 Part Number E10453-03 |
|
|
View PDF |
| Oracle® Identity Manager Connector Guide for JD Edwards EnterpriseOne User Management Release 9.0.4 Part Number E10453-03 |
|
|
View PDF |
Deploying the connector involves the following steps:
Depending on the release of Oracle Identity Manager that you use, perform the procedures described in one of the following sections:
The following table lists the deployment requirements for the connector.
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 contents of the
connectorResources directory and the JAR files to the corresponding directories on each node of the cluster.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/ThirdParty
|
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
|
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=Password |
Password of the user
This is an optional parameter. |
environment |
environment=PY812 |
Environment in which the user connects to the target system
The is a required parameter and must be specified in the The target system 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 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 |
After configuring the property files, you must add the directory in which the property files are present to the classpath environment variable. This variable is on the application server where Oracle Identity Manager is installed. The procedure to set the classpath depends on the application server on which Oracle Identity Manager is installed:
Setting the Classpath on BEA WebLogic Server Running on Microsoft Windows
Setting the Classpath on BEA WebLogic Server Running on Linux
Setting the Classpath on IBM WebSphere Application Server on Microsoft Windows
Setting the Classpath on JBoss Application Server Running on Microsoft Windows
Setting the Classpath on JBoss Application Server Running on Linux
To add the directory into the classpath in the WebLogic Application Server on Windows:
In the WebLogic server installation directory, navigate to the domain name directory.
Open startWebLogic.cmd in a text editor.
Edit the following command:
set CLASSPATH=%WEBLOGIC_CLASSPATH%;%POINTBASE_CLASSPATH%; %JAVA_HOME%\jre\lib\rt.jar;%WL_HOME%\server\lib\webservices.jar;%CLASSPATH%
Add the JDE_CONFIG directory into the classpath that contains the property files as shown below:
set CLASSPATH= JDE_CONFIG;%WEBLOGIC_CLASSPATH%;%POINTBASE_CLASSPATH%; %JAVA_HOME%\jre\lib\rt.jar;%WL_HOME%\server\lib\webservices.jar;%CLASSPATH%
In this command, replace JDE_CONFIG with full path and name of the JDE_CONFIG directory. This directory contains the property files jdbj.ini, jdeinterop.ini, and jdelog.properties.
To add the directory into the classpath in the WebLogic Application Server on Linux:
In the WebLogic server installation directory, navigate to the domain name directory.
Open startWebLogic.sh in a text editor.
Edit the following command:
CLASSPATH="${WEBLOGIC_CLASSPATH}:${POINTBASE_CLASSPATH}: ${JAVA_HOME}/jre/lib/rt.jar:${WL_HOME}/server/lib/webservices.jar:${CLASSPATH}"
Add the JDE_CONFIG directory into the classpath that contains the property files as shown below:
CLASSPATH=JDE_CONFIG:${WEBLOGIC_CLASSPATH}:${POINTBASE_CLASSPATH}: ${JAVA_HOME}/jre/lib/rt.jar:${WL_HOME}/server/lib/webservices.jar:${CLASSPATH}"
)
In this command, replace JDE_CONFIG with full path and name of the JDE_CONFIG directory. This directory contains the property files jdbj.ini, jdeinterop.ini, and jdelog.properties.
To add the directory into the classpath in the WebSphere Application Server on Windows:
In the WebSphere server installation directory, navigate to the bin directory.
Open startServer.bat in a text editor.
Edit the following command:
set CLASSPATH=%WAS_CLASSPATH%
Add the JDE_CONFIG directory into the classpath that contains the property files as shown below:
set CLASSPATH=JDE_CONFIG;%WAS_CLASSPATH%
In this command, replace JDE_CONFIG with full path and name of the JDE_CONFIG directory. This directory contains the property files jdbj.ini, jdeinterop.ini, and jdelog.properties.
To add the directory into the classpath in the JBoss Application Server on Windows:
In the JBoss installation directory, navigate to the bin directory.
Open run.bat in a text editor.
Edit the following command:
if "%JBOSS_CLASSPATH%" == "" ( set JBOSS_CLASSPATH=%JAVAC_JAR%;%RUNJAR% ) ELSE ( set JBOSS_CLASSPATH=%JBOSS_CLASSPATH%;%JAVAC_JAR%;%RUNJAR% )
Add the JDE_CONFIG directory into the classpath that contains the property files as shown below:
if "%JBOSS_CLASSPATH%" == "" ( set JBOSS_CLASSPATH=JDE_CONFIG;%JAVAC_JAR%;%RUNJAR% ) ELSE ( set JBOSS_CLASSPATH=JDE_CONFIG;%JBOSS_CLASSPATH%;%JAVAC_JAR%;%RUNJAR% )
In this command, replace JDE_CONFIG with full path and name of the JDE_CONFIG directory. This directory contains the property files jdbj.ini, jdeinterop.ini, and jdelog.properties.
To add the directory into the classpath in the JBoss Application Server on Linux:
In the JBoss installation directory, navigate to the bin directory.
Open run.sh in a text editor.
Edit the following command:
if [ "x$JBOSS_CLASSPATH" = "x" ]; then JBOSS_CLASSPATH="$JBOSS_BOOT_CLASSPATH:$JAVAC_JAR"ELSE JBOSS_CLASSPATH="$JBOSS_CLASSPATH:$JBOSS_BOOT_CLASSPATH:$JAVAC_JAR"fi
Add the JDE_CONFIG directory into the classpath that contains the property files as shown below:
if [ "x$JBOSS_CLASSPATH" = "x" ]; then JBOSS_CLASSPATH="$JBOSS_BOOT_CLASSPATH:$JAVAC_JAR"ELSE
JBOSS_CLASSPATH="$JBOSS_CLASSPATH:$JBOSS_BOOT_CLASSPATH:$JAVAC_JAR"fi
JBOSS_CLASSPATH=JDE_CONFIG:$JBOSS_CLASSPATH
In this command, replace JDE_CONFIG with the full path and name of the JD Edwards configuration directory. This directory contains the jdbj.ini, jdeinterop.ini, and jdelog.properties files.
To add the directory into the classpath in the Oracle application server:
In the Oracle application server installation directory, navigate to the opmn directory.
Open the opmn.xml file in a text editor.
Edit the following command:
-Xbootclasspath^/p:D:\product\10.1.3.1\OracleAS_3\bpel\lib\orabpel-boot.jar
Add the JDE_CONFIG directory into the classpath that contains the property files as shown below:
-Xbootclasspath^/p:D:\product\10.1.3.1\OracleAS_3\bpel\lib\orabpel-boot.jar; JDE_CONFIG
In this command, replace JDE_CONFIG with full path and name of the JDE_CONFIG directory. This directory contains the property files jdbj.ini, jdeinterop.ini, and jdelog.properties.
Note:
In this guide, the term Connector Installer has been used to refer to the Connector Installer feature of the Oracle Identity Manager Administrative and User Console.Installing the connector on Oracle Identity Manager release 9.1.0 or later involves the following procedures:
To run the Connector Installer:
Copy the contents of the connector installation media into the following directory:
OIM_HOME/xellerate/ConnectorDefaultDirectory
Log in to the Administrative and User Console by using the user account described in the "Creating the User Account for Installing Connectors" section of Oracle Identity Manager Administrative and User Console.
Click Deployment Management, and then click Install Connector.
From the Connector List list, select JDEdwards 9.0.4.2. This list displays the names and release numbers of connectors whose installation files you copy into the default connector installation directory:
OIM_HOME/xellerate/ConnectorDefaultDirectory
If you have copied the installation files into a different directory, then:
In the Alternative Directory field, enter the full path and name of that directory.
To repopulate the list of connectors in the Connector List list, click Refresh.
From the Connector List list, select JDEdwards 9.0.4.2.
Click Load.
To start the installation process, click Continue.
The following tasks are performed in sequence:
Configuration of connector libraries
Import of the connector XML files (by using the Deployment Manager)
Compilation of adapters
On successful completion of a task, a check mark is displayed for the task. If a task fails, then an X mark and a message stating the reason for failure are displayed. Depending on the reason for the failure, make the required correction and then perform one of the following steps:
Retry the installation by clicking Retry.
Cancel the installation and begin again from Step 0.
If all three tasks of the connector installation process are successful, then a message indicating successful installation is displayed. In addition, a list of the steps that you must perform after the installation is displayed. These steps are as follows:
Ensuring that the prerequisites for using the connector are addressed
Note:
At this stage, run thePurgeCache utility to load the server cache with content from the connector resource bundle in order to view the list of prerequisites. Refer to "Clearing Content Related to Connector Resource Bundles from the Server Cache" for information about running the PurgeCache utility.
There are no prerequisites for some predefined connectors.
Configuring the IT resource for the connector
Record the name of the IT resource displayed on this page. The procedure to configure the IT resource is described later in this guide.
Configuring the scheduled tasks that are created when you installed the connector
Record the names of the scheduled tasks displayed on this page. The procedure to configure these scheduled tasks is described later in this guide.
When you run the Connector Installer, it copies the connector files and external code files to destination directories on the Oracle Identity Manager host computer. These files are listed in Table 1-1.
Installing the Connector in an Oracle Identity Manager Cluster
While installing Oracle Identity Manager in a clustered environment, you must copy all the JAR files and the contents of the connectorResources directory into the corresponding directories on each node of the cluster. See Table 1-1 for information about the files that you must copy and their destination locations on the Oracle Identity Manager server.
Note:
Perform this procedure if you are installing the connector on Oracle Identity Manager release 9.1.0 or later.You must specify values for the parameters of the JDE IT Resource IT resource as follows:
Log in to the Administrative and User Console.
Expand Resource Management.
Click Manage IT Resource.
In the IT Resource Name field on the Manage IT Resource page, enter JDE IT Resource and then click Search.
Click the edit icon for the IT resource.
From the list at the top of the page, select Details and Parameters.
Specify values for the parameters of the JDE IT Resource IT resource. The following table describes each parameter:
| Parameter | Description |
|---|---|
User |
User ID of the user account for connecting to the target system |
Password |
Password of the user account for connecting to the target system |
Environment |
Environment of the user account for connecting to the target system
Sample value: |
Role |
Role of the user account for connecting to the target system
Sample value: |
ProxyUser |
User ID of the system user in the target system |
ProxyUserPassword |
Password of the system user in the target system |
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:
|
To save the values, click Update.
Installing the connector on any Oracle Identity Manager release between releases 8.5.3.1 and 9.0.3 involves the following procedures:
The connector files to be copied and the directories to which you must copy them are given in the following table.
See Also:
The "Files and Directories on the Installation Media" section for more information about these filesNote:
In a clustered environment, copy the JAR files and the contents of theconnectorResources directory to the corresponding directories on each node of the cluster.As mentioned in the "Files and Directories on the Installation Media" 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 opening files is displayed.
Locate and open the JDEConnectorResourceObject.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 following table for information about the values to be specified:
| Parameter | Description |
|---|---|
User |
User ID of the user account for connecting to the target system |
Password |
Password of the user account for connecting to the target system |
Environment |
Environment of the user account for connecting to the target system
Sample value: |
Role |
Role of the user account for connecting to the target system
Sample value: |
ProxyUser |
User ID of the system user in the target system |
ProxyUserPassword |
Password of the system user in the target system |
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:
|
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.
See Also:
If you want to define another IT resource, then refer to Oracle Identity Manager Administrative and User Console Guide for instructions.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.
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 "Copying the Connector 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. An exception is thrown if you run the command described in Step 2 as follows: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 messages that highlight the progress of the application at a 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 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 Server
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, log information is displayed on the server console.
IBM WebSphere Application Server
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, log information is written to the following file:
WEBSPHERE_HOME/AppServer/logs/SERVER_NAME/SystemOut.log
JBoss Application Server
To enable logging:
In the JBoss_home/server/default/conf/log4j.xml file, locate or add the following lines if they are not already present in the file:
<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, log information is written to the following file:
JBoss_home/server/default/log/server.log
Oracle Application Server
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, log information is written to the following file:
OC4J_home/opmn/logs/default_group~home~default_group~1.log
|
 Copyright © 2009, Oracle and/or its affiliates. All rights reserved. Legal Notices |
|