Plan how you will migrate your v5-compatible APIs and then test the process.
About this task
Plan the migration process, migrate a small set of APIs, and then test the results. You can
refine settings and repeat the process as needed.
Procedure
- Review all of the migration topics to ensure you understand the requirements, the general
process, and important considerations.
-
Plan how you will migrate your v5-compatible APIs to the DataPower Gateway.
Make sure you know exactly which APIs you want to migrate, and in which provider organizations
and catalogs they are stored.
-
Migrate a proof-of-concept deployment.
Migrate 10 to 20 of your most commonly used v5-compatible APIs to ensure that your migration
tools are configured correctly and the migration process works as intended. Plan to run several test
iterations of migration.
You can use the migration utility's --dry-run option to perform iterations of
the migration push without actually uploading data to API Connect. The test runs offer an
opportunity to test for errors and warnings that need to be resolved before you perform the actual
data push.
You can use the migration utility's --move-subscriptions parameter to move subscriptions during the push operation that uploads converted data back into API
Connect.
- Test the APIs that you migrated as proof-of-concept.
Testing the migrated APIs helps you to determine which migration utility settings you need for
successfully converting the v5-compatible APIs to DataPower API Gateway. If needed, you can move or
delete the results, modify the configuration settings, and run the migration again. When you rerun
the migration port command using the same target folder for output, the utility
skips artifacts that have already been converted to DataPower API Gateway.