CSP Gateway Configuration Guide - InterSystems Documentation

Introduction to the CSP Gateway
To have CSP serve static files for a particular CSP application, place the static files in the CSP application’s file system in
the correct location relative to the CSP files that make up the application (not in the web server’s own documents file system).
(Note that if you are serving files containing Unicode text, CSP uses the BOM to determine the correct encoding to use.
The BOM must be present in Unicode text files.)
Consult the sections in this book for your platform.
Note:
To run Zen-based applications, you must enable the Serve Files option and properly configure your web server.
See the section Static Files in Using CSP for more information.
1.7 Enable Sticky Sessions on Hardware Load Balancer
on High Availability Solutions
For High Availability solutions running over CSP, InterSystems recommends that you use a hardware load balancer for
load balancing and failover. InterSystems requires that you enable sticky session support in the load balancer; this guarantees
that -- once a session has been established between a given instance of the gateway and a given application server -- all
subsequent requests from that user run on the same pair. This configuration assures that the session ID and server-side
session context are always in sync; otherwise, it is possible that a session is created on one server but the next request from
that user runs on a different system where the session is not present, which results in runtime errors (especially with
hyperevents, which require the session key to decrypt the request). See your load balancer documentation for directions on
how to enable sticky session support.
Note:
It is possible to configure a system to work without sticky sessions but this requires that the CSP session global
be mapped across all systems in the enterprise and can result in significant lock contention so it is not recommended.
For more information on high availability and CSP, see the section “CSP Gateway Considerations” in the Caché High
Availability Guide.
1.8 Conventions Used in this Document
Where possible, the sample web server configurations described in this document are based on the current default installation
for both Caché and the CSP Gateway’s hosting web server. The default paths to the Web Server and Gateway components
are used in the configuration blocks. Change paths to these resources to suit your own installation where necessary.
Lines terminated with a back-slash (\) are continued to the next line.
For example, enter the following line, as shown in this document:
Init fn=load-modules shlib=CSPn3.dll \
funcs=csp_term
As:
Init fn=load-modules shlib=CSPn3.dll funcs=csp_term
The default installation directory for Caché is documented in the Default Caché Installation Directory section of the Caché
Installation Guide. This guide refers to the default using the variable install-dir and in many examples uses C:\cache-install-dir\
as the installation directory.
6 CSP Gateway Configuration Guide