Use the following commands to manually control the start-up and shutdown of the Gateway service and to query the running status:
systemctl start cloudgateway systemctl stop cloudgateway systemctl status cloudgateway |
The /etc/sysconfig/cloudgateway file contains the Java process memory settings and the maximum number of open file descriptors for Gateway.
HEAP_MIN=1024m HEAP_MAX=1024m MAX_OPEN_FDS=25000 |
Memory: While the default JVM heap memory settings work well for a small deployment, increase them for larger deployments handling a large transaction load for multiple tenants. The JVM heap memory is utilized for caching frequently used objects, authentication results, and other operational data.
Maximum File Descriptors: While the default maximum number of open file descriptors works well for a small deployment, increase the limit for larger deployments handling a large transaction load for multiple tenants. Network socket connections for the upstream clients plus the back-end connection pool comprises the majority of the open file descriptors during Gateway operations.
The firewall rules from the default RHEL/Rocky Linux 8 or RHEL/CentOS 7 installation need to be changed to allow inbound client access to Gateway. Adjust the IPTABLES rules to allow inbound access for each front-end protocol or disable IPTABLES entirely. Execute the following commands to disable the operating system's firewall:
systemctl disable firewalld systemctl stop firewalld |
While it is valid to use IPTABLES in conjunction with Gateway, the service startup script issues a notice, if IPTABLES are enabled as a reminder since using them can be a source of confusion if inbound traffic to Gateway is blocked. Ignore this startup notice if the inbound rules to allow access are customized.
See Configuring Domains and Configuring Buckets to create and manage domains and buckets from the Content UI.
See Manually Creating and Renaming Domains if manual creation is needed (from the command line).