Release 10.1A: OpenEdge Data Management:
Database Administration

> ## PROADSV utility

> Starts, stops, or queries the current installation of an AdminServer on UNIX.

> #### Syntax

> proadsv { -start | -stop | -query } [ -port `port-number` ] [ -adminport `port-number` ] [ -cluster ] [ -hostname `host-name` ] [ -help ]

> #### Parameters

> ``-start``

> Starts the AdminServer.

> ``-stop``

> Stops the AdminServer.

> ``-query``

> Displays AdminServer status.

> ``-port` `port-number``

> Specifies the listening port number for online command utilities, such as DBMAN. If a port number is not specified, it defaults to 20931.

> ``-adminport` `port-number``

> Specifies the listening port number for communication between a server group and an AdminServer. The default port number is 7832.

> ``-cluster``

> Specifies to the AdminServer that it is running in a clustered environment.

> ``-hostname` `host-name``

> Specifies that the AdminServer should bind the RMI registry to the host `host-name`. In a clustered environment, use the cluster alias as the value for `host-name`. In the event of a failover, using the cluster alias guarantees availability of the RMI registry for the AdminServer.

> ``-help``

> Displays command-line help.

> #### Notes

> - In Windows, the AdminServer runs as a service. The AdminServer is configured to automatically start. You can change the listening port for the AdminServer by adding
>   -`port` `port-number` or `-adminport` `port-number` (either one or both) to the following registry keys:

>     HKEY_LOCAL_MACHINE\SOFTWARE\PSC\AdminService\version\StartupCmd
>     or
>     HKEY_LOCAL_MACHINE\SOFTWARE\PSC\AdminService\version\ShutdownCmd

> To change the default port, add `-port` or `-adminport` and the port number to the end of the value. If you add both `-port` and `-adminport`, be sure not to use the same port number. Be sure to leave a space between `-port` or `-adminport` and the port number. For example:

>     ....AdminServer -port 9999 -adminport 7832

> - To run more than one AdminServer on a single system, specify a unique `-adminport` `port-number` and `-port` `port-number` for each AdminServer. Failure to do so can result in communication errors between AdminServer and server groups.

> - An AdminServer is installed on every system where you install an OpenEdge database, ODBC DataServer or ORACLE DataServer, AppServer, NameServer, WebSpeedŽ Transaction Server, or WebSpeed Messenger. The AdminServer must be running in order to use any of the Progress Explorer configuration tools or command-line configuration utilities, such as DBMAN.

> - See Chapter 3, "Starting Up and Shutting Down," for additional information describing the Progress Explorer Framework, including an AdminServer.

> - PROADSV supports the use of internationalization startup parameters such as `-cpinternal codepage` and `-cpstream` `codepage`. See Chapter 18, "Database Startup Parameters," for a description of each database-related internationalization startup parameter.

Copyright © 2005 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095