This section describes the process for upgrading from Syndeia Cloud (SC) 3.5 SP2 or 3.6 to Syndeia Cloud 3.6 SP1 (the latest service pack).

Overview

Please read the following carefully before proceeding.

1. The upgrade process described in this document applies to Syndeia Cloud 3.5 SP2 or 3.6. If you are running 3.5 or 3.5 SP1, you must first upgrade to 3.5 SP2 before proceeding. Detailed steps for this are available in the Upgrades and Migration document.

2. Source and Target Server Terminology - This document describes a side-by-side (parallel) upgrade process, involving two servers:

   • Source Server: The original server running Syndeia Cloud version 3.5 SP2 or 3.6.

   • Target Server: The cloned server, which will be upgraded to Syndeia Cloud 3.6 SP1.

3. The estimated time to complete the upgrade process excluding server cloning and file transfer time, is approximately 2-3 hours. During this period, end users should not access the original Syndeia Cloud server (3.5 SP2 or 3.6). Only administrators should have access for the upgrade.

4. Migration Process Overview

   • Stages 1-2: The existing Syndeia Cloud 3.5 SP2 or 3.6 production environment is cloned to create a new environment, which will serve as the basis for Syndeia Cloud 3.6 SP1. Before cloning, ensure that the Syndeia Cloud 3.5 SP2 or 3.6 deployment is unavailable to users. The original 3.5 SP2 production server can be brought back online after cloning, but note that any data created in the original environment post-cloning will not be migrated. This ensures the existing deployment remains as a reliable fallback for the migration process.

   • Stages 3-4: Syndeia Cloud 3.6 SP1 installation files are downloaded and uploaded to the target server, which is then prepared for the upgrade.

   • Stages 5-9: Key infrastructure services (Java, Cassandra, Zookeeper, Kafka, and Java JMX) in the cloned environment are upgraded to the latest versions. This is essential for:

     • Enabling new features in Syndeia Cloud 3.6 SP1.

     • Strengthening the system’s cybersecurity.

     • The upgrades include:

       • Java 1.8.0 → 11.0.23

       • Cassandra 3.11.X → 4.1.0

       • JanusGraph 0.5.3 → 1.0.0

       • Zookeeper 3.6.3 → 3.8.4

       • Kafka 3.2.1 → 3.7.0

       • Java JMX 1.8.0 → 11.0.23

   • Stages 10-11: The Syndeia Cloud 3.6 SP1 services are started, and data is verified. The new cloned environment is now your Syndeia Cloud 3.6 SP1-based production environment.

5. All pre-requisites must be met for the target Syndeia Cloud instance. Please refer to the Automated Deployment: Linux | Prerequisites Summary for details.

6. Sample outputs are shown in Expand sections throughout this document. You can view the expected output for a given command by clicking the “<“ symbol in the expand section. You can try it out in the example expand section below:

Scope and Limitations

This document outlines the process for upgrading a single-node Linux-based Syndeia Cloud environment. Specific instructions for multi-node environments and Windows-based installations are outside the scope of this document.

Multi-node Environments

Due to the variability in multi-node setups, instructions for upgrading multi-node installations are not provided here. Users with experience managing their multi-node environments may adapt the instructions as needed. For additional help with multi-node environments, users can open a request on our helpdesk.

Windows Server-based Environments

Syndeia Cloud 3.6 SP1 is not supported on Windows Servers. It is using newer versions of infrastructure components - Cassandra, JanusGraph, Kafka, and Zookeeper. This is necessary for expanding Syndeia capabilities and for enhanced cybersecurity. Specifically, Syndeia Cloud 3.6 SP1 requires Cassandra 4.1. Cassandra version 4+ is no longer supported on Windows Servers. Syndeia admins running Syndeia Cloud on Windows Server are encouraged to open a request on our helpdesk and get our assistance on a path forward.

Refer to the following page for additional details: Appendix W - Windows Server Support.

Offline Mode

Customers operating in an air-gapped environment requiring an offline mode installation can do so by following the preparation steps outlined in the https://intercax.atlassian.net/wiki/spaces/IN/pages/3566305787 document. Once those steps are followed, the remainder of the stages outlined in this document should be the same. If any issues or questions arise relating to this offline installation mode, please submit a help ticket.

The Syndeia Cloud 3.5 SP2 / 3.6 → 3.6 SP1 migration process has the following 11 stages.