| Oracle® Identity Manager Connector Guide for JD Edwards EnterpriseOne Release 9.0.3 Part Number B32448-02 |
|
|
View PDF |
| Oracle® Identity Manager Connector Guide for JD Edwards EnterpriseOne Release 9.0.3 Part Number B32448-02 |
|
|
View PDF |
Deploying the connector involves the following steps:
This chapter also discusses the following topic:
The following table lists the deployment requirements for the connector.
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\JDE9.0.3\Properties
|
If the EnterpriseOne server is running on Oracle Database, then copy the tnsnames.ora file to the specified destination directory. |
OIM_home\Xellerate\JDE9.0.3\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\JDE9.0.3\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 |
Configuring the Oracle Identity Manager server involves the following procedures:
Changing to the required input locale involves installing the required fonts and setting the required input locale. To set the required input locale:
Note:
Depending on the operating system used, you may need to perform this procedure differently.Open Control Panel.
Double click Regional Options.
On the Input Locales tab of the Regional Options dialog box, add and switch to the input locale that you want to use.
Whenever you add a new resource bundle file in the OIM_home\xellerate\connectorResources directory or make a change in an existing resource bundle file, 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.
Enter one of the following commands:
Note:
You must perform Step 1 before you perform this step.If you run the command as follows, then an exception is thrown:
OIM_home\xellerate\bin\batch_file_name
On Microsoft Windows
PurgeCache.bat ConnectorResourceBundle
On UNIX
PurgeCache.sh ConnectorResourceBundle
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:
For JBoss Application Server
To enable logging:
In the JBoss_home\server\default\conf\log4j.xml file, locate the following lines:
<category name="XELLERATE">
<priority value="log_level"/>
</category>
In the second XML code line, replace log_level with the log level that you want to set. For example:
<category name="XELLERATE"> <priority value="INFO"/> </category>
After you enable logging, log information is written to the following file:
JBoss_home\server\default\log\server.log
For IBM WebSphere:
To enable logging:
Add the following line in the OIM_home\xellerate\config\log.properties file:
log4j.logger.XELLERATE=log_level
In this line, replace log_level with the log level that you want to set.
For example:
log4j.logger.XELLERATE=INFO
After you enable logging, log information is written to the following file:
WebSphere_home\AppServer\logs\server_name\startServer.log
For BEA WebLogic
To enable logging:
Add the following line in the OIM_home\xellerate\config\log.properties file:
log4j.logger.XELLERATE=log_level
In this line, replace log_level with the log level that you want to set.
For example:
log4j.logger.XELLERATE=INFO
After you enable logging, log information is written to the following file:
WebLogic_home\user_projects\domains\domain_name\server_name\server_name.log
For OC4J
To enable logging:
Add the following line in the oim_home\xellerate\config\log.properties file:
log4j.logger.XELLERATE=log_level
In this line, replace log_level with the log level that you want to set.
For example:
log4j.logger.XELLERATE=INFO
After you enable logging, log information is written to the following file:
OC4J_home\opmn\logs\default_group~home~default_group~1.log
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\JDE9.0.3\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. Remove these nodes by right-clicking each node and then selecting Remove.
Click Import. The connector XML file is imported into Oracle Identity Manager.
If you plan to use the connector in trusted source reconciliation mode, then perform the same procedure to import the JDEConnectorXLResourceObject.xml file. This file is in the OIM_home\Xellerate\JDE9.0.3\xml directory.
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:
|
Configuring reconciliation involves the following steps:
Note:
Perform this step of the procedure only if you want to configure trusted source reconciliation. Only one connector can be configured for trusted source reconciliation. If you import theJDEConnectorXLResourceObject.xml file while you have another trusted source configured, then both connector reconciliations would stop working.
Refer to Oracle Identity Manager Connector Framework Guide for conceptual information about reconciliation configurations.
To configure trusted source reconciliation, you must first import the XML file for trusted source reconciliation as follows:
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 JDEConnectorXLResourceObject.xml file, which is in the OIM_home\Xellerate\JDE9.0.3\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 Import.
In the message that is displayed, click Import to confirm that you want to import the XML file and then click OK.
Then, set the value of the isTrustedSource reconciliation scheduled task attribute to True while performing the procedure described in the following section.
Expand the Xellerate Administration folder.
Select Task Scheduler.
Click Find. The details of the predefined scheduled tasks are displayed on two different tabs.
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 ERROR status to the task.
Ensure that the Disabled and Stop Execution check boxes are not selected.
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.
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.
Provide values for the attributes of the scheduled task. Refer to the "Specifying Values for the Scheduled Task Attributes" section for information about the values to be specified.
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.
Repeat Steps 5 through 10 to create the second scheduled task.
This section provides information about the values to be specified for the following scheduled tasks:
You must specify values for the following attributes of the lookup fields reconciliation 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.After you specify values for the task attributes, proceed to Step 10 of the procedure to create scheduled tasks.
You must specify values for the following attributes of the user reconciliation 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.| Attribute | Description | Sample Value |
|---|---|---|
Organization |
Default organization assigned to a new user | Xellerate Users |
Xellerate Type |
Default type assigned to a new user | End-User Administrator |
Role |
Default role assigned to a new user | Consultant |
ITResource |
Name of the IT Resource for setting up a connection with JD Edwards | JDE IT Resource |
ResourceObject |
Name of the resource object that is used for | JDE Resource Object |
isTrustedSource |
Specifies whether or not trusted source reconciliation is to be performed
If it is set to If it is set to |
false |
Password |
Default dummy password | dummy |
XLDeleteUsersAllowed |
Specifies whether or not users are to be deleted in Oracle Identity Manager during user reconciliation | false |
After you specify values for the task attributes, proceed to Step 10 of the procedure to create scheduled tasks.
The following adapters are imported into Oracle Identity Manager when you import the JDEResourceObject.xml file:
Enable and Disable User
JDE Delete User
Modify Password
PrePopulate JDE Form
JDE Remove Role
JDE Modify User
JDE Create User
JDE Add Role
You must compile these adapters before you can use them to provision accounts on the target system.
To compile adapters by using the Adapter Manager form:
Open the Adapter Manager form.
To compile all the adapters that you import into the current database, select Compile All. To compile multiple (but not all) adapters, select the adapters you want to compile. Then, select Compile Selected.
Note:
Click Compile Previously Failed to recompile only those adapters that were not compiled successfully. Such adapters do not have an OK compilation status.Click Start. Oracle Identity Manager compiles the selected adapters.
If Oracle Identity Manager is installed in a clustered environment, then copy the compiled adapters from the OIM_home\xellerate\Adapter directory to the same directory on each of the other nodes of the cluster. If required, overwrite the adapter files on the other nodes.
To view detailed information about an adapter:
Highlight the adapter in the Adapter Manager form.
Double-click the row header of the adapter, or right-click the adapter.
Select Launch Adapter from the shortcut menu that is displayed. Details of the adapter are displayed.
Note:
Perform this procedure only if you want to configure the connector for multiple installations of JD Edwards. Refer to Oracle Identity Manager Design Console Guide for detailed instructions on performing each step of this procedure.To configure the connector for multiple installations of the target system:
Create and configure one resource object for each target system installation. The Resource Objects form is in the Resource Management folder. The JDE Resource Object resource object is created when you import the connector XML file. You can use this resource object as the template for creating the remaining resource objects.
Create and configure one IT resource for each resource object. The IT Resources form is in the Resource Management folder. The JDE IT Resource IT resource is created when you import the connector XML file. You can use this IT resource as the template for creating the remaining IT resources, of the same resource type.
Create and configure one process definition for each resource object.
The Process Definition form is in the Process Management folder. The JDE Process process definition is created when you import the connector XML file. You can use this process definition as the template for creating the remaining process definitions. While creating each process definition, the following steps that you must performare specific to this procedure:
From the Object Name lookup field, select the resource object that you create in Step 1.
While mapping the adapter variables for the IT Resource data type, ensure that you select the IT resource that you create in Step 2 from the Qualifier list. Design one process form for each process definition.
The Form Designer form is in the Development Tools folder. The following process forms are created when you import the connector XML file:
UD_JDE (parent form)
UD_JDEROL (child form for multivalue attributes)
You can use these process forms as templates for creating the remaining process forms. While creating the process forms, from the Object Name lookup field, select the resource object that you create in Step 1.
Configure reconciliation for each target system installation. Refer to the "Step 6: Configuring Reconciliation" section for instructions. Note that only the values of the following attributes are to be changed for each reconciliation scheduled task:
ITResource
ResourceObject
isTrustedSource
Set the isTrustedSource attribute to True for the JD Edwards installation that you want to designate as a trusted source. You can designate either a single or multiple installations of JD Edwards as the trusted source. For the remaining JD Edwards installations, set this attribute to False.
If required, modify the fields to be reconciled for the Xellerate User resource object. When you use the Administrative and User Console to perform provisioning, you can specify the IT resource corresponding to the JD Edwards installation to which you want to provision the user.
