WebSpeed
Installation and
Configuration Guide
Development and Deployment In a Shared Configuration
When a company develops its own applications, it can have networks that are used for development, testing, and deployment simultaneously. Figure 3–6 shows this type of configuration.
NOTE: The WebSpeed Broker and the WebSpeed Agents it controls are collectively referred to as the WebSpeed Transaction Server in this figure.Figure 3–6: Development and Deployment In a Shared Configuration
![]()
In this configuration, the dedicated Web server machine, Neptune, has two Web servers installed. One Web server handles the development workload, and the other handles the deployment workload. This allows the developers to experiment with the environment without bringing down the deployment side. Each of the Web servers requires its own WebSpeed Messenger, but only the development Web server needs the WebSpeed WebTools.
On the development side, the Messenger routes requests to the NameServer on Triton. Triton’s NameServer only has the WebSpeed Transaction Servers on Proteus registered, so it looks there for a Transaction Server to handle the request. Proteus has the WebSpeed Enterprise Transaction Server and either the Enterprise Database or a non-Progress data source installed on it.
On the deployment side, that Messenger routes requests to the NameServer on Galatea. Galatea has the WebSpeed Enterprise Transaction Server installed. The deployment side uses a dedicated machine, Nereid, to hold its data source (that is the Enterprise Database or a non-Progress data source).
To set up this configuration, follow these general steps:
- Install two copies of your Web server on Neptune.
- Perform a Typical Installation of the Enterprise NameServer on Triton.
- Perform a Typical Installation of the WebSpeed Enterprise Transaction Server on Proteus.
- Perform a Typical Installation of the WebSpeed Messenger on Neptune using the development Web server’s Document Root directory and scripts path.
- Copy the static HTML and GIF files of the
DLC/progress/webspeed
directory on Proteus to the Development Web server’s/docroot/webspeed
directory on Neptune. These are the files for the WebSpeed WebTools that must reside with your Web server.- Configure the Development Web server’s WebSpeed Messenger on Neptune to pass requests to Triton’s NameServer.
- Perform Typical Installations of ProVision Plus or the WebSpeed Workshop on Thalassa and your other workstations, according to your development needs.
- Perform a Typical Installation of the WebSpeed Messenger on Neptune using the deployment Web server’s Document Root directory and scripts path.
- Perform a Typical Installation of the WebSpeed Enterprise Transaction Server on Galatea.
- Configure the Deployment Web server’s WebSpeed Messenger on Neptune to pass requests to Galatea’s NameServer.
- Install the appropriate data source components on Proteus and Nereid. This depends on what you are planning to use as your data source:
- Install your r-code on Galatea.
- Copy any Java applet, static HTML, and GIF files that your applications need to the deployment Web server’s
/docroot/webspeed
directory on Neptune.Beyond the Basic Installation
As described, this configuration uses the components for a heavy load system. If you expect a light load on the network, you might consider installing the WebSpeed Transaction Server and Workgroup Database instead of the Enterprise Transaction Server and Enterprise Database. The WebSpeed Transaction Server can handle up to 50 WebSpeed Agents. The Workgroup Database can handle up to 65 connections.
You can expand the capacity of either side of this configuration by adding new server machines with the same products installed. Register the WebSpeed Transaction Servers on the new machines with the NameServer that is handling the Transaction Servers for that side.
When you expect heavy loads on your network or want to increase its fault tolerance, you might want to use the load balancing capability of the Enterprise NameServer. If you deploy several WebSpeed Transaction Servers that support the same application service, you can use load balancing to control how the load is spread over them.
If you need access to any of the DataServers for your applications, you can add them by performing Complete Installations of the WebSpeed Enterprise Transaction Server on the appropriate machines and ProVision Plus on your workstations.
Copyright © 2004 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095 |