News
Abstract
This page of API Connect: Upgrade Central describes information to guide you on a successful journey from v2018 to v10. You will learn an overview of how moving versions will depend on the type of deployment you chose. You will learn about the process, considerations, and links to resources and tools to help you learn, plan and complete your move.
Content
Tab navigation
Announcement: API Connect v2018 End of Support (EOS) is April 30, 2023. Support Extensions are not available for purchase.
The process for moving from v2018 to v10 will depend on the choices you made when first deploying v2018. Those two choices were the deployment form factor and the type of API gateway service selected (v5c or native API gateway).
v2018 introduced new architecture and topologies that provided greater flexibility in deploying the product through cloud-native architecture and container orchestration. Three deployment form factors were supported in v2018. Each deployment form factor includes a specific path to v10.
3 Important facts:
- You can move to v10 within the same deployment form factor as your current v2018 deployment. To move across form factors see. In addition, your gateway types will remain the same (v5c gateway service or native API gateway service).
- Moving from v2018 to v10 is performed using v10.0.1.2+. You can then continue to upgrade v10 to 10.0.2+, see the v10-currency tab for those details.
- There is a 1:1 mapping between a v2018 fix pack and a corresponding v10.0.1.x fix pack that allows upgrade. Always reference v2018 to v10 upgrade paths for latest combinations of supported upgrade paths. It is typical that you will upgrade v2018 in order to move to v10.
Supported paths:
| v2018 deployment | Approach | IBM Documentation | Notes |
|---|---|---|---|
| OpenShift 4 | Upgrade ** | Link to task steps |
Must be on a specific
v2018.4.1.x fix pack
|
| Kubernetes | Upgrade ** | Link to task steps |
Must be on a specific
v2018.4.1.x fix pack
|
| VMware OVA | Version migration * | Link to task steps |
Must be on a specific
v2018.4.1.x fix pack
|
Definitions:
* Version migration is a 2 step process where you install a new version of software on new infrastructure and then move/load data from the previous version.
** Upgrade is the act of applying software updates in-place, on its existing infrastructure. Upgrades may first require system prerequisites to be updated. examples include OpenShift or K8s versions.
Infrastructure referenced in definitions refers to: VMware virtual appliances, different OpenShift clusters or K8s clusters.
Example of releases and paths forward:
Process Overview:
For v2018 deployed on OpenShift 4 or other Kubernetes platforms:
Follow IBM documentation to learn and complete the upgrade:
For v2018 deployed on VMware OVAs:
Follow IBM documentation to learn and complete the version migration: Link to task steps.
- Important Fact: API Gateways, while included in the task steps above, when deployed on VMware OVAs or physical DataPower appliances, you will simply upgrade the appliance firmware. Just like in the picture, upgrading the appliance firmware must occur after the other API Connect components are upgrades (Manager, Portal and Analytics first). Link to documentation on versioning compatibility and upgrading appliance firmware from v2018 to v10 for DataPower Gateway Virtual Edition. This differs from the other v2018 API Connect subsystems deployed on VMware OVAs.
Reviewing system requirements (IBM Software Compatibility Reports)
You should compare the specific system requirements needed for the specific v2018 fix pack and v10.0.1.x you plan to move to. By selecting system requirements that match both v2018 and v10 will reduce the prerequisite upgrade requirements. An example of a system requirement is OpenShift version or K8s version.
IBM Support:
If a problem occurs with an upgrade or a version migration, IBM Support is always here.
- Open a Support Case if needed with IBM API Connect Support
- MustGather Documents:
- Troubleshooting resources:
- Troubleshooting failures on Kubernetes
- Troubleshooting installation and upgrade on OpenShift
[{"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:
06 February 2023
UID
ibm16442169