Kbase P18467: How to Configure Multiple Versions of AdminServer to be run concurrently on UNIX
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
29/07/2008 |
|
Status: Verified
GOAL:
How to Configure Multiple Versions of AdminServer to be run concurrently on UNIX
GOAL:
Is it possible to run multiple versions of Progress on the same machine?
FACT(s) (Environment):
Progress 9.1x
OpenEdge 10.x
All Supported Operating Systems
FIX:
Yes. Several versions of the AdminServer / AdminService can be running on the same machine at the same time, however care needs to be taken in order to have them all working properly.
The ports the AdminServer listens and communicates on must be configured on each AdminServer so each uses unique ports.
For example:
One AdminServer can use the default ports of 20931 and 7832, and a second AdminServer can be configured to use ports 20932 and 7833 and so on.
The AdminServer has two parameters which are used to set the two ports it uses for communication, these are -port and -adminport.
The port referenced by -port is the main AdminServer listening port, where all queries, and start/stop requests are sent. By default, this is port 20931.
The port referenced by -adminport is used by databases to communicate with the AdminServer.
The default value for -adminport varies depending on the version of Progress / OpenEdge. Refer to Solution P104080 below for more details on those port numbers.
One reason the AdminServer may fail to start is if the adminport port is in use.
If this port is in use already by any other process the socket can not be bound to by a new process.
Example:
If two AdminServers were started on one machine and the -port parameter was used for each to differentiate the main communication port, the second of the two AdminServers would not start since a separate -adminport was not specified. They would both try to open the same -adminport (if they were the same version AdminServer).
The value of -adminport should NOT be the same port you intend to use for the database server. The purpose for the -adminport is for the AdminServer to communicate with the database to validate it's status and give a constant means for controlling the database. It is not the port specified for database startup by the parameter -S.
Please remember that the Progress Explorer and the AdminServer need to be the same version. If a version 9.1B AdminServer is started, then a version 9.1B Progress Explorer should be used to connect to it. Variations in version between Progress Explorer and AdminServer can lead to problems.
SYNTAX
proadsv -start [ -adminport port-number ] | -stop | -query [ -port port-number ] | -help
PARAMETERS
-adminport port-number
Specifies the port number used by the AdminServer for database broker communication. If a port number is not specified, the adminport defaults to port 7836.
-port port-number
Specifies the listening port number. If a port number is not specified, the port defaults to 20931.
One possible use for two versions of the AdminServer on one machine might be to allow one version for development and one for Production.
Example:
Start the first AdminServer: proadsv -adminport 7832 -port 20931
Start the second AdminServer: proadsv -adminport 7833 -port 20932