Gateway Installation

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 running 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.

Note

See the Upgrade section in Content Gateway Release Notes for the version being installed for information about upgrading.

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 this 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.
1. Complete the IDSYS Document Formatfor user authentication.
2. Complete the Policy Document for access control.

Record the location for the server logs.

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.
Optionally, install and start Docker on the Gateway server to utilize video clipping and hybrid cloud on Gateway version 7.8 and higher.
1. Install docker-ce following instructions in CentOS.
2. Run any needed post-installation step to start Docker, such as enabling the systemd services:
  Post-installation steps
3. Features will fail with SElinux set to "Enforced". Check the OS setting with the "getenforce" command. If this extra layer of security is not needed, reduce to "Permissive" or "Disabled" to allow features to proceed.