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:
- 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.
- 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.
- 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:
- Start an AppServer.
- Check and manage the operational status of the AppServer. Management options allow you to reduce (trim) and increase (add) the number of running Application Server processes for this AppServer. For more information on the effects of these options, see the "Specifying the Server Pool Parameters" section. For more information on AppServer status indicators, see the "Checking AppServer Status" section.
- Stop the AppServer.
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:
-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.
-
startStarts 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-startSpecifies the number of additional servers to start.
-trimservers
number-to-trimSpecifies the number of additional servers to trim.
-host
host-nameSpecifies 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-nameSpecifies 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:
- A user name as a simple text string, such as “
mary
,” implies a local user whose user account is defined on the local NT server machine, which is the same machine that runs the AdminServer.- A user name as an explicit local user name, in which the user account is defined on the same machine that runs the AdminServer except the user name explicitly references the local machine domain, for example “
.\mary
”.- A user name as a user account on a specific NT domain. The general format is Domain\User, in which the User is a valid user account defined within the domain and the Domain is any valid NT Server, including the one where the AdminServer is running.
-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):
The following commands start a remote AppServer instance (AS1) after starting a remote controlling NameServer (NS1):
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):
Copyright © 2004 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095 |