...
1. Create a backup copy of the following 2 two files before you start this process.
...
13. Go to the Connection Search tab in the Syndeia Dashboard and select the Get All button. 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).
...
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.. Repeat Step 13 and re-verify the number of connections.
17. Optional - In Syndeia 3.3, you can rename repositories. Uniqueness constraint is enforced on the URL of the repository and not the name, unlike Syndeia 3.2. To rename a repository, you can right-click on the repository and select Update. Specify the new name of the repository and click the Update button. When you close the Dashboard and the MagicDraw SysML model next time, the updated repository names will be saved locally.
Congratulations! You have now migrated your MagicDraw SysML project from Syndeia 3.2 to Syndeia 3.3.
...
| Info | ||
|---|---|---|
| ||
We strongly recommend using Syndeia with Syndeia Cloud for scalability, reliability, and performance. Syndeia usage with a local store should only be used for evaluation purposes. |