WebSpeed
Installation and
Configuration Guide


Starting WebSpeed Transaction Server and NameServer Instances

The WebSpeed installation includes one sample NameServer and one sample WebSpeed Transaction Server instance. Before you begin to develop or deploy applications on Windows NT, note the following required steps:

  1. The AdminServer must be running. If the AdminServer is not running, you must start it. (See the "Starting the AdminServer" section.)
  2. Start an existing NameServer or create a new NameServer instance. You can create and start a NameServer by using the Progress Explorer; or you can edit the ubroker.properties file to create an instance and then use the NSMAN utility to start the instance. When you configure a NameServer instance, you can set it to start up by default whenever the AdminServer starts.
  3. NOTE: The NameServer can be on any machine in your network, even a UNIX machine.

    If you are using the Progress Explorer, see the online help for information about creating and starting an instance. If you are editing the ubroker.properties file, see the "Editing the ubroker.properties File" section of Configuring WebSpeed On UNIX."

    To start a local instance of the NameServer from the command line, use the following command:

    nsman -name NS1 -start 
    

    where NS1 is the name of the NameServer.

    To start a remote instance of the NameServer from the command line, use the following command:

    nsman -name NS1 -host host-name -port port -user user-name -start 
    

    where host-name is the name of the host machine on which you want the instance to run; port is the port number on the AdminServer; and user-name is the user ID of the system account under which the NameServer will run. If you specify a host name, the Explorer prompts you for a user name (if you do not supply it) and password.

  4. Start an existing WebSpeed Transaction Server or create a new Transaction Server instance. You can create and start a Transaction Server by using the Progress Explorer; or you can edit the ubroker.properties file to create an instance and then use the WTBMAN utility to start the instance. When you configure a Transaction Server instance, you can set it to start up by default whenever the AdminServer starts.
  5. See the Progress Explorer online help for information about creating and starting an instance.

    To start a local instance of the WebSpeed Transaction Server from the command line, use the following command:

    wtbman -name wsbroker1 -start 
    

    where wsbroker1 is the name of the WebSpeed Transaction Server.

    To start a remote instance of the WebSpeed Transaction Server from the command line, use the following command:

    wtbman -name wsbroker1 -host host-name -port port -user user-name -start 
    

    where host-name is the name of the host machine on which you want the instance to run; port is the port number on the AdminServer; and user-name is the user ID of the system account under which the Transaction Server will run. If you specify a host name, the Explorer prompts you for a user name (if you do not supply it) and password.

By using either the Progress Explorer or the command-line utilities, you can also stop a NameServer or WebSpeed Transaction Server instance, check its status, and increase or reduce the number of running WebSpeed Agents. For more information, see the Progress Explorer online help and the "Using the Progress Explorer To Check Status," and "Managing the WebSpeed Transaction Server" sections in this chapter.


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