MMS3 to MMS4 migration [Draft]

Step	Description

Step	Description
Ensure you have “writer” permissions for MMS3 and MMS4 project
Ensure MMS3 and TWC are in sync	Note: Make sure you are using CSM/MDK version 4.5.3 or earlier for all of the steps in the "Prep for Migration" phase. *Note: Updating project usages before completing these steps may reduce validation errors. Lock the model for edit: right click the root "Model" package and select Lock -> Lock Elements for Edit Recursively. On the main toolbar, click Collaborate -> Update Project. Right click the root "Model" package and select MMS -> Validate Models. If there are any errors thrown, resolve them (slot errors or errors related to project usages may be ignored). Right click each View Editor document in the model and select MMS -> Validate Models. The "Element Validation" window will appear and display the errors (if there are any errors found). If there are any errors thrown, resolve them. Commit changes to TWC: click Collaborate -> Commit Changes to Server. In the "Comment" field, include a note that describes any updates you made.
Export View Editor HTML or PDF documents on MMS3	Login to MMS3 View Editor: https://opencae.jpl.nasa.gov/alfresco/mmsapp/mms.html#/login For each View Editor document in your model, do steps 3-5. Click the icon that looks like a paper (view full document) and scroll down to check that all of the contents of the document are there. Right click the document itself (in the whitespace) and select Save As -> under "Format" select "Webpage, HTML Only" in the dropdown. Save the file locally.
Delete “__MMSSync__” Folder	Lock the model for edit in TWC Delete "MMSSync" package in the containment tree
Remove MMS Stereotype from root “Model” Package	Right click the root "Model" package and select Specification. In the "Applied Stereotype" field, delete the <<ModelManagementSystem>> stereotype. Log out of MMS.
Commit Changes to TWC	Expected outcome: notification window doesn't print element validation summary
Close TWC project
run ID migration scripts as jython macros one by one https://github.com/Open-MBEE/_OpenMBEE-Documentation/tree/master/migration/crush2donbot/TWC	when uploading/moving a project from local or from another TWC server, CSM changes the IDs which are not compatible with VE crossreferences. The scripts revert those IDs
Open CSM with MDK with MMS Enabled	**Note: Make sure you are using MDK version 5.1.0 or later for all of the steps in the "Execute Migration" phase. Open CSM Login to TWC Open your project in TWC
Configure MMS in project options	Set URLs for MMS4 and VE4
Login to MMS	Select "MMS" tab from top ribbon -> Login -> Enter username and password -> Ok
Right Click Root Element → MMS → Validate Models	Right click the root "Model" package and select MMS -> Validate Models **Note: Validation may take awhile if it is a bigger model.
Wait for Validation Window to Print Errors/Warnings	**Note: Validation may take awhile if it is a bigger model.
Right Click Error in Validation Window → Commit Project and Model	Note: Error will remain visible until validation window is closed
Choose MMS Org	Wait for "Choose MMS Org" dialog to pop up -> Select desired Org -> Ok
Again, Right Click Root Element → MMS → Validate Models	Right click the root "Model" package and select MMS -> Validate Models **Note: Validation may take awhile if it is a bigger model.
Wait for Validation Window to see “Holding bin missing in client”	Can skip if Holding bin exists, otherwise choose “update from MMS”
Confirm that “__MMSSync__” folder has been created
Save Project locally by “File->Save Project”
Commit Changes to TWC
Again, Right Click Root Element → MMS → Validate Models
Run Presentation Element migration script	follow the readme here https://github.com/Open-MBEE/mms3-to-mms4-json
Log into VE and check that org and project exist
Run Validation on CSM side	should see zero differences
Check View Editor for Errors	Go to the View Editor page for the project Do a quick check of all of the views and documents to make sure there aren't any errors or data lost
Generate Model views	Right click all the Documents in the model and select "MMS->Generate Views Recursively" Check these Documents on View Editor again and verify they look consistent Generate cover page view
Confirm VE Content (Except Artifacts)
Run Artifact Migration Script	for ve added images, follow this script https://github.com/Open-MBEE/mms3-to-mms4-json/tree/master/images
Again, Right Click Root Element → MMS → Validate Models
Confirm VE Shows All Content
Check that project cover page migrated correctly
Run Csync by Committing to TWC
Generate Model views	Right click all the Documents in the model and select "MMS->Generate Views Recursively" Check these Documents on View Editor again and verify they look consistent Generate cover page view
Confirm VE Shows All Content
Export VE HTML/PDF documents on MMS4
Diff HTML/PDF Documents MMS3 vs MMS4
Configure permissions for MMS4 project