Prerequisites and Pre-Installation Configuration
Before deploying AnzoGraph DB, follow the instructions below to install the required software packages on each AnzoGraph DB host server. In addition to providing instructions for installing the prerequisite software, this topic also lists important notes about AnzoGraph DB users. For information about host server hardware and firewall requirements, see Server and Cluster Requirements.
The AnzoGraph DB Installer shell script guides you through the installation process, prompting you to choose specific options to include in the installation. There are two modes in which you can run the Installer, root (sudo) or non-root. Depending on the method or mode you choose, there may be additional configuration steps you need to perform manually, following the installation. See Post-Installation Configuration and Startup for more information on any potential additional steps you may need to perform.
Running the Installer in root (sudo) mode is the preferred method of installation since it allows automatic installation of most components without requiring additional post-install configuration. In addition, services are automatically configured and you can choose to automatically start AnzoGraph when the installation is complete.
- Install OpenJDK 11
- Install GNU Compiler Collection (GCC)
- Unset Linux Proxy Variables
- AnzoGraph DB User Notes
Install OpenJDK 11
Required for all methods or modes of installation. AnzoGraph DB requires Java Development Kit version 11 on each host server:
sudo yum install java-11-openjdk --enablerepo=csi*
You do not need to set the $JAVA_HOME variable to use the JDK installation. AnzoGraph DB's system management daemon (azgmgrd) requires JAVA_HOME, and it is set as part of the post-installation configuration (Post-Installation Configuration and Startup).
Install GNU Compiler Collection (GCC)
Required for all methods or modes of installation. All AnzoGraph DB servers are required to include the latest version of the GCC tools for your operating system. On all servers in the cluster, run the following command to install GCC:
sudo yum install gcc
Specifically, AnzoGraph DB requires the glibc, glibc-devel, and gcc-c++ libraries. Typically, when you install GCC by running yum install gcc
, those libraries are included as part of the package. In rare cases, depending on the host server configuration, installing GCC excludes certain libraries. If AnzoGraph DB fails to start and you receive a "Compilation failed" message, it may indicate that some of the required libraries are missing. To install the missing libraries, run the following command:
sudo yum install glibc glibc-devel gcc-c++
Unset Linux Proxy Variables
Make sure that the Linux environment variables http_proxy and https_proxy are not set on the servers. The AnzoGraph DB gRPC protocol cannot make connections to the database when proxies are enabled.
AnzoGraph DB User Notes
Mode dependent. When running the Installer as root (sudo), customers can create their own service users before installation. File system permissions will be based on the permissions of defined users. The Installer will automatically create an anzograph
user and, if the AnzoGraph DB frontend is installed, a jetty user. If customers do not create their own service users, the Installer will create them automatically.
For sudo installations, systemd units are created in /etc/systemd/system for azgmgrd and anzograph; a jetty systemd unit is also created when the AnzoGraph DB frontend is installed. By default, these systemd units will use the anzograph
user and the jetty
user.
When running the Installer as a non-root user, the Installer does not create any users and file system permissions are based on the current user who performs the installation. Example systemd units, located in the <install_path>/examples
directory, are provided as a template for customers to configure on their own.