PROADSV utility

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

Syntax


`proadsv { -start \| -stop \| -query } [ -help ] [ options ]`

Parameters

-start: Starts the AdminServer.
-query: Displays AdminServer status.
-stop: Stops the AdminServer.
-help: Displays command-line help.
options: The options that are supported are determined by whether you are running a start, query, or stop request. These options are described in this topic.

PROADSV -start usage options

The PROADSV -start action supports the following options:

`proadsv -start [ -help ] [-f plugins-filename ] [ -port port-number ] [ -adminport port-number ] [ -agentport port-number ] [ -cluster ][ -host host-name ] [ -mgmtport port-number ] [ -dbproperties filename] [ -dbaproperties filename] [ -smdbproperties filename] [ -ubproperties filename] [ -pasproperties filename] [ -mgmtproperties filename] [ -activemqini filename] [ -interactive { true \| false } ] [ -admingroup groupnames] [ -requireusername ]`

proadsv -start [ -help ] [-f plugins-filename ] [ -port port-number ]
   [ -adminport port-number ] [ -agentport port-number ]
   [ -cluster ][ -host host-name ]
   [ -mgmtport port-number ] [ -dbproperties filename]
   [ -dbaproperties filename]
   [ -smdbproperties filename] [ -ubproperties filename]
   [ -pasproperties filename] [ -mgmtproperties filename]
   [ -activemqini filename] [ -interactive { true | false } ]
   [ -admingroup groupnames] [ -requireusername ]

PROADSV -start Parameters

-help

Displays command-line help.

-f plugins-filename

List of Progress Explorer plugins. Default is $DLC/properties/AdminServerPlugins.properties.

-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 in OpenEdge 12.2 is 7849. For more information about the -adminport defaults, see the following Progress Knowledge Base article: What are the default ports used by the AdminServer?

-agentport port-number

Specifies the port number used by the database management agent to communicate with the AdminServer. To override the default value, specify the value in the command prompt or change it in the $DLC/propertes/agent.properties file.

-cluster

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

-host host-name

Specifies that the AdminServer should bind the RMI registry to the host host. 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. The host can also be specified in the AdminServerPlugin.properties args property as:

args=-host IP address or hostname -port port-number

-mgmtport port-number

Specifies the port number used by the AdminServer to accept remote monitoring connections from OpenEdge Management. This defaults to 6835. To avoid conflicts with other AdminServers running on the same machine, override the default value.

-dbproperties filename

Database configuration information. Default is the $DLC/propertes/conmgr.properties file.

-dbaproperties filename

Database agent configuration information. Default is the $DLC/propertes/agent.properties file.

-smdbproperties filename

Script managed database configuration information. Default is the $DLC/propertes/smdatabase.properties file.

-ubproperties filename

UBroker configuration information. Default is the $DLC/propertes/ubroker.properties file.

-pasproperties filename

Progress Application Server configuration information. Default is the $DLC/propertes/pasmgr.properties file.

-mgmtproperties filename

Management configuration information. Default is the $DLC/propertes/management.properties file.

-activemqini filename

Activemq ini file. Default is the $DLC/propertes/activemqs.ini file.

-interactive { true | false }

Run the AdminServer process in the foreground. Default is false.

-admingroup groups

Colon-separated list of group names.

-requireusername

Require at least one user ID to be resolved for each AdminServer operation before it will be executed.

PROADSV -query usage options

The PROADSV -query action supports the following options:


`proadsv -query [ -help ] [ -all ] [ -verbose ] [ -port port-number ]`

PROADSV -query Parameters

-help: Displays command-line help.
-all or -verbose: List all items managed by the AdminServer.
-port port-number: Specify the listening port number where the AdminServer process resides.

PROADSV -stop usage options

The PROADSV -stop action supports the following options:


`proadsv -stop [ -help ] [ -keepservers ] [ -port port-number ] [ -user username ] [ -password password ]`

PROADSV -stop Parameters

-help: Displays command-line help.
-keepservers: Do not shutdown running servers.
-port port-number: Specifies the listening port number where the AdminServer process resides. Default is 20931.
-user username: Specifies the user with AdminServer process privileges. Default is current user.
-password password: Specifies the password associated with the given user.

Notes

To change the default listening and communication ports for the AdminServer on either UNIX or Windows environments, use the AdminServerPlugins.properties file. The ports that the AdminServer uses are defined or changed by editing the following property file, section, and parameters:

Configuration file: $DLC/properties/AdminServerPlugins.properties
Section: [PluginPolicy.Progress.AdminServer]
Parameter: [port | adminport]

For example:

[PluginPolicy.Progress.AdminServer]
     pluginclasspath=...
     classpath=...
     jvmargs=...
     port= 20999
     adminport= 7999

When the AdminServer is started with the PROADSV command line utility, the listening and communication ports need to be added to the [PluginPolicy.Progress.ProAdsv] section, for example:
[PluginPolicy.Progress.ProAdsv] pluginclasspath=.. classpath=... jvmargs=... port=20999 adminport=7999
Note: When the AdminServer is started as a Service, jvmstart makes use of the[PluginPolicy.Progress.AdminServer] section, otherwise PROADSV uses the [PluginPolicy.Progress.ProAdsv] section. It's best to define these in both sections.
To run more than one AdminServer on a single system, specify a unique -adminport port-number, -port port-number, -mgmtport port-number, and -agentport 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, ORACLE DataServer, or NameServer. The AdminServer must be running in order to use OpenEdge Management, OpenEdge Explorer, or any of the command-line configuration utilities, such as DBMAN.
See in Manage the OpenEdge Database for additional information describing the Unified Broker Framework, including an AdminServer.

Manage the OpenEdge Database