3.1 -> 3.2

Owned by Manas Bajaj
Last updated: Apr 14, 2018
3 min read

Users can upgrade Syndeia data created using Syndeia 3.1 to work with Syndeia 3.2. This Syndeia data primarily includes connections stored in SysML model and repositories stored in .syndeia folder. Follow the steps below to upgrade your models from Syndeia 3.1 to Syndeia 3.2.

(1) Open SysML project.

(2) Right click on any SysML element in the model tree and select Syndeia → Settings. Check that "Select primary store" is set to SYSML_MODEL.

(3) Launch Syndeia Dashboard - Right click on any SysML element in the model tree and select Syndeia → Dashboard. In the log window of the Syndeia Dashboard, you will see some stats. Syndeia will detect that the connections stored in the SysML model and repositories in the .syndeia folder are in an older format, and it will automatically upgrade connections to the 3.2 format. In this example, 173 connections were upgraded.

(4) Click on every repository listed in the Repository Manager to check that you can connect to it.

(5) Syndeia 3.2 needs more information from the connected models and repositories compared to Syndeia 3.1. Although all Syndeia information was upgraded to Syndeia 3.2 format (syntactic upgrade) in the previous step, we still to enrich that information. Right click on any element in the SysML model tree and select Syndeia → Utils → Upgrade Utils → Upgrade to 3.2, as shown below, to start the enrichment process..

(6) A new status dialog will pop up and show the running log as each connection is upgraded after fetching additional data from the connected models. After the process is over, you will see a summary of the upgrade in the Syndeia Dashboard, as shown below. The summary will show you the following stats:

  • Total number of connections
  • Number of connections that are upgraded, including connections that were already upgraded and those upgraded in this round
  • Number of connections that could not be upgraded

If the source / target end of the connection is missing, then the connection cannot be upgraded. For example, in the above scenario, 1 connection could not be upgraded because the target end of the connection is a local folder which is not available at the specified location. If that folder is made available at the specified location and the upgrade process is run again (next round), then the connection can be fully upgraded.