migrateIn command
All results of a migrateIn command are stored in an XML results file. Use the <results>.xml file to view actions that are performed on the Gateway, identify conflicts, and resolve them. Common conflicts are:
gateway83
Purpose and Usage |
Use to import (create/update/delete entities) to:
Key Features :
|
Output Files for Import
All results of a file. Use the
migrateIn
command are stored in an XML results<results>.xml
file to view actions that are performed on the Gateway, identify conflicts, and resolve them. Common conflicts are:- Target entity already exists
- Target entity not found
- Unique key conflict (usually name)
- Cannot replace dependency
- Invalid resource when updating an entity
Example: Test an import
Migrate bundle.xml (single file) created from a
migrateOut
command.$ ./GatewayMigrationUtility.sh migrateIn --argFile commonarguments.properties --bundle bundle.xml --results results.xml --test
Example: Basic import, save results in results.xml file
$ ./GatewayMigrationUtility.sh migrateIn --argFile commonarguments.properties --bundle bundle.xml --results results.xml
Example: Import to a folder (maps root folder in the bundle to target folder)
$ ./GatewayMigrationUtility.sh migrateIn --argFile commonarguments.properties --bundle bundle.xml --results results.xml --destFolder '/path/to/target/folder'
Example: Import using a templated bundle
$ ./GatewayMigrationUtility.sh migrateIn --argFile commonarguments.properties --bundle templatedBundle.xml --results results.xml --template template.properties
Example: Import using an override mappings file
$ ./GatewayMigrationUtility.sh migrateIn --argFile commonarguments.properties --bundle bundle.xml --results results.xml --map overrideMappings.xml
Example: Import bundle without changing the active version of the updated services and policies
$ ./GatewayMigrationUtility.sh migrateIn --argFile commonarguments.properties --bundle bundle.xml --results results.xml --deactivate true