Question & Answer
Question
What are the supported upgrade paths between the supported versions of IBM API Connect?
Answer
The IBM API Connect on-premise offering has a continuous delivery model that provides regular product updates on a frequent basis.
These deliverables take the form of modification release levels; for example, 5.0.0, 5.0.1.
From time to time, IBM API Connect will also indicate that a particular modification level is designated as a Long Term Supported (LTS) Release, and therefore receives an extended period of support. See the Software Support Lifecycle for a full description of this process.
To adopt this continuous delivery model, and to ensure a stable transition, only upgrade paths between particular product levels are supported.
These upgrade paths are summarized below:
| Starting Version(s) | Supported Upgrade Path |
| 4.0.4.6 | 5.0.6.x or 5.0.8.x |
| 5.0.0.x | 5.0.6.x or 5.0.8.x |
Note: The migration of analytics data from Version 4 is supported only up to and including Version 5.0.6.6. If you want to upgrade from Version 4.0.4.6 to Version 5.0.8.2 and keep your historical analytics data, you must upgrade first to Version 5.0.6.6. If you choose an upgrade path that does not migrate Analytics data and you want to save the historical analytics data, you can copy the V4 Analytics data from Version 4 using the API Manager UI
(see https://www.ibm.com/support/knowledgecenter/SSWHYP_4.0.0/com.ibm.apimgmt.apionprem.doc/task_APIonPrem_exportanalytics.html )
or REST APIs
(see https://www.ibm.com/support/knowledgecenter/SSWHYP_4.0.0/com.ibm.apimgmt.apionprem.doc/tapim_exportanalytics_api_calls.html).
An example:
Starting Version is 4.0.4.6.
End goal is 5.0.8.2
Supported upgrade path is 4.0.4.6 -> 5.0.6.6 -> 5.0.8.2 (will maintain historical analytics data)
Reference material:
Was this topic helpful?
Document Information
Modified date:
15 June 2018
UID
swg21984408