Building Distributed
Applications
Using the Progress AppServer


Starting and Managing an AppServer with the Management Utilities

You can use the command-line management utilities on Windows or UNIX platforms to start local AppServer instances and remote AppServer instances running on any platform.

To start an AppServer instance:

  1. Using the NSMAN utility, start each NameServer that you need to support your AppServer instance. For more information, see the Progress Installation and Configuration Guide Version 9 for Windows or the Progress Installation and Configuration Guide Version 9 for UNIX.
  2. Start each Progress Database or DataServer that your application requires. For more information on starting databases and DataServers, see the Progress Installation and Configuration Guide Version 9 for Windows or the Progress Installation and Configuration Guide Version 9 for UNIX.
  3. Using the ASBMAN utility, start the AppServer instance.
Using the ASBMAN Utility

The ASBMAN utility runs on both Windows and UNIX platforms. It allows you to invoke the following management functions on a local or remote AppServer instance:

Unlike the Progress Explorer, the ASBMAN utility has no mechanism for viewing log files or deleting configured AppServer instances. If you want to view the AppServer log file or delete the AppServer instance, you must do it manually using operating system commands. To delete the AppServer, you must remove the entry for this AppServer instance in the AppServer properties file or use the Progress Explorer. For more information on managing log files, see the Progress Installation and Configuration Guide Version 9 for Windows or the Progress Installation and Configuration Guide Version 9 for UNIX. For more information on accessing the AppServer properties file, see the "Configuring an AppServer Using the Properties File" section.

NOTE: Before you can delete an AppServer instance, you must stop the AppServer.

This is the syntax to invoke the ASBMAN utility:

SYNTAX
asbman
  {
      { -name AppServer-name
        {
             -kill
           | -start
           | -stop
           | -query
           | -addservers number-to-start
           | -trimservers number-to-trim
        }
        [
             -host host-name -user user-name
           | -user user-name
        ]
        [ -port port-number ]
      }
    | -help
  } 

-name AppServer-name

This parameter is required. It specifies the name of an AppServer.

-kill

Stops and removes the AppServer from memory, no matter what it is doing.

-start

Starts an AppServer.

-stop

Tells the NameServer to stop itself.

NOTE: The AppServer stops only after completing any active client requests.

-query

Queries an AppServer for its status.

-addservers number-to-start

Specifies the number of additional servers to start.

-trimservers number-to-trim

Specifies the number of additional servers to trim.

-host host-name

Specifies the name of the machine where the AdminServer is running. If a host name is not specified, it defaults to the local host name.

-user user-name

Specifies a user name and prompts for a password. A user name and password are required only when you use the -host parameter and specify a remote host name. If you specify a remote host name with the -host parameter, but do not specify a user name with the -user parameter, you receive a prompt for a user name and password.

Windows NT supports three different formats for user-name:

-port port-number

Specifies the port number of the machine on which the AdminServer is running. If a port number is not specified, it defaults to 20931.

-help

Displays command-line help.

Examples

The following commands start a local AppServer instance (AS1) after starting the local controlling NameServer (NS1):

nsman -name NS1 -start
asbman -name AS1 -start 

The following commands start a remote AppServer instance (AS1) after starting a remote controlling NameServer (NS1):

nsman -name NS1 -host nsserve -port 20950 -user daniel -start
asbman -name AS1 -host asserve -port 20950 -user daniel -start 

Note that the AppServer and controlling NameServer are on different hosts and happen to use the same TCP/IP port number to access the AdminServer on each host. If you specify a host, the Explorer prompts always prompts for a user name (if necessary) and password. In this example, the commands specify the user name and prompt only for the password.

The following commands stop a local AppServer instance (AS1) and its controlling NameServer instance (NS1):

asbman -name AS1 -stop 
nsman -name NS1 -stop  


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