E1: WLS : Starting Oracle HTTP Server 12.1.2 Fails from startComponent.cmd Command When Installed as Standalone Server on Same Machine as a WebLogic Server
(Doc ID 2077644.1)
Last updated on FEBRUARY 25, 2020
Applies to:JD Edwards EnterpriseOne Tools - Version 9.1 and later
Information in this document applies to any platform.
Important Note: The present information is provided as a proof of concept and it is not required nor directly supported by EnterpriseOne support groups. It is presented as an example and any inquiries about WLST (Weblogic Scripting Tool) should be taken with the WebLogic support groups for the best assistance.
Oracle HTTP server 12.1.2 is installed in the same machine as WebLogic server as a "standalone server" following the steps described in the <Document 1475940.1> - JD Edwards EnterpriseOne 9.1.2.x Configuration with Oracle HTTP Server and a DMZ.
A node manager port was configured for Oracle HTTP server (for e.g., say 5557). The node manager port specific to OHS is starting up successfully without any issues.
After installation , the startup of Oracle HTTP server by running ./startComponent.sh fails .
The startcomponent.cmd is trying to connect to the node manager of the WebLogic Server (for e.g., say 5556 ) and fails.
However if Weblogic Scripting tool (WLST) is used to create a script which explicitly mentions the Node manager details , the startup of Oracle HTTP server is successful.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document