Integrating Web Servers
HTTP transport in OpenROAD allows HTTP communications between an OpenROAD client and the OpenROAD Server. This capability allows thin client OpenROAD applications to run through a firewall or across domains where trust relationships between machines is not possible. This integration requires the addition of an HTTP web server to the configuration. You can use any of the major HTTP servers including Microsoft Internet Information Server (IIS), Apache, and so on.
You can implement security on the web server like any other web application, and additional security can also be provided in the application itself.
A simple “gatekeeper” application is used to forward requests from the client to the OpenROAD Server. Sample applications are located in the Ingres installation folders with instructions on how to customize and deploy these interfaces.
The OpenROAD .NET Gatekeeper instructions are located in:
%II_SYSTEM%\ingres\ordotnet\Gatekeeper2\readme.txt
The OpenROAD Java Gatekeeper instructions are located in:
%II_SYSTEM%\ingres\orjava\Gatekeeper2\readme.txt
Note: HTTP transport is required for mobile applications because Windows CE and Windows Mobile do not support Distributed COM (DCOM)-based communications.
For more information about HTTP transport, see
HTTP Transport.