The Content Gateway is the access point and gatekeeper for the back-end storage cluster. It provides value-added services for user applications and storage administrators.
SCSP Proxy
See Migrating from SCSP Proxy for implementing Gateway to replace SCSP Proxy.
Important
Use one Gateway dedicated to run as Service Proxy for your cluster administration (using Swarm UI and Management API) in production, and additional Gateway appliances to handle all content management at scale. Enable both cluster administration and content management on a single Gateway instance if the cluster is for testing or less usage.
Upgrading
See the Upgrading section in Release Notes for the version being installed for information about upgrading.
Apply all current operating system patches before installing the Gateway. The Installer preserves the existing versions of
pip
andrequests
detected.Install Java. Gateway requires a Java 8 SDK. The SDK must be Oracle’s Java or OpenJDK. Use the same JVM and version on all Gateway appliances.
Install the Java language on the server.
yum install java-1.8.0-openjdk
After installing, verify the correct Java version is active.
java -version
Run the following command to change the active Java version.
alternatives --config java
Download the Swarm bundle from the Downloads section on the DataCore Support Portal to get the Gateway distribution, and unzip it.
Locate the RPM for the Gateway software. If the Caringo RPM public key is not added, which is included with the distribution bundle to your system, run the following command:
rpm --import RPM-GPG-KEY
Run the command to install the Gateway package, substituting the exact version number for the RPM in the distribution file for the {version} string.
yum install caringo-gateway-{version}.rpm
Navigate to the
examples
directory for configuration file examples to study and clone./etc/caringo/cloudgateway/examples
Complete authentication for Gateway.
Note:
The plain-text passwords in both Gateway configuration and IDSYS are replaced by encrypted versions during Gateway's startup. (v7.1)Complete the IDSYS document for user authentication.
/etc/caringo/cloudgateway/idsys.json
Complete the Policy document for access control.
/etc/caringo/cloudgateway/policy.json
Record the location for the server logs.
/var/log/caringo/cloudgateway_server.log
Verify NTP time synchronization is used on the Gateway server to guarantee storage transaction handling and that the audit log timestamps match across servers. NTP is critical for the Swarm operation and should be used on all hosts interacting with Swarm.
If required, install and start Docker Community Edition on the Gateway server to utilize video clipping and hybrid cloud on Gateway version 7.8 and higher. See Gateway Requirements.
Start Docker after installing. See https://docs.docker.com/config/daemon/systemd/?msclkid=36e68349c0d411ecb438f130e19228bc.
On certain operating systems, run an additional command to restart Docker after a server reboot. See https://docs.docker.com/engine/install/linux-postinstall/#configure-docker-to-start-on-boot.