News
Abstract
This page of API Connect: Upgrade Central describes information to guide you on a successful journey from IBM API Connect to IBM Cloud Pak for Integration. Check back regularly for more information on how to migrate your API Management Solution from previous versions of IBM API Connect to a multi-style integration platform that provides a single experience with flexibility to deploy multiple types of integrations, API Management, App Integration, Messaging, Events, and more. You will learn an overview of how to migrate, the choices available, with links to detailed resources and tools to complete a migration.
Content
Tab navigation
What is IBM Cloud Pak for Integration?
IBM Cloud Pak for Integration® is a hybrid integration platform with an automated, closed-loop approach that supports multiple styles of integration within a single, unified experience. Unlock business data and assets as APIs, connect cloud and on-premise applications, reliably move data with enterprise messaging, deliver real-time event interactions, transfer data across any cloud and more. Included with IBM Cloud Pak for Integration is API Management, which is provided by v10 of API Connect. Some additional capabilities are only available under Cloud Pak for Integration entitlement. Learn more about IBM Cloud Pak for Integration and read client stories including CVS Health.
Migrating an API Connect deployment to IBM Cloud Pak for Integration
This page focuses on migrating your data from a stand-alone API Connect deployment to a new Cloud Pak for Integration (CP4I) topology on OpenShift, where the API Management capability has also been deployed. In this case, v10 of API Connect is deployed to provide the API Management capability. While other possible deployment patterns are licensed, such as deploying API Connect stand-alone as bundled software, this page will not focus on those. You can find information on moving from previous versions of API Connect to v10 stand-alone on the tabs above.
If you are already on a previous version of IBM Cloud Pak for Integration and are seeking to upgrade to newer versions, see Upgrading capabilities and runtimes.
Licensing considerations
Migrating from one program to another, in this case to Cloud Pak for Integration, requires changes to your license entitlement. For existing customers who purchased IBM API Connect Enterprise Edition PVU, there are two options to consider when planning a move to v10. PVU (processor value units) is a capacity measure of compute cores. While you can simply move forward to a newer release of the same program, API Connect, using existing licensed entitlements, there are two options to consider, specific to migrating to IBM Cloud Pak for Integration. Contact your IBM sales rep for more details on pricing.
- If you are consuming (or plan to consume) multiple styles of Integration (API integration, App Integration, Messaging, Eventing) you can upgrade from IBM API Connect Enterprise PVU licenses to Cloud Pak for Integration. This provides a single experience with pricing flexibility to deploy multiple integration capabilities based on Virtual Processor Cores (VPC). Unlike PVU deployments, all cores are counted equally with VPCs. Cloud Pak for Integration can be perpetual or subscription licenses. Cloud Pak for Integration licenses include OpenShift entitlement for deployment of CP4I.
- Many customers are seeking an OpEx cost model and licensing based on API consumption instead of compute capacity. You can upgrade from IBM API Connect Enterprise PVU licenses to Cloud Pak for Integration with an add-on Subscription based on API Call volumes. This can simplify planning for growth based on business metrics like API consumption instead of a capacity measure of compute cores. This approach may also be more cost effective for some highly available API Management topologies, hybrid and multi-cloud deployments.
Migrating from IBM API Connect v5
The API Connect Migration Utility (AMU) is capable of extracting data from an API Connect v5 deployment and enabling migration to Cloud Pak for Integration. Because a version migration is completed, it is possible to move your v5 data (using the AMU tooling) to v10 of API Connect on OpenShift deployed as part of a CP4I deployment. Please see the v5 to v10 page for all details which describe an overview of the process, with links to detailed resources and tools to learn, plan and complete a migration.
Migrate an on-premises deployment of IBM API Connect V5 or V10 to IBM Cloud Pak for Integration.
Links & instructions for migrating from IBM API Connect v5 to IBM Cloud Pak for Integration can be found in the
API Connect transformation guide in the IBM Documentation Center for Cloud Pak for Integration.
Moving from IBM API Connect v2018 to IBM Cloud Pak for Integration.
This path is not currently supported. This requires the ability to move from one deployment form factor such as VMware OVAs or other Kubernetes platforms to Cloud Pak for Integration running on OpenShift anywhere. That support is not available at this time.
[{"Type":"SW","Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSMNED","label":"IBM API Connect"},"ARM Category":[{"code":"a8m50000000L0rvAAC","label":"API Connect"}],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"All Version(s)"}]
Was this topic helpful?
Document Information
Modified date:
05 January 2022
UID
ibm16453589