CSP Gateway Configuration Guide - InterSystems Documentation

Apache Servers
4.3.4.1 Operating and Managing the Gateway with Apache API and NSD
This connectivity option depends on the CSP Gateway’s Network Service Daemon (NSD).
1. Start the CSP NSD as described in Operating the Network Service Daemon.
2. Restart Apache after making changes to its configuration (httpd.conf).
The order in which Apache and the NSD are started is unimportant.
3. To access the CSP Web Gateway Management page, point your browser at one of the following locations.
Although CSP pages are served through the higher-performing module (mod_csp.dll), the CSP Web Gateway Management
page is accessed through the CGI module dedicated to this purpose (nph-CSPcgiSys.exe).
http://localhost:/csp/bin/Systems/Module.cxw
http://localhost:/csp-bin/nph-CSPcgiSys.exe
If you see an Unauthorized User error message, refer to the section on security considerations.
The CSP engine is automatically invoked for requested files that contain a .csp, .cls, or .zen extension. For example:
http://localhost:/csp/samples/menu.csp
4.3.5 Option 4: Apache and ISAPI Modules (CSPms.dll)
This connectivity option is superseded by the stand-alone API modules described in Option 1 and should not be used. It is
documented here as a reference for legacy systems that have used it in the past.
The Apache Group provides a module that attempts to emulate Microsoft’s ISAPI interface. If Apache is configured to use
this module then ISAPI extensions may be run. However, there are significant differences between the Apache Group
ISAPI interface and Microsoft’s original. The most troublesome feature of the Apache ISAPI module is that it unloads its
ISAPI extensions (DLLs) after servicing each and every request. This behavior is unacceptable for CSP because the CSP
Gateway relies on its ISAPI DLLs remaining in memory in order for it to manage a persistent pool of connections to Caché.
The modified ISAPI module supplied with CSP allows the CSP Gateway’s ISAPI extensions to remain loaded between
requests. The modifications only affect the Gateway’s ISAPI DLLs; all other ISAPI DLLs are subject to the original Apache
Group’s functionality.
4.3.5.1 Rebuilding the Apache Executable
1. Upgrade the Apache ISAPI module (mod_isapi.c)
Overwrite the Apache Group’s ISAPI module with the version contained in the CSP distribution:
C:\Program Files\Apache Group\Apache\src\os\win32\mod_isapi.c
2. Rebuild the Apache executable
In order to perform this step you need version 5.0 (or later) of the Microsoft C Compiler (Microsoft Visual C++).
Change to the following directory:
C:\Program Files\Apache Group\Apache\src\os\win32\mod_isapi.c
Build Apache with:
nmake /f Makefile.nt installr INSTDIR=d:\progra~1\apache~1\apache
You can safely ignore the many warning messages that the build process displays.
3. Runtime configuration
CSP Gateway Configuration Guide 97