Migrating from API Connect V5
Migrate from API Connect V5 to API Connect V10 as a capability of Cloud Pak for Integration.
The migration model is centered around using tooling to bring the contents of V5 catalogs into a V10 (Cloud Pak for Integration) deployment that is set up to import them. The tooling migrates provider organization configuration information, including APIs, Catalogs, Products, Consumers, subscriptions, user registries, and more.
You use a V5 extract command to gather the V5 data, and then use a migration unpack command to
convert the data into V10 format. This extraction will generate a
where your V5 data will be represented as YAML files. By viewing the contents of the
cloud folder, you can see which structures, such as provider organizations, are
needed to support your catalog.
The model recognizes that not all V5 data is applicable to a new V10 deployment. You can use a text editor to remove unneeded or obsolete V5 configurations from the converted file. When you install and configure your V10 management server, you manually create those structures. You can then use migration tooling to load the V5 data into the prepared V10 system.
You must have system administrator privileges on both the old and new deployments to complete a migration. You should be familiar with API Connect V5 architecture and requirements, and with the Cloud Pak for Integration deployment configuration.