Feedback
 
Did this article resolve your question/issue?

   

Your feedback is appreciated.

Please tell us how we can make this article more useful. Please provide us a way to contact you, should we need clarification on the feedback provided or if you need further assistance.

Characters Remaining: 1025

 


Article

How To Configure Multiple Versions of AdminServer To Be Run Concurrently since OpenEdge 10.1B

« Go Back

Information

 
Article Number000014110
EnvironmentProduct: OpenEdge
Version: 10.1B, 10.2x, 11.x, 12.x
OS: All Supported Operating Systems
Other: AdminServer
Question/Problem Description
How to configure multiple versions of AdminServer to be run concurrently without port conficts?
How to change the default ports of multiple AdminServer versions on the same machine?
Steps to Reproduce
Clarifying Information
Error Message
Defect/Enhancement Number
Cause
Resolution
For Progress versions pre OpenEdge 10.1B, refer to Article 000010295, How to configure multiple AdminServer versions to be run concurrently on Windows    

Since the advent of the unified DLC\properties\AdminServerPlugins.properties in OpenEdge 10.1B, the -port and -adminport which need to be changed in order to run multiple different OpenEdge versions on the same machine, can be added to this file for each installed version, instead of the registry as was required previously. This makes this solution portable to environments where the AdminServer runs on UNIX or Windows servers.

Care with port conflicts needs to be taken in order to have different versions of the AdminServer running and working properly on the same server. The AdminServer has two ports set aside for use, with the -port and -adminport parameters.

Where:
  • The port referenced by the -port parameter, is the main AdminServer listening port. All queries and start/stop requests are sent, for example when running: proadsv -query -port <port>, fathom -stop -port <port>, dbman -start -all -port <port>
The default AdminServer listening port is 20931 across all Progress OpenEdge versions.
  • The port referenced by the -adminport parameter, is the communication port between the servergroup and the AdminServer used by databases to communicate with the AdminServer. For example to re-connect to the AdminServer when the AdminServer is restarted.
The default AdminServer communication port for different Progress versions are documented in Article:
To change the -adminport and -port that the AdminServer service uses:

The ports on which the AdminServer is listening (-port) and communicating (-adminport), can be uniquely defined in the DLC\properties\AdminServerPlugins.properties file, for each OpenEdge 10.1B and later AdminServer version running on the same machine.

1.  Shutdown any instances of the AdminServer for which the change are needed.

2.  Backup and then Open DLC\properties\AdminServerPlugins.properties file in a text editor

3.  Append the port and adminport arguments at the end of the following Section:
  • For each OpenEdge 10.1B to 11.6 version, find the section: [PluginPolicy.Progress.AdminServer] 
  • For OpenEdge 11.7, find the section: [PluginPolicy.Progress.ProAdsv]
Example:

[PluginPolicy.Progress.AdminServer] or [PluginPolicy.Progress.ProAdsv]

pluginclasspath=!{value-of:classpath}     
classpath=<full classpath referencing necessary .jar files>
jvmargs=-Xmx1024m -Xrs -Djava.awt.headless=true -Xbootclasspath/a:oee/dlc/jars/pja.jar 
port=20941
adminport=7841


4.  Start the AdminServer. 

Considerations:
  • 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.
Example:
  1. Two AdminServers running on two different listening ports (-port 20931, and -port 20932).
  2. A distinct -adminport is not specified.
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.
  • The value of -adminport must not be the same Server port that is used for any of the OpenEdge Server products. These are two different ports, for different purposes.
  • When using the associated 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 (retired) Progress Explorer > Properties > Advanced > Server Port Number. Alternatively add the -port argument and port number to the ubutil.bat file:
:endparm
set PARMS=%PARMS% -port 20951
OpenEdge 12 added switches to the proadsv command for the DBAgent (-agentport) and Remote AdminServer (-mgmtport):
Workaround
Notes
Attachment 
Last Modified Date10/18/2019 2:30 PM