The HttpSrvr ISAPI library is an alternative to the socketserver as a communications handler. It provides HTTP and HTTPS support for client to application server communications. It is necessarily slower than the socketserver due to the overheads imposed by the HTTP / HTTPS protocols. If used, it must be installed as an IIS application.

The HttpSrvr dll is installed by the installation program into the directory:

<install dir>\scripts\

Depending on your version the HttpSrvr dll may also be installed into bpcsxsrvr instead. This is the later and preferred directory, although these notes still illustrate "scripts". (NOTE: An error has been reported in the V6256 installer or application set that suggests that the application will attempt to work with scripts although the installer sets up bpcsxsrvr. Until this error is traced and fixed, these instructions remain correct exactly is written. It might be wise to remove the automatocally created HTTPSrvr.dll copied into the bpcsxsrvr directory, or rename the virtual directory "scripts". We will advise when this problem is rectified.)

You will need to move it to the appropriate directory on your IIS server. The client is set, by default, to assume the scripts directory so we recommend you use a virtual directory called scripts to house the HttpSrvr dll (which will make it simpler for clients to connect).

(Skip if using IIS5) If your IIS server does not have a scripts directory (IIS6 and above) you will need to create one. Do this by creating an appropriate directory in a folder of your choosing and map that directory to IIS using the name “scripts” as the virtual directory name. Our advice is that you do NOT create this directory as a subdirectory of the wwwroot directory as it will require special access rights. We also advise that you do NOT simply map the installation folder to the scripts directory as future patches may directly update the installation directory, effectively instantly setting the new patched library to “live” mode.
(Skip if using IIS5) To map the newly created folder to your web server right click on the folder and choose properties from the context menu. On the properties window select the “web sharing” tab. In the “web sharing” tab select “Share this folder”.

A window will open, enter “Scripts” in the Alias field. Tick “Read” and ensure the other check boxes are unticked, and select the “Execute (include scripts)” radio option and choose “Ok”.

Select OK again on the folder properties window to close the window.
Copy the HttpSrvr.dll to your scripts directory.
Open the IIS Manager (or right click on My Computer) and expand the “Internet Information Services”/”Web Sites”/”Default Web Site” tree.
Right click on the “Scripts” object and choose “properties”.
On the properties window select the “Virtual Directory Tab” and enter an Application Pool name:
Still in the properties window, select the “Directory Security” tab and select the edit button in the “Authentication and access control”:
On the Authentication methods tab, tick “Enable anonymous access” and untick any other options. In setting the anonymous authentication user, you can do one of three things: leave the user name as the built-in anonymous user account (in which case you will have to grant access to the application server to the anonymous user account) or create a dedicated local service account made for the purpose (eg. RiskManager Services - in which case you will have to create it with service execution rights and grant access to the application server exe - see below) or as is our suggestion use the builtin local computer administrator account as the activation Id. It is preferable to either use the local admin account or a dedicated application services account that you have created specially for the purpose. There are good arguments for all options. The principal advantage of the configuration illustrated is that the socket server access method and the httpsrvr access method will share the Application server activation space, and the application server will show on the administration console system tray when activated. Illustrated is our suggested configuration. By using the local administrator you can keep the application pool operating under the lower network service account. If you use the local administrator as the anonymous activation account, you should not have any other libraries in the script directory other than the HttpSrvr library (and irrespective that is probably the preferred scenario). Later in these instructions we illustrate configuring application server access using a dedicated RiskManager Services account. You will not be able to use the builtin local system account as you need the password at some points to configure it. After entering your settings, Select “OK” to close the window.
On the IIS manager, expand the Application Pools tree and right click on the icon matching the application pool name you created in step 6. Select properties from the menu.
On the properties window tick the Recycling check box on the Recycling tab and set the parameters for Recycling to a value that makes sense (or accept the default). The recycling time should be long, but at least every 1 to 3 days, or at a fixed time each day or night when users are unlikely to be accessing the application.
Select the Performance tab and ensure that the “Web Garden” has a maximum number of processes set to 1.
Select ok to close the properties window.
On the IIS Manager select the “Web Service Extensions” tree node and in the right hand panel select “All Unknown ISAPI Extensions” and select the “Allow” button.
Finally select the “Default Web Site” tree node in the IIS Manager and stop and restart the web site using the stop and play buttons or the stop and start options in the context menu that appears when you right click the icon.
Next we have to set the execution parameters of the RiskManager DCom server to allow the HTTPSrvr to access it. This step is not required if using socketserver. Using windows explorer, navigate to the directory in which BPC RiskManager Dataserver was installed. Usually this will be:

C:\Program Files\BishopPhillips\BPCRiskManager\ApplicationFiles (But it may be a little different depending on the version of BPC RiskManager you are installing).
- Locate the executable file “RiskManagerDataserver.exe”
- Double click on the file to start the application server.
- A green disk should appear in the system tray.
- Double click on the green disk and the BPC RiskManager DataServer configuration window will open, and the Dataserver will silently register itself as a DCom service.
- Choose “End Process” and slect “Ok” in the warning window that opens. The application will close and the.green disk will disappear.
Open the Component Services Manager. This may be found in a few places. On W2003 it may be found by Selecting the Start Button and from the programs menu choose “Administration Tools/Component Services”
Expand the tree in the left panel by expanding “Component Services” / “Computers” / “My Computer” / “DCom Components”
Locate the “RiskManagerServices Object” in either the right panel or the list of nodes below the DCom Components and right click on it and choose the properties option to open the properties window.
On the Properties window for the component select the “General” tab and ensure the Authentication level is set to default.
On the Security tab select “customize” for both the “Launch and activation permissions” and the “Access Permissions”.
Select the Edit button for the Launch and Activation permissions and the permissions window will open. Add the user you chose in step 8. In our example we have used the local administrator account, but we have also shown the window with a dedicated “specially created” “RiskManager Service Account” (which must have the similar rights to a local service account when created). In either case grant all rights to the chosen activation account. If you are using the local administrator account, be sure to add that account and not a network administration account.
If you are using the builtin administration account, you can skip this step. Select the Edit button for the “Access Permissions” and grant the account used in step 8 access to the component by clicking on the “add” button and granting all rights.as shown.. When completed, close the window.
Select the identity tab on the RiskManager services property window and select the “Interactive user” radio button. Close the property window
Close the component services manager window.