Anzo 5.1 Installation and Upgrade Notes

To view installation and upgrade instructions for Anzo servers, see Deploying Anzo in the Anzo Deployment and User Guide.

If you are upgrading to a 5.1 version from a previous release, review the following notes for important details about upgrades to Anzo components.

Review Your License when Upgrading Between Major Versions

If you are upgrading to a new major version of Anzo, such as from 4.x to 5.x, your Anzo license may need to be updated to add the new version. Before upgrading between major versions, contact Cambridge Semantics to review and update your license if necessary.

Upgrade Anzo Unstructured Leader and Worker Nodes

Updates to the Anzo server typically include changes to the Anzo Unstructured (AU) cluster software. If you are upgrading from a previous release, upgrade the AU worker and leader nodes to the latest version. For instructions on upgrading an AU cluster, see Upgrading Anzo Unstructured in the Anzo Deployment and User Guide.

When upgrading the AU software, the leader and worker applications must be upgraded at the same time using the same installer so that the software versions are identical across the cluster. You cannot upgrade the worker nodes without upgrading the leader and vice versa.

Use a 2.2.x or Later Version of AnzoGraph

For the best performance, stability, and compatibility with all Anzo features, use a 2.2.x or later version of AnzoGraph with Anzo Version 5.1.x. For installation and upgrade instructions, see Deploying a Static AnzoGraph Cluster in the Anzo Deployment and User Guide.

Upgrade Any CData ODBC and JDBC Drivers for Anzo

Updates to the Anzo server often include improvements to the CData ODBC and JDBC drivers. To take advantage of the improvements, Cambridge Semantics recommends that you upgrade any existing ODBC or JDBC drivers with the latest version after upgrading Anzo. For instructions, see Accessing Data via the ODBC or JDBC API in the Anzo Deployment and User Guide.

Prepare any Custom Orchestration Services

As described in Incorporated Orchestration Service and Associated Datasets into Anzo, Version 5.1.7 added a default Orchestration Service configuration to Anzo. If you are upgrading from a pre-5.1.7 version and have an Orchestration Service that is defined by the URI http://cambridgesemantics.com/service/OrchestrationService, your service will be updated automatically during the Anzo upgrade, and you do not need to perform any additional steps.

If you are upgrading from a pre-5.1.7 version and have a custom Orchestration Service that uses a different URI, follow the general guidelines below to prepare your environment before upgrading Anzo.

Your Cambridge Semantics Customer Success manager can provide additional guidance for your specific solution.
  1. Unregister all Ingest Managers.
  2. Download the existing Orchestration Service graph to use as a baseline for comparison after the upgrade.
  3. Once the Orchestration Service graph is downloaded, delete the graph instance in Anzo. In addition, make sure that you delete any references to the graph, such as from the Semantic Services registry (reg:SemanticService), ASDL Configurations, etc.
  4. Upgrade Anzo.
  5. After the upgrade, compare the new default Orchestration Service configuration that was created from the product registry-data with the graph that you downloaded before the upgrade. Identify any custom configurations that need to be added to the new service and make the changes.

Recreate Existing Cloud Locations

Version 5.1.3 modified the way available memory and CPU are calculated for Kubernetes-based dynamic deployments of AnzoGraph, Anzo Unstructured, Elasticsearch, and Spark. If you have Cloud Locations configured in Anzo and are upgrading from a pre-5.1.3 version, those Cloud Location instances need to be recreated after upgrading. To do so, create a new Cloud Location and import the configuration files that were used to create the original instance. Removing previous Cloud Location instances is not required.

Database Data Source Upgrade Notice

Version 5.1.0 updated the internal data source ontology. The upgrade process updates your existing data sources to follow the new ontology. If you are upgrading from a pre-5.1.0 version of Anzo and want to add a volume from the previous release or if you use custom JDBC drivers, those components need to be updated separately. See Refactored Database Data Source Ontology for details.

Related Topics