WebSpeed
Installation and
Configuration Guide
How WebSpeed Components Work Together
In the configuration shown in Figure 2–1, the Web server and the WebSpeed Messenger are on the same machine, as required. The AdminServer, the NameServer, the WebSpeed Broker, and the WebSpeed Agents reside on a second machine.
Figure 2–1: How WebSpeed Processes an HTML Client Request
![]()
In Figure 2–1, you can follow the path of a WebSpeed transaction, beginning with a connection request from an HTML Client and continuing as follows:
- The HTML Client, running in an Internet browser, generates connection requests. Each request is in the form of a URL and is sent to a Web server, which forwards it to a WebSpeed Messenger.
- The WebSpeed Messenger, which is either a CGI program or an ISAPI or NSAPI process (depending on the Web server and the configuration), sends a request to the NameServer for an available WebSpeed Transaction Server that supports the required application service.
- The NameServer selects a WebSpeed Transaction Server, which supports the requested application service, from its pool of Transaction Servers and notifies the WebSpeed Messenger which Transaction Server to use.
- The WebSpeed Messenger forwards the HTML Client’s request to the WebSpeed Transaction Server identified by the NameServer.
- In the WebSpeed Transaction Server, the WebSpeed Broker selects an available WebSpeed Agent from the pool of agents.
- The WebSpeed Agent executes the HTML Client’s request and creates an HTML page that it returns to the WebSpeed Messenger.
- The WebSpeed Messenger passes the HTML page to the Web server, which passes it back to the HTML Client.
All of these components (the Web server, the WebSpeed Messenger, the WebSpeed Broker, the WebSpeed Agents, and the NameServer) can reside on a single physical machine. However, you can also distribute them on separate machines, with the following restrictions:
- The Web server and the WebSpeed Messenger must reside on the same physical machine.
- The NameServer can reside on any machine, but requires an AdminServer.
- The Transaction Server (the WebSpeed Broker and the WebSpeed Agents) requires an AdminServer on its machine. The WebSpeed Broker and the WebSpeed Agents that it supports must reside on the same physical machine. You can have WebSpeed Brokers and Agents on several machines if you purchase multiple Transaction Servers. For example, if you install the Transaction Server on two machines, you can configure a pool of WebSpeed Agents on each machine. Each pool is managed by its own WebSpeed Broker.
See "WebSpeed Configurations," for several ways to distribute the components across a network. You can also distribute the databases over a network. For more information about distributing Progress databases across a network, see the Progress Database Administration Guide and Reference . For information on accessing a non-Progress data source, see the appropriate Progress DataServer guide. When you read these manuals, which describe a typical client/server environment, substitute the term Agent for Client.
Copyright © 2004 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095 |