WebSpeed
Installation and
Configuration Guide
WebSpeed Configuration Overview
You must perform the following preliminary tasks before you can begin configuring the WebSpeed installation:
- Install the necessary WebSpeed components. For more information about the distribution of resources in the WebSpeed environment, see WebSpeed Configurations."
- Configure the machines involved in the WebSpeed installation. This includes setting the appropriate environment variables and setting up your Web server. For more information about configuring the rest of the your WebSpeed environment, see Before You Install WebSpeed."
Once you complete these preliminary tasks, you can begin to configure the WebSpeed components. The following overall steps take you through this process:
- Start the AdminServer process on each machine by using the PROADSV utility. (See the "Starting the AdminServer" section.)
- Once the AdminServer is running, you can then use the Progress Explorer or a text editor to create and modify NameServer and WebSpeed Transaction Server configurations. Progress stores these configurations in the properties file (
ubroker.properties
) on the machine where you installed the WebSpeed Transaction Server. You can use the Progress Explorer remotely from a Windows 95, Windows 98 or Windows NT 4.0 machine to access configurations installed on a UNIX machine.You can also edit the
ubroker.properties
file manually using a text editor. If you choose to use a text editor, you must have file system access to the file. (See the "Overview Of the ubroker.properties File" section.)You can validate edited NameServer and WebSpeed configurations using the validation utilities (NSCONFIG and WSCONFIG). These utilities must have access to the properties file. (See the "WebSpeed Command-line Utilities" section.)
- Determine if you need to set (or change any preset) WebSpeed environment variables. (See the "Setting Up the WebSpeed Environment" section.)
- Use the NSMAN utility (or the Progress Explorer remotely) to start up a NameServer instance that you configured to coordinate client access to one or more WebSpeed Transaction Server instances on your network. After the NameServer has started, use the WTBMAN utility (or the Progress Explorer remotely) to start up each WebSpeed Transaction Server instance controlled by that NameServer. (See the "Starting WebSpeed Transaction Server and NameServer Instances" section.)
After a WebSpeed Transaction Server starts up, it registers its location and the Application Services it supports with its controlling NameServer.
- Set up the WebSpeed Messenger on your Web server. (See the "Setting Up WebSpeed On the Web Server Machine" section.)
- At any time after Step 5, you can validate that the AdminServer, the NameServer, and the WebSpeed Transaction Server are running and test the configuration to confirm that you have set up WebSpeed correctly. You perform this validation by using the WebSpeed command-line utilities, the Progress Explorer (remotely, from a Windows 95, Windows 98, or Windows NT 4.0 machine), or the WebSpeed Messenger Administration (WSMAdmin) page in a browser. (See the "Testing Your Configuration" section for more information.)
- You can shut down the AdminServer process at any time on the WebSpeed machine. If you shut down the AdminServer while there are NameServer and WebSpeed Transaction Server instances still running, those instances are shut down as well.
Copyright © 2004 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095 |