Install Socket Server as a Service And HTTPSrvr as an ISAPI library
The RiskManager Dataserver (the application server) is a Windows DCOM server. It is registered and operates on the application server computer but requires a local listener component to listen for RiskManager Dataserver requests, launch the Dataserver object if necessary and relay the data requests and response between a Client Programme and the Dataserver. The RiskManager client application connects to the Risk Manager Dataserver using one or both of two methods:
- The Borland Socket Server that connects the client to the Application Server Computer via port 211, and/or
- The ISAPI library called HTTPSrvr that connects the client to the Application Computer Server via either HTTP (port 80) or HTTPS (port 443).
As the HTTPSrvr runs as part of the IIS server it represents a level of architectural complexity beyond the operation of the raw socket server solution. Where the HTTPSrvr is used, it is strongly recommended that you also install and run the SocketServer as it provides the simplest possible method of launching the RM dataserver and therefore a reliable method of isolating network and DCom issues because a system administrator can use a RiskManager client on the local area network to connect to the RiskManager Dataserver bi-passing the IIS dependent components.
Both the Socket Server and the HTTPSrvr must be run on the network server running the Risk Manager DataServer application server. It is theoretically possible to run them remotely from the application server, but we have not tested such a configuration.