How to Deploy The Administration Console On A Port Different From Other WEB Applications?
(Doc ID 815485.1)
Last updated on DECEMBER 31, 2020
Applies to:Oracle Communications Converged Application Server - Version 4.0.0 and later
Oracle Communications Services Gatekeeper - Version 4.1.0 and later
Information in this document applies to any platform.
WLCP - WebLogic Network Gatekeeper (includes ESDK) - Version: 4.0 to 4.1
BEA Telco WebLogic SIP Server - Version: 4.0 to 4.0
Checked for relevance on 19-May-2011
How to separate the administration traffic from the public HTTP/HTTPS traffic in order to avoid the WebLogic Administration Console being available over the Internet?
In OCSG and OCCAS we have basic domains that allow us to only start one AdminServer and deploy everything on this one server. In this case WEB applications are accessible over the same port as the WebLogic Administration Console - for example http://<host>:7001/console . In addition one might like to enforce that the WebLogic Administration Console can only be called via HTTPS to avoid sniffing out the administration password.
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