Last updated on MAY 30, 2017
Applies to:JD Edwards EnterpriseOne Tools - Version 8.97 and Prior and later
Microsoft Windows (32-bit)
The configuration for the OAS 10g R3 web development feature is set to start the local OC4J immediately when the HTML/Web client is launched. After logging into EnterpriseOne Web Dev client, an error dialog is displayed with the following message:
To troubleshoot this issue, provide console output in text files when manually starting the OC4J using the following steps:
- Go to d:\b7\system\oc4j\j2ee\home\log and delete everything in that directory.
- Create two new empty text files in that directory, one named startOC4J.log and the other named javaVersion.log.
- Change the "StartAppServer=IMME" in the client JDE.INI to "StartAppServer=MANUAL" and save the change.
- Launch the E1 client. Do not do anything but login.
- Open a command prompt and change directories to:
- Invoke the following:
java -version > d:\b7\system\oc4j\j2ee\home\log\javaVersion.log
- In the same command prompt, change directories to
- invoke the following command:
startOC4J.bat > d:\b7\system\oc4j\j2ee\home\log\startOC4J.log
When trying to start the OC4J manually using the startOC4J.bat script, Windows reports that "d:\b7\system\OC4J" is not a valid path in the command window, even though it is. This is seen when working with the same directory in Windows Explorer.
- The "d:\b7" directory is the location specified when installing the EnterpriseOne 8.12 development client.
- The directory is typically named "\e812" and can be installed to any valid drive on a Windows workstation.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms