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 change the port the AdminServer is running on to allow more than one AdminServer to run at the same time pre 10.1B?

« Go Back

Information

 
Article Number000001377
EnvironmentProduct: Progress
Version: 9.x
Product: OpenEdge
Version: 10.0x, 10.1A
OS: All supported platforms
Question/Problem Description
How To Change the Port Number when AdminServer is installed on Windows?
How To Change the Port Number when the Admin Server is installed on UNIX?
How To Change the Port the AdminServer is listening on?
How to use a non-default port for the AdminServer?
How to run the AdminServer for more than one version of Progress on the same machine at the same time?
Can you run the AdminServer from different Progress versions on the same Windows machine at the same time?
Is it possible to run more than one AdminServer on the same Windows machine?
Need to run the AdminService for more than one version of Progress on the same machine at the same time.
Steps to Reproduce
Clarifying Information
Error Message
Defect/Enhancement Number
Cause
Resolution
For OpenEdge 10.1B and later, refer to Article: P159835, How To Configure Multiple Versions of AdminServer To Be Run Concurrently since OpenEdge 10.1B   

The AdminServer runs on port 20931 as default listening port for command line utilities (eg: dbman) and adminport 7832 for default communication between the servergroup and the AdminServer on both UNIX and Windows systems by default for all versions of Progress 9.x.

Ensure each AdminServer is running on a unique port and adminport. The default adminport for different Progress versions are documented in Article P104080, What are the default ports used by the AdminServer?   

UNIX:

If there is a conflict with the default listening port number 20931, for example, the port that the AdminServer runs on (on UNIX) can be changed by adding the -port argument along with identifying the new port number at the end of the startup command.

Example:
     $  proadsv -start -port 20932

To have multiple Admin Servers started on UNIX,  add the -adminport startup command to the proadsv command along with -port

Example:
For the Progress 9.1C AdminServer
$  proadsv -start -port 20932 -adminport 7833
For the Progress 9.1E AdminServer
$  proadsv -start -port 21932 -adminport 8833

The proadsv script in the $DLC/bin directory may be modified to make this easier.
The last line of the proadsv script typically looks like the following:
exec $JVMSTRT -w $WRKDIR -o stderr  -m silent $JREHOME/bin/$JVMEXE -classpath $CLASSPATH $JVMARGS -Djava.security.policy=$JAVAPOLICY -DInstall.Dir=$DLC -DWork.Dir=$WRKDIR -Djvmstart.debug=$JVMSTRT_DBGOPT  -Djava.command=$JVMEXE -Dadmsrv.jvm
=$JREHOME/bin/$JVMEXE  -Djava.jvmargs="$JVMARGS" $ADMSRVRCLASS $@

To set the AdminServer to start on port 20932 with an adminport of 8833 modify the line as follows:
exec $JVMSTRT -w $WRKDIR -o stderr  -m silent $JREHOME/bin/$JVMEXE -classpath $CLASSPATH $JVMARGS -Djava.security.policy=$JAVAPOLICY -DInstall.Dir=$DLC -DWork.Dir=$WRKDIR -Djvmstart.debug=$JVMSTRT_DBGOPT  -Djava.command=$JVMEXE -Dadmsrv.jvm=$JREHOME/bin/$JVMEXE  -Djava.jvmargs="$JVMARGS" $ADMSRVRCLASS -port 20932 -adminport 8833 $@

WINDOWS:

To change the port that the AdminServer uses on Windows:

1) Stop the AdminService(s) through: Control Panel / Services. 
If manually started, stop these from a PROENV shell: proadsv -stop
 
2) Run regedit.  

It is strongly recommended to backup the registry entires before making any changes. 
Add the -port -adminport arguments along with the port numbers to the startup and shutdown entries.

For 32-bit Windows:
    HKEY_LOCAL_MACHINE\SOFTWARE\PSC\AdminService\(version_of_Progress)\StartupCmd
    HKEY_LOCAL_MACHINE\SOFTWARE\PSC\AdminService\(version_of_Progress)\ShutdownCmd

For 64-bit Windows:
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\PSC\AdminService\(version_of_Progress)\StartupCmd
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\PSC\AdminService\(version_of_Progress)\ShutdownCmd

Example:  Notice that the -port 21932 -adminport 8833 have been added to the end of the string before the "-start -service".
"C:\bin\jvmstart" -o eventmgr -w @{WorkPath} @{JAVA\JREHOME}\bin\jre -classpath @{JAVA\JRECP};@{JAVA\PROGRESSCP} @{JAVA\JVMARGS} -DInstall.Dir=@{Startup\DLC} -DWork.Dir=@{WorkPath} com.progress.chimera.adminserver.AdminServer -port 21932 -adminport 8833 -start -service

3)  If using the Progress Explorer:
    a.) Ensure that you have specified the port in the "properties" -> [advanced tab] ."port", otherwise the default port will still be specified here.
    b.) You must use the Progress Explorer tool from the same version of Progress as the AdminServer is running. Therefore Progress Explorer 9.1C to AdminServer 9.1C, Progress Explorer 9.1E to AdminServer 9.1E, you cannot use Progress Explorer 9.1C to AdminServer 9.1E.

When no longer using the default listening and communication ports, the listening port that the AdminServer is now using must be specified when running command line utilities like proadsv; wtbman; asbman; dbman; nsman.

Example:
$ proadsv -start -port 21932 -adminport 8833 
$ proadsv -query
AdminServer not alive. (8543) # because the listening port was not used
$ proadsv -query -port 21932
AdminServer is alive. (8545).
Workaround
Notes

 
Attachment 
Last Modified Date9/13/2015 4:14 AM