Building Distributed
Applications
Using the Progress AppServer


Summary of Management Tasks

This section summarize the basic management tasks that are available to maintain existing AppServer configurations. They are described with reference to the command-line utilities, but you can also accomplish most of these tasks, except running the AdminServer, using the Progress Explorer.

Table 3–2 describes the utilities (in addition to the Progress Explorer tool) that Progress provides to help configure and manage a Progress AppServer installation, listed generally in order by task.

Table 3–2: AppServer Utilities 
Utility
Execution
Location
Description
PROADSV
Local to the AppServer installation
Starts, stops, and queries status for the AdminServer on UNIX. On NT, you start the AdminServer as an NT service using the Services applet in the Control Panel.
NSCONFIG
Local to the AppServer installation files
Validates the syntax of NameServer configurations in the ubroker.properties file. (Never needed if you always use the Progress Explorer GUI.)
ASCONFIG
Local to the AppServer installation files
Validates the syntax of AppServer configurations in the ubroker.properties file. (Never needed if you always use the Progress Explorer GUI.)
NSMAN
Local or remote to the NameServer machine
Starts, stops, and queries status for a NameServer.
ASBMAN
Local or remote to the AppServer installation
Starts, stops, adds Application Server processes, trims Application Server processes, and queries status for an AppServer instance and its Application Broker.

For more information on the NameServer and NSMAN utility, and the AdminServer and PROADSV utility, see the Progress Installation and Configuration Guide Version 9 for Windows or the Progress Installation and Configuration Guide Version 9 for UNIX.

Table 3–3 lists sample command-line utility syntax used to:


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