Kbase P159835: How To Configure Multiple Versions of AdminServer To Be Run Concurrently on Windows since 10.1B
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
25/05/2011 |
|
Status: Verified
GOAL:
How to configure multiple versions of AdminServer to be run concurrently.
GOAL:
How to setup multiple AdminServers on Windows
FACT(s) (Environment):
OpenEdge Category: Configuration
OpenEdge 10.1B
OpenEdge 10.2x
Windows
FIX:
Please refer to Solution P10465, "How To Configure Multiple Versions of AdminServer To Be Run Concurrently on Windows" for instructions on Progress OpenEdge versions pre OpenEdge 10.1B
It is possible to have several versions of the AdminServer running on the same server, but some care needs to be taken in order to have them all working properly.
The AdminServer has two ports set aside for use which can be configured from the Windows registry. To set the two ports, use the parameters -port and -adminport.
Where:
The port referenced by -port is the main AdminServer listening port, where all queries, and start/stop requests are sent.
The port referenced by -adminport is used by databases to communicate with the AdminServer.
The default AdminServer -adminports vary by version since Progress 9.1E01+ and OpenEdge 10.0B02, so essentially only the default -port 20931 needs to be changed to run one instance of each, but any available port can be used:
7835 is the default -adminport for any Progress 9 version below 9.1E, OpenEdge 10 and 10.0B SP01 (included)
7836 is the default -adminport for Progress 9.1E01+
7837 is the default -adminport for OpenEdge 10.0B02+
7838 is the default -adminport for OpenEdge 10.1A
7839 is the default -adminport for OpenEdge 10.1B
7840 is the default -adminport for OpenEdge 10.1C
7841 is the default -adminport for OpenEdge 10.2A
7842 is the default -adminport for OpenEdge 10.2B
For each AdminServer version, the ports on which the AdminServer is listening (-port) and communicating (-adminport), need to be uniquely defined in the
%DLC%\properties\AdminServerPlugins.properties file.
STEPS:
To change the -adminport (and -port as needed) that the AdminServer service uses on Windows:
1) Shutdown any instances of the AdminServer for which the change are needed
2a) Backup and then Open %DLC%\properties\AdminServerPlugins.properties file in a text editor
2b) Find the section: [PluginPolicy.Progress.AdminServer] and append the port and adminport arguments
For example:
[PluginPolicy.Progress.AdminServer]
pluginclasspath=!{value-of:classpath}
classpath=D:\102A\DLC/java/ext/jmxri.jar,D:\102A\DLC/java/ext/mgmt_agent.jar,D:\102A\DLC/java/ext/mgmt_client.jar,D:\102A\DLC/java/ext/mgmt_config.jar,D:\102A\DLC/java/ext/sonic_Client.jar,D:\102A\DLC/java/progress.jar,D:\102A\DLC/java/osmetrics.jar,D:\102A\DLC/java/jdbc.jar,D:\102A\DLC/java/base.jar,D:\102A\DLC/java/openedge.jar,D:\102A\DLC/java/util.jar,D:\102A\DLC/java/ext/soap.jar,D:\102A\DLC/java/prorepl.jar,D:\102A\DLC/java/ext/wsdl4j.jar
jvmargs=-Xmx256m -Xrs -Djava.awt.headless=true -Xbootclasspath/a:D:\oee\dlc/jars/pja.jar
port=20941
adminport=7841
3) Start the AdminServer
Note: This Solution is also portable to environments where the AdminServer runs on an UNIX box.
Considerations:
1.) The AdminServer will fail to startup if the adminport port is in use. If this port is in use already, another server socket cannot be created using this port. For example:
If two AdminServers running on two different listening ports (-port 20931, and -port 20932). If a separate -adminport is not specified on these, they will both try to open the default adminport for that Progress version (eg: 7832), so one of them will fail to start. Another reason could be that the -port (20931, 20932) or -adminport (7835) is already in use by some other process.
2.) The value of -adminport must NOT be the same port that is used for any of the database servers. These are two different .ports, for different purposes.
3.) The Progress Explorer and the AdminServer need to be the same version and patch level exactly. ie: If the AdminService of 10.0B02 is started, then connect to it using Progress Explorer 10.0B02.
4.) When using the assocated command-line utilities (proadsv, nsman, dbman, asbman, wtbman) remember to use the appropriate -port argument for the AdminServer in use, this also applies to the Progress Explorer > Properties > Advanced > Server Port Number. The OpenEdge Explorer does not require any change if the default port and adminport are changed.
5.) Progress Solution P45120, "Instances in Progress Explorer get lost when using multi Progress versions".