5. Configuring the OpenROAD Server : Server Component and Gatekeeper Configuration : How You Configure the OpenROAD Server .NET Client Gatekeeper2 : OpenROAD ASP.NET Gatekeeper2
 
Share this page                  
OpenROAD ASP.NET Gatekeeper2
You may install the Ca.OpenROAD.dll and Ca.OpenROAD.Orrsolib.dll assembly files in the Global Assembly Cache using gacutil. Or you can drop both of these DLLs into the bin subdirectory of your ASP.NET application root ("httpApp1\bin" in this example).
This gatekeeper (sources: OpenROADGatekeeper.ashx.cs, OpenROADGatekeeper.ashx) provides an out-of-the-box experience through using just the source files and configuration options, which you can set in the web.config file. The files are contained in a subdirectory, which you can copy directly into an IIS webapp application subdirectory. The new subdirectory is used to keep the old source files for reference.
This gatekeeper no longer uses global.asax and global.asax.cs. The whole C# code is contained in OpenROADGatekeeper.ashx.cs. The gatekeeper is referenced by a URL that refers to the OpenROADGatekeeper.ashx file provided, for example:
http://localhost/openroad/OpenROADGatekeeper.ashx
You are, of course, free to rename this file. If you rename OpenROADGatekeeper.ashx.cs, then you should update the name in the *.ashx file accordingly.
The gatekeeper requires .NET Framework version 2.0 or higher (such as 3.5), which you can download from MSDN. The registered application (virtual directory) in IIS must be configured accordingly to use this version. You do this on the "ASP.NET" tab of the "Properties" for the application. There you can choose between versions 1.1 and 2.0. Use 2.0—this setting also works with newer .NET framework versions (such as 3.5).
The gatekeeper should work out of the box, that is, without requirements to change the code.
The default configuration allows access to all SCPs in all OpenROAD Server applications.