The SCSP Proxy tab allows you to change the proxy log level, as well as modify or add a cluster. The SCSP Proxy installation on the CSN allows for clients on the external network, including remote clusters using Content Router, to send and receive SCSP requests to and from Netmail Store nodes on the internal network. The SCSP Proxy is configured during the network bootstrap process to listen on port 80 of both the external and internal interfaces. The log level for the Proxy can be changed from the user interface by selecting an alternate value from the dropdown and clicking Update.
The SCSP Proxy is also capable of communicating with remote clusters to perform operations like global infos for one or more objects. To add a remote cluster to the configured list, click the Add Cluster button. To edit an existing remote cluster, click the Edit button. To delete a cluster from the list, click the checkbox in the Delete column next to the cluster that should be deleted and then click Update.
The following information is required for all configured remote clusters:
|Remote Cluster Name|
The alpha-numeric name for a remote cluster that will be used in requests sent to the proxy. May not contain whitespace. May be the DNS name for the cluster but that is not required.
The IP address or hostname of the remote proxy the local proxy will communicate with. May not contain whitespace.
The port on which the remote proxy will listen incoming requests. This is usually port 80. May not contain preceding or trailing whitespace.
The name of an administrator that belongs to the Netmail Store Administrators group for the remote cluster. May not contain whitespace.
The password for the administrator specified in the User ID field. This value may contain spaces as long as they are not leading or trailing.
The Netmail Administration Console should be used for all configuration updates, but, for reference purposes, all SCSP Proxy configuration parameters are stored in the /etc/caringo/scspproxy/scspproxy.cfg and /etc/caringo/scspproxy/hosts.cfg configuration files. These files are automatically generated and should never be manually edited unless under direction of your support personnel.
The scspproxy service will be started automatically after the initial configuration of the CSN. If needed, it can be started, stopped or restarted via a standard init.d script: