JD Edwards EnterpriseOne
Connector name |
|
Connector type | Executable |
Type (UI field value) | JD Edwards EnterpriseOne 9.0 (Java) |
Target system versions supported / tested | If you have JD Edwards EnterpriseOne 9.0 installed on your network, Bravura Security Fabric can perform operations using the agents for JD Edwards EnterpriseOne. |
Connector status / support | Customer-Verified Clients may contact Bravura Security support for assistance with this connector. Troubleshooting and testing must be completed in the client's test environment as Bravura Security does not maintain internal test environments for the associated target system. |
Installation / Set up | Version specific files are available in the agent directory on the Bravura Security Fabric server. When targeting using WarningFor proper integration, the OCM (Object Configuration Manager) must be configured to allow the necessary business functions used by Bravura Security Fabric to run on the server. (Not applicable for |
The following Bravura Security Fabric operations are supported by the agents for JD Edwards EnterpriseOne:
user verify password
user change password
enable account
disable account
check account enabled
lock account
unlock account
check account lock
create account (No attributes)
List
accounts
groups
The following sections show you how to prepare your Bravura Security Fabric server to target JD Edwards EnterpriseOne.
Consult your JD Edwards EnterpriseOne documentation for more information.
Preparation
Before Bravura Security Fabric can target JD Edwards EnterpriseOne applications, you must:
Install JD Edwards EnterpriseOne client software.
Configure the Dynamic Java Connector, if communicating with JDE 9.0 (Java).
Installing JD Edwards EnterpriseOne client software
Install the JD Edwards EnterpriseOne client software and development tools onto your Bravura Security Fabric server and ensure that the system path is updated to include the paths to the bin directories. These directories are typically C:\B7\system\bin32 and C:\B7\TS7334\bin32 .
Configuring the Dynamic Java Connector
When targeting using agtjdeow-java.exe, you must configure the Dynamic Java Connector as follows:
Obtain the following jar files from JD Edwards EnterpriseOne server and add them to your CLASSPATH environment variable:
ApplicationAPIs_JAR.jar
ApplicationLogic_JAR.jar
Base_JAR.jar
BizLogicContainer_JAR.jar
BizLogicContainerClient_JAR.jar
BusinessLogicServices_JAR.jar
castor.jar
commons-httpclient-3.0.jar
commons-logging.jar
Connector.jar
EventProcessor_JAR.jar
Generator.jar
j2ee1_3.jar
JdbjBase_JAR.jar
JdbjInterfaces_JAR.jar
JdeNet_JAR.jar
jmxremote.jar
jmxremote_optional.jar
jmxri.jar
log4j.jar
ManagementAgent_JAR.jar
Metadata.jar
MetadataInterface.jar
PMApi_JAR.jar
Spec_JAR.jar
System_JAR.jar
SystemInterfaces_JAR.jar
xerces.jar
xmlparserv2.jar
JDBC drivers
Add the path where the jdelog.properties, jdeinterop.ini, and jdbj.ini files are located into CLASSPATH.
Edit jdeinterop.ini, jdelog.properties, and jdbj.ini for proper settings.
Consult the online documentation for additional configuration information: http://docs.oracle.com/cd/E17984_01/doc.898/e14696/dynamic_java_connector.htm
Targeting JD Edwards EnterpriseOne
Add a JD Edwards EnterpriseOne, add a target system in Bravura Security Fabric (Manage the System > Resources > Target systems).
Type is: JD Edwards EnterpriseOne 9.0 (Java)
Address using the following options:
Environment The name of the JDE environment.
(key: env)
Password update frequency Specifies how often the passwords for user accounts should change. If this option is not set, the default is 60 days.
(key: frequency)
Number of attempts Specifies how many connection attempts should be made to the JDE server before failing. If this option is not set, the default is 3 tries.
(key: attempts)
The address is entered in the following syntax:
env=JDEENV/frequency=25/attempts=5
Troubleshooting
Debugging
The following can be added to the jdeinterop.ini file on the Bravura Security Fabric server to enable debugging on the JDE side:
[DEBUG] log=c:\net.log DebugFile=c:\interopDebug.log JobFile=c:\interop.Log netTraceLevel=2 debugLevel=12
This can provide very useful debugging information from the JDE perspective.