Anzo Server Requirements
This topic lists the requirements and guidelines to follow when choosing the hardware and software for an Anzo host server and the client workstations that will access Anzo.
Hardware Requirements
The following guidelines apply to individual Anzo host servers within production and development environments. Your Cambridge Semantics Customer Success manager can help you identify an overall platform deployment configuration that is appropriate for your solution and use cases.
Production Environments
| Component | Minimum | Recommended | Description |
|---|---|---|---|
| RAM | 64 GB | 128+ GB | The system data source is a disk-based graph store (called a journal or volume). When the system source is queried, Anzo swaps the data from disk to memory on demand. Choosing a host server with more RAM increases the performance of system queries because the OS can store the journal data in its file cache, avoiding the need to swap data from disk to memory. In addition, RAM is required to hold intermediate results for join queries. |
| Disk Space: Installation Path | 100 GB | 500+ GB | The installation disk needs to have enough space to store the system data source, log files, plugins, and the Anzo client. Do not install Anzo on an NFS mount as it causes issues with the Java environment. |
| Disk Space: Shared File System | 500 GB | 1+ TB | The shared file system stores all of the files that are shared between Anzo components. See Platform Shared File Storage Requirements. |
| vCPU | 16 | 32 | Once you provision sufficient RAM, performance depends on CPU capabilities. Keep in mind that you are provisioning for both a production database and a busy application server. A greater number of cores and high clock speed can make a dramatic difference in performance when there are many concurrent users. |
| Architecture | 64-bit | 64-bit | Anzo is supported only on 64-bit architecture. |
Development Environments
| Component | Minimum | Recommended | Description |
|---|---|---|---|
| RAM | 32 GB | 64+ GB | These RAM guidelines assume that the development environment is intended to host smaller data volumes than the production environment and support one or two users at a time. For development environments with large data volumes and many concurrent users, increase the RAM amount. |
| Disk Space: Anzo Install Path | 100 GB | 500+ GB | The installation disk needs to have enough space to store the system data source, log files, plugins, and the Anzo client. Do not install Anzo on an NFS mount as it causes issues with the Java environment. |
| Disk Space: Shared File System | 500 GB | 1+ TB | Typically the development environment mounts the same shared file system as the production environment. |
| vCPU | 8 | 16 | Like the RAM guidelines, these vCPU guidelines assume that the development environment is intended to host smaller data volumes than the production environment and support one or two users at a time. For development environments with large data volumes and many concurrent users, increase the number of vCPU. |
| Architecture | 64-bit | 64-bit | Anzo is supported only on 64-bit architecture. |
Software Requirements
This section lists the software requirements for Anzo servers and client workstations. It also includes important service account information and lists the supported single sign-on providers.
Do not run any other software, including anti-virus software, on the same server as Anzo. Additional software may be run in a development environment with the expectation of lowered Anzo performance. Cambridge Semantics strongly recommends that you do not run additional software on the Anzo server in a production environment.
| Component | Minimum | Recommended | Guidelines |
|---|---|---|---|
| Operating System: Anzo Server | RHEL/CentOS 7.9 | RHEL/CentOS 7.9 | Anzo is supported on Enterprise Linux 7.9 – 9.3 operating systems. |
| Java: Anzo Server | Java 8 | Oracle JVM 8 (included in the installer) | Anzo requires Java version 8. OpenJDK and JVM environments are supported. Oracle JVM 8 is included in the Anzo installer and does not need to be pre-installed on the host server. |
| Web Browser: Client Workstation | Firefox 62+ Chrome 74+ Safari 12+ Chromium-Based |
Chrome 90+ | Use the latest versions of web browsers, especially if you are using a Chromium-based browser, as some older versions will not work with the Anzo user interface components. |
| Service User Account | N/A | Enterprise-level account | It is important to install and run Anzo (and all other platform components) as the same service user. See Platform Service User Account Requirements. |
Supported Single Sign-On Providers
Anzo supports the following single sign-on (SSO) protocols:
- Basic SSO
- JSON Web Tokens (JWT)
- Kerberos
- OpenID Connect (OIDC)
- Security Assertion Markup Language (SAML)
- Spring Security OAuth2
Firewall Requirements
The table below lists the TCP ports to open on the Anzo server host. The following image shows a representation of the ports and connected components.
| Port | Description | Required Access |
|---|---|---|
| 61616 | HTTP port used by the software development kit (SDK) and command line interface (CLI) | Available on the Anzo server and between Anzo and client workstations if installing the CLI or SDK remotely |
| 61617 | SSL port used by the SDK and CLI | Available on the Anzo server and between Anzo and client workstations if installing the CLI or SDK remotely |
| 8022 | OSGi SSH service port | Available on the Anzo server |
| 8945 | Administration application HTTP port | Between Anzo and client workstations |
| 8946 | Administration application SSL port | Between Anzo and client workstations |
| 8080 | Anzo application HTTP port | Between Anzo and client workstations |
| 8443 | Anzo application SSL port | Between Anzo and client workstations |
| 3389 | LDAP port | Between Anzo and the LDAP server |
| 2551 (optional) | For Distributed Unstructured (DU), this is the SSL port for communication between the leader node, which is typically installed on the Anzo host server, and the worker nodes | Between the DU leader node (on the Anzo host) and the worker nodes |
| 9200-9300 (optional) | If you plan to connect to an Elasticsearch server, Anzo needs access to the Elasticsearch http.port |
Between Anzo and Elasticsearch |
| 9393 (optional) | Optional Java Management Extensions (JMX) HTTP port for connecting to Anzo from a JMX client | Between Anzo and the JMX client |
| 9394 (optional) | Optional JMX SSL port | Between Anzo and the JMX client |
| 5700 | The Anzo protocol (gRPC) port for secure communication between AnzoGraph and Anzo | Between Anzo and the AnzoGraph leader server |
| 5600 | The AnzoGraph SSL system management port | Between Anzo and the AnzoGraph leader server |
For instructions on installing Anzo, see Installing the Anzo Server.