Try OpenEdge Now
skip to main content
WebSpeed Essentials
Configuring WebSpeed : Configuring a WebSpeed Messenger

Configuring a WebSpeed Messenger

The WebSpeed Transaction Server and WebSpeed Messenger combine to allow an application written in SpeedScript® (the WebSpeed variant of the 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 the 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.
Note: There is also a Messenger that works with Microsoft's Active Server Pages, the WSASP Messenger. Using the WSASP Messenger, you can call out of an Active Server Page to a WebSpeed application.
For information on developing SpeedScript applications for WebSpeed deployment, see OpenEdge Application Server: Developing WebSpeed Applications.
* Configuring a Messenger-only installation
* Installing the Messenger executable
* Editing the Netscape Web server configuration file
* Where to place the Messenger executable file
* Managing the WebSpeed Messenger