GMU Command Help
The following table shows steps for a simple migration workflow. The GMU commands highlight important arguments.
gateway83
Basic Migration Workflow
The following table shows steps for a simple migration workflow. The GMU commands highlight important arguments.
Step | Task | GMU Command Highlights |
1 | Export all entities of a Gateway. | migrateOut --all |
2 | Test the import, but do not commit the migration. Save results to an XML file. | migrateIn --bundle bundleimport.xml --test --results testresults.xml |
3 | Review testresults.xml to find conflicts. Find entities for mapping to the target Gateway. | list or browse |
4 | Prepare the mappings file to resolve conflicts that are uncovered during the test import. | manageMappings --outputFile mappings.xml |
5 | Test import with new mappings. | migrateIn --test --map overrideMappings.xml |
6 | Repeat steps 4 and 5 until all mapping conflicts are resolved. | |
7 | Commit the migration with the new mappings. Save mappings.xml for future migrations. | migrateIn --map overrideMappings.xml --results migrateResults.xml |
For a more advanced migration workflow, see
Migration Example
.Entity Names
All entity names are case insensitive. For example, for readability, ENCAPSULATED_ASSERTION is uppercase, but is not required.
$ ./GatewayMigrationUtility.sh manageMappings --bundle rename.xml --type ENCAPSULATED_ASSERTION --srcName MyEncass --targetGuid c079fc4f-3e04-4231-b2e9-9834ef7bceb1