The WebSpeed Transaction Server consists of the processes that handle the server-side activity of your WebSpeed applications:
WebSpeed agent — An application process that can execute Web objects, perform database transactions, and dynamically merge data into HTML format. The agent is the standard character ABL client running in batch mode. An AppServer agent is a single AVM instance running on the AppServer.
Note: The agent process is inherently stateless. This means that the agent is only busy when a request is being processed. It will be idle at all other times.
WebSpeed broker — An application that can do the following:
Register with a NameServer the application services that it provides to fulfill requests from HTML clients.
For information on running WebSpeed from a client other than the HTML client (for example, an ActiveX page or a Java application), see the Progress Communities WebSpeed Forum:
Manage connections between clients and a pool of WebSpeed Agents.
Maintain the status of each agent in its pool and dynamically scale the number of agents according to changing demand.
Note: If you start a WebSpeed broker without specifying a username, the Broker inherits the account that the AdminServer is using. This is generally the system account, which might not have access to network drives.
WebSpeed agent — An application process that can execute Web objects, perform database transactions, and dynamically merge data into HTML format. The agent is the standard character ABL client running in batch mode. An AppServer agent is a single AVM instance running on the AppServer.