The WebSpeed® Transaction Server and WebSpeed Messenger combine to allow an application written in SpeedScript® (the WebSpeed variant of ABL) to use a Web browser as its user interface. Essentially, the WebSpeed Transaction Server becomes an application server for Web browser clients. The Transaction Server runs SpeedScript, which generates HTML pages, and returns these Web pages to Web browser clients through the Messenger in response to Post and Get requests from the clients.
The Messenger runs on a Web server as a CGI or equivalent process (depending on the Web server type) and acts as the gateway and translator between Web requests and responses on the Web server side and the corresponding WebSpeed requests and responses on the Transaction Server side. Like the AppServer, the WebSpeed Transaction Server can have a controlling NameServer configured to provide server-level fault tolerance with multiple Transaction Servers supporting the same application service. The WebSpeed Transaction Server and Messenger each rely on the Unified Broker framework for configuration and administration.
For information on developing SpeedScript applications for WebSpeed deployment, see OpenEdge Getting Started: WebSpeed Essentials and OpenEdge Application Server: Developing WebSpeed Applications.
For information on managing the WebSpeed Transaction Server and WebSpeed Messenger, see Part 4, "WebSpeed Administration." The chapters in Part IV cover all aspects of WebSpeed deployment, run-time management, and security, as well as the management of the WebSpeed Transaction Server and Messenger themselves.
