Kbase P158426: What is the preferred method for changing the default port of the AdminServer to run concurrent Admi
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
6/3/2010 |
|
Status: Verified
GOAL:
What is the preferred method for changing the default port of the AdminServer to run concurrent AdminServers in Release 10.x and higher?
GOAL:
What is the preferred method for changing the default port the AdminServer is running on to allow more than one AdminServer to run at the same time for Release 10.x and higher.
GOAL:
How To Configure Multiple Versions of AdminServer To Be Run Concurrently on UNIX or Windows in release 10.x or higher?
GOAL:
How To Change the Port Number when AdminServer is installed on Windows?
GOAL:
How To Change the Port Number when the Admin Server is installed on UNIX?
GOAL:
How To Change the Port the AdminServer is running on?
GOAL:
How to use a non-default port for the AdminServer.
GOAL:
How to run the AdminServer for more than one version of Progress on the same machine at the same time?
GOAL:
Can you run the AdminServer from different Progress versions on the same Windows machine at the same time?
GOAL:
Is it possible to run more than one AdminServer on the same Windows machine?
GOAL:
Need to run the AdminService for more than one version of Progress on the same machine at the same time
FACT(s) (Environment):
All Supported Operating Systems
OpenEdge 10.x
FIX:
Edit the DLC\properties\AdminServerPlugins.properties file, under the [PluginPolicy.Progress.AdminServer] heading to set the desired -port and -adminport settings for the 10.x or higher installation that needs to be changed.
Take care to insure that each AdminServer is running on a unique port and adminport.
If there is a conflict with the default listening port or the default adminport, for example, the port that the AdminServer runs may be changed by editing the DLC\properties\AdminServerPlugins.properties file under the
[PluginPolicy.Progress.AdminServer] section and adding the "port" and "adminport" parameter along with identifying the new port number at the end of this heading as in the example below:
example:
[PluginPolicy.Progress.AdminServer]
pluginclasspath=!{value-of:classpath}
classpath=C:\OpenEdge101C\dlc/java/ext/jmxri.jar,C:\OpenEdge101C\dlc/java/ext/mgmt_agent.jar,C:\OpenEdge101C\dlc/java/ext/mgmt_client.jar,C:\OpenEdge101C\dlc/java/ext/mgmt_config.jar,
:\OpenEdge101C\dlc/java/ext/sonic_Client.jar,C:\OpenEdge101C\dlc/java/progress.jar,C:\OpenEdge101C\dlc/java/osmetrics.jar,C:\OpenEdge101C\dlc/java/jdbc.jar,C:\OpenEdge101C\dlc/java/base.jar,
C:\OpenEdge101C\dlc/java/openedge.jar,C:\OpenEdge101C\dlc/java/util.jar,C:\OpenEdge101C\dlc/java/ext/soap.jar,C:\OpenEdge101C\dlc/java/prorepl.jar,C:\OpenEdge101C\dlc/java/ext/wsdl4j.jar
jvmargs=-Xmx256m -Djava.awt.headless=true -Xbootclasspath/a:C:\OEManage31C\DLC/jars/pja.jar
port= 20999
adminport= 7899