Anzo Requirements
This page provides important guidelines to follow when choosing the hardware and software for servers that host Anzo.
- Hardware Requirements
- Software Requirements
- Firewall Requirements
- File Storage Requirements
- Standalone Ingestion Server Requirements
For information about Anzo Unstructured architecture requirements, see Anzo Unstructured Requirements and Recommendations.
Hardware Requirements
Cambridge Semantics lists above average production system hardware requirements as a guideline. These specifications are similar to what Cambridge Semantics currently provisions as the standard hosted environment. Larger production data sets running interactive queries may require significantly more powerful hardware and RAM configurations. Keep in mind that you are installing both a high performance graph database server as well as a fully featured application server. Provision production server hardware accordingly to avoid performance issues.
The table below provides a summary of the recommended hardware for production servers and the minimum requirements for test servers.
| Component | Minimum | Recommended | Guidelines |
|---|---|---|---|
| Available RAM | 8 GB | 32 GB or more | The Anzo 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 for Anzo to swap data from disk to memory. In addition, RAM is required to hold intermediate results for join queries. |
| Disk space and type | 10 GB (Anzo Server) 100 GB (Data) |
100 GB (Anzo Server) 1+ TB (Data) |
See File Storage Requirements below. |
| CPU | 4 core 2.2GHz | 8 core 3GHz+ | Once you provision sufficient RAM and a high-performing I/O subsystem, 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 the performance of interactive queries. |
| Architecture | 64-bit | 64-bit | Cambridge Semantics only supports the 64-bit versions of the server for production use. |
Software Requirements
This section lists the software requirements for Anzo servers and client workstations. It also includes user account information and lists the supported single sign-on providers.
| Component | Minimum | Recommended | Guidelines |
|---|---|---|---|
| Operating System (Anzo Server) | RHEL/CentOS 6 | RHEL/CentOS 7 | Cambridge Semantics recommends that you tune the ulimits for your Linux distribution to increase the limits for certain resources. See Configure User Resource Limits for more information. |
| Microsoft Excel (Client Workstation) | Excel 2003 | Excel 2007+ | The Anzo for Office data integration mapping tool plugin requires Microsoft Excel. |
| Web Browser (Client Workstation) | Firefox 62+ Chrome 74+ Safari 12+ |
Chrome 80+ | Use the latest versions of web browsers as some older versions will not work with the Anzo user interface components. |
| Enterprise-Level Anzo Service User Account | N/A | N/A | It is important to work with your IT organization to create an Anzo service user account at the enterprise level. The service user account needs to be associated with a central directory server (LDAP) so that it is available across Anzo environments and is managed in accordance with the permissions policies of your company. For more information, see Anzo Service User Account Requirements below. |
Anzo Service User Account Requirements
For consistent and appropriate access management across current and future Anzo environments, it is important for the IT organization to create an enterprise-level, LDAP-managed Anzo service user account. The service user account should be used when installing and running Anzo and all component environments, such as AnzoGraph, Spark, Elasticsearch, and Anzo Unstructured clusters. The service account should not have root user privileges but does need the following access:
- The account must have read and write permissions for the Anzo component installation directories. The default Anzo server installation directory is
/opt/Anzo. - The account must have read and write access to the shared file store, such as the NFS mount location, where all Anzo components will read and write files during the data onboarding processes.
- The account must have a home directory on the Anzo host server.
Supported Single Sign-On Providers
Anzo supports the following single sign-on (SSO) protocols:
- Basic SSO
- Facebook OAuth
- JSON Web Tokens (JWT)
- Kerberos
- OpenID Connect (OIDC)
- Security Assertion Markup Language (SAML)
- Spring Security OAuth2
For information about configuring SSO access, see Configuring SSO Access.
Firewall Requirements
The table below lists the TCP ports to open on the Anzo host.
| Port | Description | Access Needed... |
|---|---|---|
| 61616 | Anzo port used by the software development kit (SDK) and command line interface (CLI) |
|
| 61617 | Anzo SSL port used by the SDK and CLI |
|
| 8022 | Anzo SSH service port |
|
| 8945 | Anzo Administration service port |
|
| 8946 | Anzo Administration service SSL port |
|
| 80 | Application HTTP port |
|
| 443 | Application HTTPS port. |
|
| 3389 | LDAP port |
|
| 9393 (optional) | Optional Java Management Extensions (JMX) port. Enable this port if you want to connect to Anzo from a JMX client. |
|
| 9394 (optional) | Optional JMX SSL port. Enable this port if you want to make a secure connection to Anzo from a JMX client. |
|
| 5700 | The Anzo protocol (gRPC) port for secure communication between AnzoGraph and Anzo For more information about the communication between Anzo and AnzoGraph, see Firewall Requirements in AnzoGraph Server Requirements. |
|
| 5600 | AnzoGraph's SSL system management port |
|
File Storage Requirements
Anzo supports reading from and writing to storage systems such as a mounted NFS, Hadoop Distributed File Systems (HDFS), File Transfer Protocol (FTP or FTPS) systems, Google Cloud Platform (GCP) storage, and Amazon Simple Cloud Storage Service (S3).
Set up a storage system that is accessible by both Anzo and AnzoGraph. Depending on your infrastructure and use case, you might need to have enough storage space available for storing source data files, RDF load files, ETL job files, and other supporting files.
For more information about connecting to file storage, see Connecting to a File Store.
Standalone Ingestion Server Requirements
Anzo includes an embedded Spark ETL engine to integrate data from various sources. Depending on your server configuration, the embedded engine might not be sufficient for ingesting very large amounts of data. To support ingestion of large data sets, you can install standalone ingestion servers. This page lists the recommended configuration for standalone data ingestion servers.
| Component | Recommendation |
|---|---|
| Available RAM | 100+ GB |
| Disk Space | 200+ GB |
| CPU | 16+ cores |