Salesforce

How to change the default http listener port used by OpenEdge Management / Explorer ?

« Go Back

Information

 
TitleHow to change the default http listener port used by OpenEdge Management / Explorer ?
URL NameP155290
Article Number000132305
EnvironmentProduct: OpenEdge
Version: 10.1C04, 10.2x, 11.x, 12.x
OS: All supported platforms
Other: OpenEdge Management OEM, OpenEdge Explorer OEE
Question/Problem Description
How to change the default http listener port used by OpenEdge Management?
How to change the default port used by OpenEdge Explorer?
How to modify the Web server HTTP Listener Port used by the AdminServer
How to start OpenEdge Explorer Console Browsers against different OpenEdge versions?
How to change the Jetty or Tomcat WebServer http listener port when running multiple versions of OEE or OEM?
Steps to Reproduce
Clarifying Information
The default http listener port is 9090.  
Error Message
Defect Number
Enhancement Number
Cause
Resolution
In OpenEdge 10 and 11 versions:

OpenEdge Management is a web application hosted in the Jetty Web Server. This Jetty web server is hosted as a plugin to the AdminServer. 
The AdminSever connects through the Jetty WebServer HTTP Listener Port (default=9090) which will need to be changed when remote monitoring of other versions is not used. 

The default http listener port is 9090. Its value can be changed by editing the fathom.properties file and restarting the AdminServer.
  • OpenEdge 10.1C and 10.2A : {OEE | OEM installation directory}\config\fathom.properties  
  • OpenEdge 10.2B and 11 : {DLC OpenEdge installation directory}\properties\fathom.properties
If OpenEdge Explorer (OEE) or OpenEdge Management (OEM) has never previously been started, the fathom.properties file will not show an entry for the http port as this is updated in the fathom.properties file as part of the initialization screens at first login, otherwise it will already have the default port:9090 tailored unless otherwise specified during the initialization tailoring.

To change the default http listener port:

Edit the [webserver] Section in the fathom.properties file, to change the port number to the required port available:
 
[webserver]
    httpenabled=true
    httpport=<newPortHere>

Save the file and restart the AdminServer.

In OpenEdge 12 - OEM is installed as a standalone web application running in a Tomcat.

Since OpenEdge 12.0 OEM/OEE is no longer a self-hosted web application running as a part of the AdminServer, it has been converted to a pure web application running in Tomcat. The OEM/OEE (fathom.plugin) has been abstracted from the AdminServer and is exposed as a webapp running on a PASOE instance which uses the tomcat http(s) listener port. As such there is no longer the need to that enable (glue) and disable (unglue) OEM functionality. The OEM install directory is effectively the directory of a deployed PAS instance

The  http(s) listener port used by the OpenEdge Management/Explorer webinterface can be found under "port #s used by server.xml"
in: 
  • {OEE | OEM installation directory}\conf\catalina.properties
psc.as.http.port=9090
psc.as.https.port=9443

Restart the PASOE instance:
 
1. Windows restart the service "OpenEdge Management Service for OpenEdge".
        
2. From the commandline with pasman or tcman
$OEM/bin/tcman service start (on windows)
$OEM/bin/tcman start (if not service, if not on windows)
 
Update the URL:
  1. Modify the OpenEdge Console Browser address accordingly eg: http://<host>:<newPortHere>
  2. Modify the fathom.url to reflect the updated url port.  
The fathom.url file is located in the OpenEdge installation and/or the OpenEdge Management (OEM) / OpenEdge Explorer (OEE) installation path (depending upon the OpenEdge version).  

Example:  
Pre-OpenEdge 10.2B the fathom.url file is located in OpenEdge installation path.
Post-OpenEdge 10.2B, 11, 12: the fathom.url file is located in OpenEdge Management/Explorer installation path.
 
Workaround
Notes
References to Other Documentation:

Progress Article: 
How To Configure Multiple Versions of AdminServer To Be Run Concurrently since OpenEdge 10.1B      
Keyword Phrase
Last Modified Date11/20/2020 6:55 AM

Powered by