CSP Gateway Configuration Guide - InterSystems Documentation
CSP Gateway Configuration Guide - InterSystems Documentation
CSP Gateway Configuration Guide - InterSystems Documentation
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
<strong>CSP</strong> <strong>Gateway</strong> Operation and <strong>Configuration</strong><br />
• Delete an application path.<br />
• Add new application paths.<br />
Each <strong>CSP</strong> application must have the path to its <strong>CSP</strong> files configured. The configuration for each path identifies the Caché<br />
server responsible for running the application. Optional directives for specifying failover and load-balancing are included<br />
in the application path's configuration. The default application path, root, (/) is automatically configured when the <strong>CSP</strong><br />
<strong>Gateway</strong> is started for the first time. Inheritance is applied to application paths. For example, if a <strong>CSP</strong> request asks for a<br />
file in /Accounts/Invoices and there is no configuration for /Accounts/Invoices, the <strong>CSP</strong> <strong>Gateway</strong> uses the configuration<br />
defined for /Accounts. If this is not defined, the configuration for the default path of / is used.<br />
2.1.8.1 Adding an Application Path<br />
To configure the path to an application:<br />
1. On the Web <strong>Gateway</strong> Management page, click Application Access.<br />
2. Click Add Application. Note that many parameters have default settings.<br />
3. In the Application Path text box enter a unique path for the application. This path is the path which appears in the<br />
application URLs.<br />
Note:<br />
A Caché installation creates a new /csp configuration. If you have configured /csp as your application, your<br />
configuration is overwritten when you install a new build of Caché. To maintain your application configuration,<br />
enter a path other than /csp.<br />
Any directory under /csp works fine, such as /csp/myapplication, but the path cannot contain any dots (periods).<br />
These lead to ambiguity for the <strong>CSP</strong> <strong>Gateway</strong>. In this example: /csp/samples/menu.csp/csp/aaa/bbb/ccc.cls,<br />
the <strong>CSP</strong> <strong>Gateway</strong> could either interpret this as a request for /csp/samples/menu.csp/csp/aaa/bbb/ccc.cls or as<br />
a REST request for/csp/samples/menu.csp (where PATH_INFO is /csp/aaa/bbb/ccc.cls). The <strong>Gateway</strong>,<br />
working in the web server environment, has no way of resolving these ambiguities.<br />
<strong>CSP</strong> is case sensitive. Specify your path names consistently when you are configuring <strong>CSP</strong>.<br />
4. Enter the other configuration path and server parameters (described in the tables below) for this application.<br />
5. When you have finished, click Save <strong>Configuration</strong>. Changes you make to the application configuration take effect as<br />
new user sessions are created for that application path. Existing users are unaffected.<br />
Application Path <strong>Configuration</strong> Parameters<br />
The set of base parameters are as follows:<br />
Parameter<br />
Service Status<br />
Web Server Physical Path<br />
Function<br />
Enable and disable access to an application via the application path (default<br />
is Enabled).<br />
Path to the corresponding directory on the Web server.This setting is particularly<br />
important for Microsoft IIS systems where each path configured must be set<br />
up as a virtual directory under the Web server configuration. Each virtual<br />
directory defined within IIS must have a physical path associated with it. The<br />
purpose of this additional configuration procedure for IIS is to allow the paths<br />
used by <strong>CSP</strong> to be defined with execute permissions.The default is for execute<br />
(and hence access to <strong>CSP</strong>) to be denied.<br />
24 <strong>CSP</strong> <strong>Gateway</strong> <strong>Configuration</strong> <strong>Guide</strong>