ASP.NET HTTP Gatekeeper
The OpenROAD HTTP Transport option lets you use HTTP as an alternative to DCOM when communicating with the OpenROAD Server. When a client specifies "http" as the Routing parameter in the RemoteServer Initiate method, that RemoteServer instance will transform its normal DCOM calls into HTTP messages and post them to the HTTP URL specified in the Location parameter.
This requires the web server application listening at that URL to be able to recognize those HTTP messages and transform them back into DCOM calls to the OpenROAD Server, and then transform the DCOM responses into HTTP response messages. We call this application a "gatekeeper" because it serves two crucial functions:
Message Transformation
The gatekeeper application converts HTTP requests into DCOM calls, and converts DCOM return values into HTTP responses.
Security
The gatekeeper application decides which clients are allowed to make calls, and which 4GL SCPs they are permitted to call.
The message transformation process is the same for all applications, and we have provided generic code that handles this. But the security decisions are unique to each customer and each application, so we can only provide examples and a starting template. You must customize the gatekeeper application to meet your own security requirements.
%II_SYSTEM%\ingres\ordotnet
This directory contains source files for a sample ASP.NET gatekeeper application. You can use the files as-is to produce a simple "helloworld" demo of the HTTP capability. You can also use them as the starting point for real HTTP gatekeeper applications.