Follow the steps below to migrate your SysML model from Syndeia 3.2 to Syndeia 3.3. Do not install Syndeia 3.3 until specified in this process.
| Info | ||
|---|---|---|
| ||
Please read each step carefully. Do not skip any step. |
1. Create a backup copy of the following 2 files before you start this process.
...
9. Go to the Repository Manager tab and click on each repository to connect. Provide your credentials during the connection process as shown below. You will need to connect to each repository before you can upgrade connections. Syndeia needs to reach out to the repositories to gather additional data for the sources and targets of the connections before they are upgraded. After you have connected to each repository, go to the next step. Keep the Dashboard open.
8/ 10. Right-click on the top-level element in the SysML model and select Syndeia → Utils → Upgrade Utils → Upgrade to 3.3
Select to Upgrade Connections
5/ You will see upgrade of repositories and connections
6/
3/
Close Dashboard, save MD project, close, reopen, and check num connections, should see the same as above.
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. as shown below. This will start the process of upgrading the connections in the SysML model to Syndeia 3.3.
11. You will see a window titled Upgrading data to Syndeia 3.3, as shown below. The messages in this window will indicate the specific connections being upgraded. Do not close this window and let the process run.
12. After the upgrade process is finished, the upgrade window will close and you will see a Connection Upgrade Summary as shown below in the log window of the Syndeia Dashboard. Note that the number of connections upgraded to Syndeia 3.3 should match the number of connections in the Syndeia 3.2 model (Step 2).
If some of the connections failed to upgrade, you will see warning messages indicating the same in the Connection Upgrade Summary. Check that you are able to connect to the repositories that have the source/target of those connections in the Syndeia Dashboard. Do not close the Dashboard. You can retry Step 10 again. This will attempt to upgrade the non-upgraded connections again.
13. Go to the Connection Search tab in the Syndeia Dashboard and select Get All. You should now see all the connections upgraded to Syndeia 3.3. Note that the number of connections should match the number of upgraded connections in the previous step, and the number of connections you had when you started the upgrade (Step 2).
14. Close the Syndeia Dashboard. This will rewrite the upgraded connections in the SysML model. Save the MagicDraw SysML project and close it. You do not need to close the MagicDraw application.
15. Open the MagicDraw SysML project, right-click on the top-level model element, and select Syndeia → Dashboard to launch the Syndeia Dashboard.
16. Go to the Connection Search tab in the Syndeia Dashboard and click on Get All. This will display all the upgraded Syndeia 3.3 connections. Verify that the number of connections matches the number from Step 13.
Congratulations! You have now migrated your MagicDraw SysML project from Syndeia 3.2 to Syndeia 3.3.
We strongly recommend you to start using Syndeia Cloud for scalability, reliability, and performance.