Users working with Syndeia 3.2 3 in local mode can also migrate data to Syndeia Cloud and start working in cloud mode. Follow the instructions steps below carefully to migrate your local project Syndeia data saved locally (SysML models and repos.info file) to Syndeia Cloud.
PrerequisitePrerequisites:
- Syndeia information in the Your MagicDraw SysML project should either have has been created with (or using) Syndeia 3.2 or migrated successfully 3, or has been upgraded from Syndeia 3.1 2 local store to Syndeia 3.2 3 local store using the process specified here.
- You have an account on Syndeia Cloud 3.3 that has permissions to create and update all types of Syndeia resources (Repository, Container, Artifact, Relation, and Types) except Users.
1. Open the MagicDraw SysML project that you are using with Syndeia 3.3.
2. Right-click on any SysML element in the model tree and select Syndeia → Settings. Check and update Syndeia settings as described below.
| Info | ||
|---|---|---|
| ||
| You must press Enter after you update settings that take a text-based value. Click on the Apply button after you have made all the changes. |
- Select primary store = SYSML_MODEL. This is the default mode in which we will first launch the Syndeia Dashboard.
- Protocol = http (or https) depending on your Syndeia Cloud 3.3 installation. Press Enter if you update this value.
- Authentication protocol = BASIC (or LDAP) depending on your Syndeia Cloud 3.3 installation
- Hostname = hostname of your Syndeia Cloud 3.3 server, e.g. mySyndeiaCloud33.myOrg.com. Press Enter if you update this value.
- Port = 9000 if the protocol is http, or 9443 if the protocol is https.
- Username = Username for your account on Syndeia Cloud 3.3
- Password = Password for your account on Syndeia Cloud 3.3
3. Set the following in the Settings tabRight-click on any SysML element in the model tree and select Syndeia → Settings. Check that "Select primary store" is set to SYSML_MODEL as shown below.
(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
(1) Right click on a SysML element in the model tree and select Syndeia → Utils → Upgrade Utils → Push to Syndeia Cloud
...