Accessing CSP on Multiple Caché Servers

Read this section if you need to configure a single web server to access a single CSP application on more than one Caché server. Also read this section if you want to use a single web server to access more than one CSP application on more than one remote Caché server.

This section uses the Management Portal as the example application. Adapt these procedures for your own CSP application.

The Management Portal application is usually called with a URL in this format:

http://domain.com/csp/sys/UtilHome.csp

Once you have configured your application as described below, then to access this application on different servers, such as servers called cache1 and cache2,you will include the individual Caché servers names as part of the URLs as follows.

http://domain.com/cache1/csp/sys/UtilHome.csp
http://domain.com/cache2/csp/sys/UtilHome.csp

Changing the Caché Server Name in the URL

You can choose to display the Caché server name in the application path URL or not. If you are content with using the Caché server name in the URL, skip this subsection and proceed to the next subsection called “Configuring the Caché Server for the Application Path”.

If you do not want the Caché server name displayed in the CSP application URL, then follow the procedure in this subsection to create a substitute name.

Use the CSPConfigName parameter of the %System.CSP.SetConfigOpens in a new tab method for each of these servers. This example uses linda as the substitute name for server cache1 and perry as the substitute name for a server cache2. Follow this example using your own servers and substitute names.

In a terminal window on the cache1 server, run:

d $System.CSP.SetConfig("CSPConfigName","linda")

In a terminal window on the cache2 server, run:

d $System.CSP.SetConfig("CSPConfigName","perry")

On cache1, access the CSP Gateway Management page with:
http://localhost/csp/bin/Systems/Module.cxwOpens in a new tab
Select Server Access. Add server configurations for cache1 and cache2. See the section “Configuring Server Access” for details.
Select Application Access. Create an application path /linda/csp/sys/ with a Default Server of cache1. Create an application path /perry/csp/sys/ with a Default Server of cache2. See the section “Configuring Application Access” for details.
If the web server is IIS then set up virtual directories for /cache1 and /cache2 as described in the Add Virtual Directories to IIS section.
If using an Apache web server see Add Aliases to Apache Configurations.

To see other CSP global parameters, enter %SYS>d $system.CSP.DisplayConfig()

Configuring the Caché Server for the Application Path

If you are content with using the Caché server name in the URL, follow this procedure. If you do not want the Caché server name displayed in the CSP application URL, then follow the procedure in the preceding subsection “Concealing the Caché Server Name in the URL”

On your first server, access the CSP Gateway Management page with:
http://localhost/csp/bin/Systems/Module.cxwOpens in a new tab
Select Server Access. Add server configurations for cache1 and cache2. See the section “Configuring Server Access” for details.
Select Application Access. Create an application path /cache1/csp/sys/ with a Default Server of cache1. Create an application path /cache2/csp/sys/ with a Default Server of cache2. See the section “Configuring Application Access” for details.
If the web server is IIS then set up virtual directories for /cache1 and /cache2 as described in the Add Virtual Directories to IIS section.
If using an Apache web server see Add Aliases to Apache Configurations.