CSP Gateway Configuration Guide - InterSystems Documentation
CSP Gateway Configuration Guide - InterSystems Documentation
CSP Gateway Configuration Guide - InterSystems Documentation
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Locked-down Apache Environments for Open VMS<br />
For example, to add the file extension xxx to the list of files processed by <strong>CSP</strong>, use:<br />
LoadModule csp_module /apache$root/csp/bin/mod_csp2.exe<br />
AddType application/x-csp csp cls zen xxx<br />
One of the problems with using MIME types to associate types of file with <strong>CSP</strong> is that Apache checks to ensure that the<br />
path to the resource (that is, the hosting directory) physically exists, and returns a file not found error if it does not.<br />
It does not, however, check to ensure that the file requested physically exists – which is appropriate for resources served<br />
by <strong>CSP</strong> since they are served by Caché and are virtual as far as the web server is concerned. The “By MIME type” approach<br />
is therefore only suitable for cases where the application’s path structure can be replicated on the web server.<br />
5.2.2 Operating and Managing the <strong>Gateway</strong> with OpenVMS API and NSD<br />
This connectivity option depends on the <strong>CSP</strong> <strong>Gateway</strong>’s Network Service Daemon (NSD).<br />
1. Start the <strong>CSP</strong> NSD as described in “Operating the Network Service Daemon (NSD)”.<br />
2. Restart SWS/Apache after making changes to its configuration file (HTTPD.CONF).<br />
The order in which SWS/Apache and the NSD are started is unimportant.<br />
3. To access the <strong>CSP</strong> Web <strong>Gateway</strong> Management page, point your browser at one of the following locations. Although<br />
<strong>CSP</strong> pages are served through the higher-performing module (MOD_<strong>CSP</strong>*.EXE), the <strong>CSP</strong> Web <strong>Gateway</strong> Management<br />
page is accessed through the CGI module dedicated to this purpose (NPH-<strong>CSP</strong>CGISYS.EXE).<br />
http://localhost:/csp/bin/Systems/Module.cxw<br />
http://localhost:/csp-bin/nph-<strong>CSP</strong>cgiSys.exe<br />
If you see an Unauthorized User error message, refer to the section on security considerations.<br />
The <strong>CSP</strong> engine is automatically invoked for requested files that contain a .csp, .cls, or .zen extension. For example:<br />
http://localhost:/csp/samples/menu.csp<br />
5.3 Locked-down Apache Environments for Open VMS<br />
The requirement that the <strong>CSP</strong> components be installed within the Apache directory structure for this server has been discussed<br />
in previous sections. Occasionally it is necessary to install the <strong>CSP</strong> <strong>Gateway</strong> components in the appropriate pre-configured<br />
Apache directories in order to avoid HTTP 403 Forbidden error codes being returned on attempting to access <strong>CSP</strong><br />
resources. If this is the case for your installation then proceed as follows:<br />
1. Copy CGI modules to: APACHE$ROOT:[cgi-bin]<br />
copy APACHE$ROOT:[csp.bin]*cgi*.exe;* APACHE$ROOT:[cgi-bin]*.*;*<br />
2. Copy API modules to: APACHE$ROOT:[modules]<br />
copy APACHE$ROOT:[csp.bin]mod*.exe;* APACHE$ROOT:[modules]*.*;*<br />
copy APACHE$ROOT:[csp.bin]cspa*.exe;* APACHE$ROOT:[modules]*.*;*<br />
3. Copy static files and subdirectories in these directories to locations under: APACHE$ROOT:[htdocs]<br />
copy APACHE$ROOT:[csp.samples]*.*;* APACHE$ROOT:[htdocs.csp.samples]*.*;*<br />
copy APACHE$ROOT:[csp.broker]*.*;* APACHE$ROOT:[htdocs.csp.broker]*.*;*<br />
copy APACHE$ROOT:[csp.sys]*.*;* APACHE$ROOT:[htdocs.csp.sys]*.*;*<br />
<strong>CSP</strong> <strong>Gateway</strong> <strong>Configuration</strong> <strong>Guide</strong> 87