The following figure shows the WebSpeed architecture. The dotted arrows and borders show optional interactions and components.
Figure 6. WebSpeed architecture
A WebSpeed application can include the following components, potentially distributed on the following machines shown in the above figure:
1. HTML client — This is typically a Web browser that provides the user interface and run-time engine for the HTML application.
2. WebSpeed Messenger — A process that runs on a Web server and handles the transfer of data between the Web server and the WebSpeed agent during a single Web transaction.
3. NameServer — A process that accepts a client request for connection to a WebSpeed Transaction Server and directs that request to the appropriate Transaction Server instance. This is optional depending on the Transaction Server configuration. If your application service is supported by multiple WebSpeed Transaction Server instances, you must use the NameServer for effective connection management.
4. WebSpeed Transaction Server — A core product set that contains the following components:
WebSpeed agent — A process that executes ABL procedures in response to Web requests from a WebSpeed Messenger and returns results as HTML. Thus, a WebSpeed agent is essentially an OpenEdge session with its user interface replaced by HTML that can present the user interface in a Web browser.
WebSpeed broker — The process that manages connection requests from a WebSpeed Messenger and its pool of WebSpeed agents (agent pool).
A WebSpeed Transaction Server instance:
Is one WebSpeed broker and the pool of WebSpeed agents that it manages.
Has a specified configuration and makes a well-defined set of ABL procedures (SpeedScript Web objects) available as an application service for execution by client applications.
Can have any number of WebSpeed agents to service remote procedure requests from any number of Web browser applications, depending on licensing and available resources.
The WebSpeed Messenger is the point of contact for a given WebSpeed application service, which can be supported by one or more WebSpeed Transaction Server instances. Each WebSpeed application service must have at least one WebSpeed Messenger instance configured for it on a Web server.
A WebSpeed Transaction Server installation is the WebSpeed application service component of an OpenEdge Application Server environment that is installed on a particular machine. Depending on your licensing and resources, you can configure and run multiple WebSpeed Transaction Server instances for a given WebSpeed installation.
A WebSpeed Messenger installation is the Web server component of an OpenEdge Application Server environment that is installed on a particular machine. You can configure and run multiple Messenger instances for a given WebSpeed Messenger installation.
The AdminServer is the core of the Unified Broker framework used to manage the WebSpeed Transaction Server and most of its related components. For more information on the framework, see Unified Broker framework.
WebSpeed agent — A process that executes ABL procedures in response to Web requests from a WebSpeed Messenger and returns results as HTML. Thus, a WebSpeed agent is essentially an OpenEdge session with its user interface replaced by HTML that can present the user interface in a Web browser.