The WebSpeed components include:
• WebSpeed Agent—A process that executes the Web objects, performs database
transactions, and dynamically merges data into HTML format. This is the standard
character Progress 4GL client running in batch mode.
• WebSpeed Broker—A process that does the following:
– Registers the WebSpeed Services that it provides to a NameServer for access by one
or more HTML clients. The HTML client runs from within an Internet browser.
– Manages connections between clients and a pool of WebSpeed Agents.
– Maintains the status of each agent in its pool and dynamically scales the number of
agents according to changing demand.
• WebSpeed Messenger—A process that handles the transfer of data between the Web
server and the WebSpeed Agent during a single Web transaction. The Messenger is a CGI
program or an ISAPI or NSAPI process, depending on the Web server and how you plan
to write your applications.
• NameServer—A process that maintains a list of WebSpeed Transaction Servers. The
Transaction Servers register the application services they provide with the NameServer.
The NameServer can then direct client connection requests to a WebSpeed broker that
supports a requested application service. This provides scalability and location
transparency to your applications.
When the Enterprise Transaction Server is installed, the NameServer also performs load
balancing. Load balancing allows you to balance client workload among multiple brokers
that support the same application service (that is, the same set of procedures and
resources).
