CSP Gateway Configuration Guide - InterSystems Documentation

More documents

Recommendations

Info

Web Servers for Microsoft Windows 4.2.10.4 Operating and Managing the Gateway This connectivity option depends on the CSP Gateway’s Network Service Daemon (NSD). 1. Start the CSP NSD as described in the section dedicated to this service. Although CSP pages are served through the higher-performing ISAPI module (CSPcms.dll), the Gateway’s management suite is accessed through the CGI module dedicated to this purpose (nph-CSPcgiSys.exe). To access the CSP Gateway’s Systems Management suite, point your browser at one of the following locations: http:///csp/bin/Systems/Module.cxw http:///csp-bin/nph-CSPcgiSys The CSP engine is automatically invoked for requested files that contain a .csp, .cls, or .zen extension. For example: http:///csp/samples/menu.csp If you see an unauthorized user error message, refer to the section “CSP Gateway and Security.” 4.2.11 Restarting IIS This section describes what happens when IIS is restarted via the various control panels: Most configuration changes can be made in real-time to an active IIS installation. However, the Internet Information Services (IIS) Manager control panel provides stop, start, and restart options. These are useful for the refreshing the Web server configuration but does not result in an active Gateway installation being reinitialized (the Gateway DLLs is not reloaded). As with previous versions of IIS, if you want to force IIS to restart, so that the Gateway modules are reloaded, then you have to restart the World Wide Web Publishing service via the main Windows Services control panel. 4.2.12 Troubleshooting This section describes problems that commonly occur in configuring third-party modules (both Native and ISAPI) to work with IIS. The most common problem likely to be encountered is that, after reconfiguring, requests to IIS fail with the following error: Service Unavailable HTTP Error 503. The service is unavailable. This usually indicates that the default Application Pool has terminated. 1. Open the Internet Information Services (IIS) Manager window. 2. In the left panel expand the top level to reveal the Application Pools section. [MACHINE_NAME] ([machine_name]\[user_name]) Appliation Pools 3. Check that the Default Application Pool (DefaultAppPool), or whatever application pool your server is configured to use, is marked with a Status of Started. 4. Restart the application pool if necessary (using the options in the right panel). 5. If problems persist, look for clues in the main Windows Event Log: the Applications section. In particular, check for the following error message: Failed to find the RegisterModule entrypoint in the module DLL C:\inetpub\CSPGateway\CSPms.dll. The data is the error. 90 CSP Gateway Configuration Guide
Apache Servers This, for example, indicates that the version of Gateway DLLs that you are using do not implement the Native Modules interface. Either obtain later DLLs from InterSystems or configure the Gateway to work through the conventional ISAPI interface. As with all software, restarting often clears transient problems: To completely restart IIS, restart the World Wide Web Publishing service via the main Windows Services control panel. 4.3 Apache Servers Apache is supplied by the Apache Group and can be downloaded free of charge from:http://www.apache.org. The complete source code to Apache is available from Apache for download together with clear instructions for building the server. To build Apache under Windows, you must have the Microsoft C compiler (Visual C++) version 5.0 (or later). Instead of building the server yourself, you can instead download prebuilt kits for Windows. The prebuilt kits are, generally, a few builds behind the latest Apache source code. This guide assumes that the CSP Gateway components are installed in the following directory: C:\Program Files\Apache Group\Apache\CSPGateway It is assumed that the Web server is installed under: C:\Program Files\Apache Group\Apache\ If the layout is different on your system, amend the configuration directives in the following sections, as appropriate. First follow the directions in the section Installing with Apache Servers (All Connectivity Options), then follow the directions in one of connectivity option sections that follow. The CGI-based approach is the easiest to get started with. On the other hand, the solutions based on dynamically-linked modules perform better. Note that the ISAPI-based solution requires the Apache server to be rebuilt with a modified version of the ISAPI module (mod_isapi.c). 4.3.1 Installing with Apache Servers (All Connectivity Options) All users of the Apache server should follow the directions in this section, then follow the directions in one of connectivity option sections that follow. Install the CSP Gateway components and the CSP static files as follows: 1. NSD Module (if required): • CSPnsd.exe • CSPnsdSv.exe The default location for these modules is: C:\Program Files\Apache Group\Apache\CSPGateway\nsd The NSD should be run from within its home directory (above). The configuration file (CSP.INI) and Event Log (CSP.LOG) are written in this directory for NSD-based connectivity options. 2. CGI and other dynamically-linked modules: Note: There are separate binaries for each version of the Apache server as shown below. Common files: CSP Gateway Configuration Guide 91
Page 1 and 2:
CSP Gateway Configuration Guide Ver
Page 3 and 4:
Table of Contents About this Book .
Page 5:
5 Web Servers for UNIX®, Linux, an
Page 9 and 10:
1 Introduction to the CSP Gateway T
Page 11 and 12:
Using the Network Service Daemon (N
Page 13 and 14:
Minimal Apache Web Server or Privat
Page 15 and 16:
2 CSP Gateway Operation and Configu
Page 17 and 18:
CSP Web Gateway Management Page The
Page 19 and 20:
CSP Web Gateway Management Page 2.1
Page 21 and 22:
CSP Web Gateway Management Page Use
Page 23 and 24:
Page 25 and 26:
CSP Web Gateway Management Page Log
Page 27 and 28:
Page 29 and 30:
CSP Web Gateway Management Page 2.1
Page 31 and 32:
CSP Web Gateway Management Page Par
Page 33 and 34:
CSP Gateway and Security 4. Click S
Page 35 and 36:
CSP Gateway and Security Windows Pa
Page 37 and 38:
CGI Environment Variables The clien
Page 39 and 40:
HTTP Response Headers by invoking o
Page 41 and 42:
Compressing the Response to Request
Page 43 and 44:
Compressing the Response to Request
Page 45 and 46: CSP Page Output Caching 2.7.1 %resp
Page 47 and 48: CSP with Microsoft Active Server Pa
Page 49 and 50: Registering Additional File Types w
Page 51 and 52: Registering Additional File Types w
Page 53 and 54: Implementing HTTP authentication fo
Page 55: Implementing HTTP authentication fo
Page 58 and 59: Using Caché Server Pages with a Re
Page 65 and 66: 4 Web Servers for Microsoft Windows
Page 67 and 68: Microsoft Internet Information Serv
Page 95: Microsoft Internet Information Serv
Page 99 and 100: Apache Servers 4.3.2 Option 1: Apac
Page 101 and 102: Apache Servers Duplicate this confi
Page 103 and 104: Apache Servers 4.3.4.1 Operating an
Page 105 and 106: Apache Servers copy c:\MyCache\csp\
Page 107 and 108: Operating the Network Service Daemo
Page 109 and 110: 5 Web Servers for UNIX®, Linux, an
Page 111 and 112: Sun Web Servers 3. HyperEvents Comp
Page 113 and 114: Apache Servers Locate the block of
Page 115 and 116: Apache Servers /usr/CSPGateway/bin
Page 117 and 118: Apache Servers To be consistent wit
Page 119 and 120: Apache Servers SetHandler csp-hand
Page 121 and 122: Apache Servers ScriptAliasMatch /*\
Page 123 and 124: Apache Servers 5.2.4.2 Check the Ap
Page 125 and 126: Apache Servers The Web server confi
Page 127 and 128: Operating the Network Service Daemo
Page 129: Operating the Network Service Daemo
Page 132 and 133: Web Servers for Hewlett-Packard (HP
show all

CSP Gateway Configuration Guide - InterSystems Documentation

Create successful ePaper yourself

Delete template?

Save as template?