This page outlines the software requirements of a Gateway Hub node.
The following Linux operating systems are supported with Gateway Hub:
|Operating System||Versions Supported|
|Red Hat (64-bit)||7.6, 7.7, 7.8, 7.9, 8.0, 8.1, 8.2, 8.3, 8.4, 8.5, 8.6|
|CentOS (64-bit)||7.6, 7.7, 7.8, 7.9|
Each node must have the following software and utilities installed prior to installing Gateway Hub:
|Java Runtime Environment 8 (java-1.8.0-openjdk, java-1.8.0-openjdk-headless)|
|Network Time Protocol (ntp) or equivalent time synchronisation|
|Python (libselinux-python)||3.6 or newer||On RHEL 8.x systems use python3-libselinux instead.|
|PyYAML||5.3.1 or newer.|
|compat-openssl10||Required on RHEL 8.x systems only.|
|libnsl||Required on RHEL 8.x systems only.|
If your server has internet access, you can use the following command to install the prerequisite software for Gateway Hub:
sudo yum install libselinux-python3 java-1.8.0-openjdk java-1.8.0-openjdk-headless rpcbind redhat-lsb-core syslinux nc openssl PyYAML ntp
You must add the following to the
/etc/sysctl.conf file on each node:
vm.swappiness = 1 net.ipv4.tcp_retries2 = 5 vm.overcommit_memory = 0
The following settings must be applied:
- A unique hostname must be set.
- The reported time must be accurate. Follow the operating system documentation to configure NTP or other time synchronization software as needed.
- The Gateway Hub runtime user must exist.
/opt/hubfolder must exist and must be owned by the Gateway Hub runtime user.
- The Gateway Hub ports must be open. For more information, see Connectivity requirements.
- By default CentOS is configured with a user processes limit of
4096. You must not lower this limit, otherwise this may cause an error when installing Gateway Hub. You can check the current limit by using the
ulimit -ucommands and set the limit using the
ulimit -ucommand with a specified value.
Typically a Gateway Hub installation is performed as the Gateway Hub runtime user, which must exist on all nodes.
You can alternatively use separate installation user by specifying
installation > connection > user in your configuration file. If you are using a separate installation user, this must be on the sudoers list.