We are glad that you are reading this page because that means you’re already convinced of the power of Syndeia 3.3 with all the cool, new features and you’ve either already installed Syndeia Cloud 3.3, or are in the process of doing so, and you are wondering what happens to the data that you’ve painstakingly created with Syndeia Cloud 3.2? Well, since Syndeia 3.3 was such a big release, a lot has changed behind the scenes, and that means, unavoidably, you’ll have to migrate your data so that it complies with the data format expected by Syndeia 3.3. This page explains what the entire migration process entails and the steps to successfully transition to Syndeia 3.3.

For the remainder of the document, whenever Syndeia 3.3 is mentioned, it means Syndeia Cloud 3.3, and same for Syndeia 3.2.

Pre-requisites

Syndeia 3.2 installed and running on a server. Syndeia 3.2 requires the Cassandra database and a syndeia keyspace to hold 3.2 data. This is our source server (database).
Syndeia 3.3 installed and running on a server. Syndeia 3.3 also requires the Cassandra database and syndeia_cloud_store & syndeia_cloud_auth keyspaces to hold 3.3 data. Additionally, Syndeia 3.3 uses JanusGraph behind the scenes, which requires additional syndeia_cloud_graph & syndeia_cloud_graph_config keyspaces to hold graph data. This is our target server (database).
The superuser and the setup steps should’ve already been run on the Syndeia 3.3 server.
The migration process requires an additional syndeia_cloud_devops keyspace on the target 3.3 server. The schema/gen-schema.cql file contained in this utility has the required CQL statements to create the schema and tables. Please run this utility from a CQL shell or using a tool similar to DataStax Devcenter. This keyspace has three sets of tables - a pre_stage_* set, a migrate_stage_* set, and a duplicate_* set of tables.
The Syndeia-Migration-3.3 utility.
The user who is doing the migration should be an admin user. Additionally, he should have the credentials of each external repository (server) because one of the steps requires that you run the Syndeia dashboard and connect to each of the repositories using your credentials. Also, this user should have permission to view all the data in any of the external repositories (servers).

Overview of Syndeia Cloud 3.2 → 3.3 Migration Process

The migration process works in the following stages:

Replicating (copying) data from the source (3.2) database to the migration (pre_stage) tables
Enhancing data in pre_stage tables by connecting to Slim (so that it is in a form which can be loaded in 3.3)
Staging data from pre_stage tables to migrate_stage tables
Loading data in target (3.3) database tables by calling the Syndeia Cloud API for data from migrate_stage tables.

The details of the various stages are as follows:

Replicate - first copy all data from the source (3.2) database to pre_stage tables (note that the 3.2 database has only 4 tables for repositories, containers, artifacts, and relations). Once the data has been copied from the 3.2 server to the pre_stage tables, we can safely disconnect from the 3.2 server and its role ends there. When the data is copied into the corresponding pre_stage tables, the value of the status column is set to -2.
Enhance - In 3.3, we also have type related tables, which were not there in 3.2. Hence, in this step, we also have to connect to a running instance of Slim. Using this running instance, we can get external repository types and internal relation types (which is like hard-coded data, made up by us) which we first insert in pre_stage tables. Then for containers and artifacts, we need to connect to the actual repositories, get the type information for each of the container and artifact, and populate the corresponding pre_stage tables. Once, all data has been enhanced, we modify the value of the status column to -1.
Stage - Once all the data has been enhanced, we just insert all data from pre_stage tables to migrate_stage tables. During the insertion, we first update the value of the status column to 0 in pre_stage tables and then set this same value 0 in migrate_stage tables (because the final part of the migration process only picks up those records whose status is 0).
Load - Load all the data from various migrate_stage tables (whose status is 0), create the corresponding *CreateForm(s), or *UpdateForm(s) for each piece of data and call the relevant POST / PUT Cloud APIs on the Syndeia 3.3 server.

Syndeia Cloud Migration Utility

A Syndeia-Migration utility is provided for the migration from Syndeia Cloud 3.2 to 3.3.

Syndeia Migration Utility

This utility is responsible for replicating data from Syndeia Cloud 3.2, enhancing the data, staging it for loading in Syndeia 3.3, and finally loading the data in Syndeia 3.3. This utility is a command-line application and accepts the following command-line arguments:

-r (or --replicate), with the following possible values - None, Repositories, Containers, Artifacts, Relations, Users or All
-e (or --enhance), with the following possible values - None, Repositories, Containers, Artifacts, Relations, Users, RepositoryTypes, ContainerTypes, RelationTypes or All (NOTE: artifact types are automatically enhanced when enhancing artifacts)
-s (or --stage), with the following possible values - None, Repositories, Containers, Artifacts, Relations, Users, RepositoryTypes, ContainerTypes, ArtifactTypes, RelationTypes or All
-l (or --load), with the following possible values - None, Repositories, Containers, Artifacts, Relations, ContainerTypes, ArtifactTypes, Users or All

The conf/application.conf file contained in this utility has to be supplied with the correct values for the source/target databases and whether the source server is LDAP enabled or not. It should also specify the Syndeia 3.3 server IP address and the port and the sign-in username and password for signing in to Syndeia Cloud 3.3 (preferably, this user should have admin rights so that he may create/update any data he likes). The relevant sections are -

target {
  db {
    host = "localhost",
    username = "cassandra-username",
    password = "cassandra-pwd",
    port = 9042
    keyspace = "syndeia_cloud_devops"
  }
}

source {
  db {
    host = "localhost",
    username = "cassandra-username",
    password = "cassandra-pwd",
    port = 9042
    keyspace = "syndeia"
  }

  server {
    isLdapEnabled = false
  }
}

sign-in {
  username = "super.user"
  password = "super.user.pwd"
}

server {
  ip-address = "localhost"
  port = 9000
}

api {
  default-wait-duration = 2
}

Similarly, we need to update a few lines in the bin/syndeia-migration.bat file (or the bin/syndeia-migration file, for Linux / Mac). The following is an example of changes made to the bin/syndeia-migration.batfile; please do the similar changes in bin/syndeia-migration file.

set CFG_OPTS=-Xms1G -Xmx8G
set _JAVA_PARAMS=-Djava.library.path=lib -Dconfig.file=conf/application.conf
set "APP_CLASSPATH=%APP_LIB_DIR%\*;%APP_LIB_DIR%\com.intercax.syndeia-migration-3.3.jar"

Step-by-Step Migration Process

Step 1 - Replicate all data from Syndeia Cloud 3.2

bin\syndeia-migration.bat -r All

Step 2 - Enhance, stage, and load users

bin\syndeia-migration.bat -e Users -s Users -l Users

Step 3 - Enhance repository, container and relation types

bin\syndeia-migration.bat -e RepositoryTypes

bin\syndeia-migration.bat -e ContainerTypes

bin\syndeia-migration.bat -e RelationTypes

Step 4 - Stage repository and relation types

bin\syndeia-migration.bat -s RepositoryTypes

bin\syndeia-migration.bat -s RelationTypes

Step 5 - Enhance, stage, and load repositories

bin\syndeia-migration.bat -e Repositories -s Repositories -l Repositories

Step 6 - Launch the Syndeia 3.3 Standalone client and connect to each of the repositories using (admin) credentials, or the user should have access to all the data in any of the external repositories (servers).

When you launch Syndeia 3.3 Standalone, you’ll see an empty screen because no Syndeia Projects exist yet. So create a Syndeia Project for migration with the following values:

Key: MIGCONT
Name: Migration container
Description: Container for migrating data from Syndeia 3.2 to 3.3, and press Create New button (as shown below).

NOTE: This is a sample project which can be deleted later once this migration activity is complete.

Once you click “Create New” this Syndeia project should be created.

Double-click the newly created Syndeia project and Syndeia dashboard will launch. It will show all the repositories which were migrated from Syndeia 3.2 in the Repository Manager tab. Click on each of the repositories and you might be prompted to enter the password. If the prompt does not appear, then right-click each of the repositories and press “Update…” and enter your credentials there. Once you’ve entered the credentials for all the repositories, you should expand each of the repositories by clicking the “right-pointing triangle” icon. The repositories should look like the following:

The picture above shows the username which is used for connecting to each of the repositories.
NOTE: The user used to connect to any repository, must have access to data in that repository, otherwise that data won’t be migrated.

Step 7 - Enhance containers and stage container types & containers

bin\syndeia-migration.bat -e Containers

bin\syndeia-migration.bat -s ContainerTypes

bin\syndeia-migration.bat -s Containers

Step 8 - Migrate container types & containers

bin\syndeia-migration.bat -l ContainerTypes

bin\syndeia-migration.bat -l Containers

Step 9 - Enhance artifacts and stage artifact types & artifacts

bin\syndeia-migration.bat -e Artifacts

bin\syndeia-migration.bat -s ArtifactTypes

bin\syndeia-migration.bat -s Artifacts

Step 10 - Migrate artifact types & artifacts

bin\syndeia-migration.bat -l ArtifactTypes

bin\syndeia-migration.bat -l Artifacts

Step 11 - Enhance, stage and load relations

bin\syndeia-migration.bat -e Relations -s Relations -l Relations

Migration (3.2 -> 3.3)