CSP Gateway Configuration Guide - InterSystems Documentation

More documents

Recommendations

Info

Web Servers for Hewlett-Packard (HP) OpenVMS /PROCESS_NAME=CSPNSD CSPNSD If this process starts successfully, the NSD's startup banner is written to the file: CSPNSD.LOG. Use the following procedure to stop the NSD: 1. Change to the NSD's home directory: $ SET DEF APACHE$ROOT:[CSP] 2. Stop the NSD using the command: $ MCR APACHE$ROOT:[CSP]CSPNSD.EXE STOP This command closes down the NSD in an orderly manner – it gracefully terminates all open connections to Caché and releases all its system resources before terminating. Do not use a plain stop command to terminate the NSD. All errors are reported in the Event Log (CSP.LOG). OpenVMS System Errors are reported in CSPNSD.LOG. These files are created and maintained in the NSD’s home directory. The configuration file CSP.INI also resides in this directory. 6.2.1 Starting the NSD on Alternative TCP port By default, the NSD listens for incoming requests on TCP port 7038. You can override this by creating and specifying alternative parameters in the CSPNSD.INI file. The format of this file is as follows and must be installed in the NSDs home directory. [SYSTEM] Ip_Address=127.0.0.1 TCP_Port=7038 It is necessary to communicate the value of the following parameters to the Apache modules so that they know how to access the NSD. To do this, set the following environment variables in the Apache configuration to indicate the address and port of the target NSD installation. CSP_NSD_NAME — This is the IP address of the NSD. Only use this parameter if the NSD is operating on a remote computer. CSP_NSD_PORT — This is the TCP port of the NSD. Example 1: Distribute the load for two Apache virtual hosts (say, 123.123.1.1 and 123.123.1.2) between two independent NSD installations (listening on TCP port 7038 and 7039). Add the following directives to the Apache configuration (HTTPD.CONF): ServerName 123.123.1.1 SetEnv MGW_NSD_PORT 7038 ServerName 123.123.1.2 SetEnv MGW_NSD_PORT 7039 Example 2: Distribute the load for two CSP applications (say, /csp1 and /csp2) between two independent NSD installations (listening on TCP port 7038 and 7039). 1. Add the following directives to the Apache configuration (HTTPD.CONF): SetEnv MGW_NSD_PORT 7038 SetEnv MGW_NSD_PORT 7039 130 CSP Gateway Configuration Guide
Operating the Network Service Daemon (NSD) 2. Restart Apache after making changes to its configuration. If you want to run multiple instances of the NSD, you must install separate instances in separate directories, each maintaining its own copy of the configuration and log files (CSPNSD.INI, CSP.INI and CSP.LOG). The CSP Web Gateway Management page for each instance can easily be accessed by using the NSD’s internal HTTP server. For example: http://localhost:7038/csp/bin/Systems/Module.cxw http://localhost:7039/csp/bin/Systems/Module.cxw CSP Gateway Configuration Guide 131
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 60 and 61:
Page 62 and 63:
Page 65 and 66:
4 Web Servers for Microsoft Windows
Page 67 and 68:
Microsoft Internet Information Serv
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
Page 85 and 86: Microsoft Internet Information Serv
Page 97 and 98: Apache Servers This, for example, i
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
Page 134 and 135: Web Servers for Hewlett-Packard (HP
show all

CSP Gateway Configuration Guide - InterSystems Documentation

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?