Kbase 18919: How to change the port the AdminServer is running on to allow more than one AdminServer to run at th
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
5/6/2011 |
|
Status: Verified
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
Progress 9.x
OpenEdge 10.x
FIX:
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.
You must therefore make sure each AdminServer is running on a unique port and adminport.
UNIX:
If there is a conflict with the default listening port number 20931, for example, you can change the port that the AdminServer runs on (on UNIX) by adding the -port argument along with identifying the new port number at the end of your startup command.
For example:
$ proadsv -start -port 20932
If you need to have multiple Admin Servers started on UNIX, you need to add the -adminport startup command to proadsv command as well
For 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 $@
If you wished to set the AdminServer to start on port 20932 with an adminport of 8833 you would 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:
- If you want to change the port that the AdminServer uses on Windows NT, follow these steps:
1) Go to the Control Panel / Services. Make sure you that you have stopped your AdminServer service(s).
2) Run regedit. You will have to add the -port -adminport arguments along with the port numbers to the startup and shutdown entries in your Registry.
These registry keys are:
HKEY_LOCAL_MACHINE\SOFTWARE\PSC\AdminService\(version_of_Progress)\StartupCmd
HKEY_LOCAL_MACHINE\SOFTWARE\PSC\AdminService\(version_of_Progress)\ShutdownCmd
An example of the 'edit string' for the StartUpCmd in your Registry would be:
"C:\V9\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
Notice that the -port 21932 -adminport 8833 have been added to the end of the string before the "-start -service".
Please be careful when you edit the registry key manually. You should not change the other parameters in this registry key, unless instructed to do so, or your AdminServer may not start up again. It is strongly recommended to backup the registry entires before making any changes.
3) If using the Progress Explorer:
a.) Make sure 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 you're no longer using the default listening and communication ports, you need to specify the listening port that the AdminServer is now running on when running command line utilities like proadsv; wtbman; asbman; dbman; nsman.
For example:
$ proadsv -start -port 21932 -adminport 8833
PROGRESS Version 9.1E01 as of Thu Feb 3 22:30:10 EST 2005
$ proadsv -query
PROGRESS Version 9.1E01 as of Thu Feb 3 22:30:10 EST 2005
AdminServer not alive. (8543) # because the listening port was not used
$ proadsv -query -port 21932
PROGRESS Version 9.1E01 as of Thu Feb 3 22:30:10 EST 2005
AdminServer is alive. (8545).