3.2 Local -> 3.3 Local.

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. 

1. Create a backup copy of the following two files before you start this process.

1. SysML model that you will be migrating
2. repos.info file in the .syndeia folder in your home directory, e.g. C:\Users\Username\.syndeia\repos.info on Windows.

If you make a mistake during this process, copy the backup files and start this process again. 

2. Open the Rhapsody SysML model that was used/created with Syndeia 3.2, and launch the Syndeia Dashboard. Go to the Connection Search tab and press the Get All button. Note the number of connections. In this case, we will be demonstrating the migration process on a model with 140 connections. After migration to Syndeia 3.3, you will need to verify the number of connections.

3. Close the Syndeia Dashboard, SysML model, and the Rhapsody application.

4. Follow the installation instructions here to install Syndeia 3.3 plugin for Rhapsody. Note that you will need a new license file for Syndeia 3.3. 

5. After installation, start Rhapsody, right-click on any element in the model tree and select Syndeia → Settings. Do not launch the Dashboard yet.

6. Check that the setting Select primary store is set to SYSML_MODEL as shown below. If not, change to SYSML_MODEL and click on the Apply button. Close the Settings window.

7. Right-click on the top-level model element in your model and select Syndeia → Dashboard. This will launch the Syndeia Dashboard. During the launch process, your repositories will be upgraded from Syndeia 3.2 to Syndeia 3.3 format. During this repository upgrade process, only repositories with unique host addresses will be retained. For example, if you had two GitHub repositories GitHub 1 and GitHub 2 with the same host URL, then only one of them will be retained and show up in the Repository Manager when the Dashboard launches, as shown below. The other one will be marked as a duplicate. 

8. Go to the Connection Search tab in the Syndeia Dashboard and click on the Get All button. You will see 0 connections. This is because the connections saved in the SysML model have not yet been upgraded from Syndeia 3.2 to Syndeia 3.3 yet. We will do that in the next step.

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.

10. Right-click on the top-level element in the SysML model and select Syndeia → Utils → Upgrade Utils → Upgrade to 3.3 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 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).

14. Close the Syndeia Dashboard. This will rewrite the upgraded connections in the SysML model. Save the Rhapsody SysML project and close it. You do not need to close the Rhapsody application.

15. Open the Rhapsody SysML project, right-click on the top-level model element, and select Syndeia → Dashboard to launch the Syndeia Dashboard.

16. 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 Rhapsody SysML model next time, the updated repository names will be saved locally.

Congratulations! You have now migrated your Rhapsody SysML project from Syndeia 3.2 to Syndeia 3.3.