CSP Gateway Configuration Guide - InterSystems Documentation

CSP Web Gateway Management Page
file in /Accounts/Invoices and there is no configuration for /Accounts/Invoices, the CSP Gateway uses the configuration
defined for /Accounts. If this is not defined, the configuration for the default path of / is used.
2.1.9.1 Adding an Application Path
To configure the path to an application:
1. On the Web Gateway Management page, click Application Access.
2. Click Add Application. Note that many parameters have default settings.
3. In the Application Path text box enter a unique path for the application. This path is the path which appears in the
application URLs.
Note:
A Caché installation creates a new /csp configuration. If you have configured /csp as your application, your
configuration is overwritten when you install a new build of Caché. To maintain your application configuration,
enter a path other than /csp.
Any directory under /csp works fine, such as /csp/myapplication, but the path cannot contain any dots (periods).
These lead to ambiguity for the CSP Gateway. In this example: /csp/samples/menu.csp/csp/aaa/bbb/ccc.cls,
the CSP Gateway could either interpret this as a request for /csp/samples/menu.csp/csp/aaa/bbb/ccc.cls or as
a REST request for/csp/samples/menu.csp (where PATH_INFO is /csp/aaa/bbb/ccc.cls). The Gateway,
working in the web server environment, has no way of resolving these ambiguities.
CSP is case sensitive. Specify your path names consistently when you are configuring CSP.
4. Enter the other configuration path and server parameters (described in the tables below) for this application.
5. When you have finished, click Save Configuration. Changes you make to the application configuration take effect as
new user sessions are created for that application path. Existing users are unaffected.
Application Path Configuration Parameters
The set of base parameters are as follows:
Parameter
Service Status
Web Server Physical Path
Extra CGI Environment
Variables
Process with this class
Function
Enable and disable access to an application via the application path (default
is Enabled).
Path to the corresponding directory on the web server.This setting is particularly
important for Microsoft IIS systems where each path configured must be set
up as a virtual directory under the web server configuration. Each virtual
directory defined within IIS must have a physical path associated with it. The
purpose of this additional configuration procedure for IIS is to allow the paths
used by CSP to be defined with execute permissions.The default is for execute
(and hence access to CSP) to be denied.
Comma-separated list of additional CGI Environment Variables to be returned
to the Caché environment with each and every request. The commonly-used
CGI Environment Variables are automatically sent with each request. Enter
the wildcard character (*) to instruct the CSP Gateway to send all Environment
Variables supplied by the web server to the Caché server with each request.
Process files in this path with the specified class. This allows you to build your
own request handlers in CSP. For example, you could build your own WebDAV
server by creating a WebDAV class and defining it here. There is a WebLink
emulation class which makes use of this facility: %CSP.WebLink.
CSP Gateway Configuration Guide 29