CMT Differences and Command Mappings
This topic highlights the major benefits provided by GMU (Gateway Migration Utility) over the older CMT (Command Line Migration Tool). It also provides a mapping of the GMU equivalent commands for each CMT command.
gateway
This topic highlights the major benefits provided by GMU (Gateway Migration Utility) over the older CMT (Command Line Migration Tool). It also provides a mapping of the GMU equivalent commands for each CMT command.
The CMT is the predecessor to GMU and is no longer supported officially by CA Technologies. This topic is intended to help those familiar with CMT transition to GMU.
GMU Highlights
GMU is nearly equivalent to the Command Line Migration Tool (CMT) 2.4, and provides these additional features:
- Better performance, especially during import, export, and dependency analysis
- Gracefully handles failed imports (all or nothing) so theCA API Gatewayis not left in an unstable state
- Supports encoded password and mutual authentication
- Flexible mapping options that reduce the risk of overwriting environment-specific values: New, Update, Existing, ForceNew, Delete, Ignore, NewOrExisting, NewOrUpdate, DeleteOrIgnore
- Entity values are grouped in the template.properties file making it easier to edit
- Ability to export encrypted secure passwords and private keys
CMT to GMU Command Mapping
Operations | CMT Command | GMU and Equivalent |
Entities | ||
listEntities Lists entities with search filters | list | |
exportEntity Exports a single entity | restman GET <resource > | |
importEntity Creates or updates a specific entity | restman PUT <resource >/<id > or restman POST <resource > | |
deleteEntity Deletes a single entity | restman DELETE <resource >/<id > | |
Templatization | ||
templatize Templatizes exported contents | template | |
detemplatize Puts templated values back into exported contents | migrateIn with --template argumentor detemplate | |
Migration | ||
migrateOut Exports the objects and their dependencies (= exportObjects + exportDependencies) | migrateOut (full or partial Gateway configurations) | |
migrateIn Imports the content of migrateOut | migrateIn (full or partial Gateway configurations) | |
Delete | ||
DeleteObjects Deletes folder/policy/service and or their dependencies. | The equivalent in GMU uses the following commands. migrateOut (specified entities)manageMappings --action=delete (change all entities to delete)migrateIn | |
Objects | ||
listObjects Lists all objects under a folder | ||
exportObjects Exports only service/policy/folder contents | migrateOut (with specified entities) | |
importObjects Imports a directory of objects to a folder | migrateIn | |
Dependencies | ||
listDependencies List dependencies for service/policy/folders | restman GET <resource >/dependencies | |
importDependencies Imports exported referenced dependencies | migrateIn | |
exportDependencies Exports referenced dependencies | migrateOut | |
createMap Creates mappings for a bundle | Output from m igrateOut | |
testMap Validates an existing dependency mapping file and identifies missing dependency mappings | migrateIn with --test argument | |
Miscellaneous | ||
enableService Enables or disables a service | restman PUT services/{id}restman PUT policies/{id}MigrateIn with the --deactivate argument (do not activate updated services or polices). | |
Reset Deletes all entities that are not on the whitelist | manageMappings --action Delete . | |
Info Lists build info, compatible CA API Gateway versions, available entity types | No equivalent. | |
search Searches a CA API Gateway for a text string | No equivalent. | |