Web Connection User's Guide

Web Server Interface

In order to run your Web application, you must also be running a Hypertext Transfer Protocol (HTTP) server that can run server programs in response to client requests. The HTTP server relays requests to the VisualAge application through a Web server application interface. There are several interfaces through which Web servers can access a Web Connection application (for more information about these interfaces, see Setting up the Web Connection server interface):

The Servlet interface offers several advantages over the other Web Server interfaces:

The Web Connection feature provides a Web Server Interface (WSI) module for each of the supported interfaces. For CGI, the interface is through a stand-alone executable program; for the others, it is through a dynamically loaded shared library. The interface module handles all interaction with the VisualAge application, which stays up and running all the time. This arrangement provides several advantages:

On your Web server, you must set up the appropriate interface module so that it is accessible to your HTTP server software. Web clients can then access your VisualAge application by submitting requests to the Web server, which then calls the appropriate interface module. The interface module then relays the client request to the VisualAge application.

The VisualAge application receives these requests, and returns the results, by way of the WSI server, a process running within the VisualAge image.


[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]