WebSpeed
Installation and
Configuration Guide
Multiple LAN Development Environment
Some development environments include several local area networks (LANs). For example, a company’s intranet might include two LANs—a Sales LAN and a Manufacturing LAN.
The common Progress administration architecture includes a method for connecting NameServers to other NameServers. When a NameServer receives a request for an application service, it checks to see whether any of the WebSpeed Brokers registered with it supports that application service. If none of its registered brokers supports that application service, the NameServer passes the request to other NameServers that it knows about.
Using this capability, you can link Progress installations across the LANs that make up a wide area network. Figure 3–4 shows the products installed on a multiple LAN configuration.
Figure 3–4: Multiple LAN Development Environment
![]()
In this configuration, the NameServer machine, Saturn, is the central communication point that routes requests to the WebSpeed Transaction Servers on both LANs. Requests start from workstations, like Prometheus (which has ProVision Plus installed on it). A workstation passes the request to the Web server machine, Pandora, which has the WebSpeed Messenger installed. The Messenger asks the NameServer on Saturn to find a WebSpeed Transaction Server that can handle the request, by specifying an application service with the WService parameter.
Calypso and Hyperion both have the Transaction Server installed. The Transaction Servers are registered with Saturn’s NameServer. Saturn’s NameServer checks its list of registered Transaction Servers to see whether one supports the application service that can handle the request from Pandora’s Messenger. If one of them does, the NameServer passes its location back to the Messenger and the request is completed as shown in the flow diagram in the "How WebSpeed Components Work Together" section of Overview Of the WebSpeed Architecture."
The Transaction Server installed on Titan includes a NameServer. You can register this NameServer with Saturn’s NameServer. If the WebSpeed Brokers on Calypso or Hyperion do not support the correct application service, Saturn’s NameServer passes the request to the NameServer on Titan to see whether the Broker registered with it supports that application service. If the Broker on Titan does support the application service, Titan’s NameServer passes its location to Pandora’s Messenger. Then the request is completed as normal.
For more information on how this works, see the “Using NameServer Neighbors” section of the “Configuring Progress Unified Broker Products” chapter in the Progress Installation and Configuration Guide Version 9 for Windows .
Note that there are only two machines with data sources in this configuration—Hyperion, on the NT side, and Atlas, on the UNIX side. Because the WebSpeed Transaction Server does not come with a database, you must install the Enterprise Database or the appropriate DataServer to connect to your non-Progress database. The WebSpeed Agents on any of the Transaction Server machines in the configuration can access either data source.
To set up this configuration, follow these general steps:
- Install a Web server on Pandora.
- Perform a Typical Installation of the NameServer on Saturn.
- Perform Typical Installations of the WebSpeed Transaction Server on Calypso, Hyperion, and Titan.
- Perform a Typical Installation of the WebSpeed Messenger on Pandora.
- Copy the static HTML and GIF files of the
DLC/progress/webspeed
directory on one of the Transaction Server machines to your Web server’s/docroot/webspeed
directory on Pandora. These are the files for the WebSpeed WebTools that must reside with your Web server.- Perform Typical Installations of ProVision Plus or the WebSpeed Workshop on Prometheus and your other workstations, according to your development needs.
- Install the appropriate data source components on Hyperion and Atlas. This depends on what you use as your data source:
Beyond the Basic Installation
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. See the "Understanding the NameServer’s Load Balancing Option" section in "Configuring WebSpeed On Windows," and the “Configuring Progress Unified Broker Products” chapter in the Progress Installation and Configuration Guide Version 9 for Windows .
If you need access to any of the DataServers for your applications, you can add them by performing a Complete Installation of the WebSpeed Transaction Server on those machines and ProVision Plus on your workstations.
Copyright © 2004 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095 |