WebSphere Liberty, a component of the WebSphere Application Server family of products, adheres to a Single Stream Continuous Deliver (SSCD) Software Support Lifecycle Policy as described below. The WebSphere Application Server traditional component continues to adhere to the Enhanced IBM Software Support Lifecycle Policy and is documented elsewhere (see the Related Information section).
Standard support for Open Liberty, the upstream open source project for WebSphere Liberty, is available through some editions and versions of the WebSphere Application Server family of products. Where this is the case, the Support Lifecycle Policy described herein also applies to Open Liberty when used under the appropriate entitlement.
- There are no differences in functionality between the entitlement provided by WebSphere Application Server versions V8.5.5, WAS V9.0, or any subsequent release -- they all provide entitlement to the same single code stream.
- Differences in Liberty functionality only come from different supported features as provided by the different WebSphere Liberty Editions (eg. Liberty Core, Liberty "Base", Liberty Network Deployment (ND), and Liberty for z/OS).
- There will never be a "version to version" migration for Liberty, its applications or configuration. More information is available in the description of the Liberty zero-migration architecture .
- The single code stream of Liberty eliminates End of Support (EOS) Announcements for Liberty, and therefore there is no need for a Support Extension on Liberty.
|All CD releases
|CD releases ending in
“.3”, “.6”, “.9” or “.12” or starting with “18.”
|For 5 years
|For 5 years
|For 24 weeks
|For 2 years
|Proactive Security Fixes
|Most recent 2
- IBM Support is provided for any Liberty CD update that is not more than five (5) years old. If you are on a Liberty CD update that is more than five years old, you must move to a more current CD update in order to request IBM Support to investigate a problem that you report.
- In general, fixes and new functionality will continue to be provided in Liberty CD updates.
- A fix may also be provided upon request and at IBM's discretion as an interim fix (iFix) to be applied to a recent Liberty CD update if all of the following conditions apply:
- The fix resolves a problem that impacts ongoing production or a committed production start date.
- There is no acceptable workaround for the problem.
- The customer is running with a recent Liberty CD update eligible for interim fixes. Eligible CD updates are limited to:
- Any of the six (6) most recent Liberty CD updates.
- Any of the eight (8) most recent Liberty CD Updates ending in “.3”, “.6”, “.9” or “.12”.
- Fixes for security vulnerabilities will be automatically created and made available for:
- The most recent Liberty CD Update
- The two (2) most recent Liberty CD Updates ending in “.3”, “.6”, “.9” or “.12”.
- From an IBM Support perspective, other than the "eligibility" to receive an iFix, there are no other differences between Liberty CD updates.
- The customer is responsible for ensuring Liberty is running on a supported Java SE environment. Liberty aims to support Java SE versions as long as the Eclipse Adoptium project continues to provide maintained builds of that runtime (see the Adoptium Release Roadmap). This may mean that the Java SE support dates for Liberty and traditional WebSphere Application Server are different. Removal of support of a Java SE version is published in the Knowledge Center Removal notices page - typically these announces are made two years ahead of the removal.
- If Liberty is being run on an operating system release that is no longer within publicly documented production support by the vendor, or with a co-requisite or prerequisite product that is no longer supported, IBM technical support may be limited to defects that can be replicated on currently supported environments. In this situation, the existing 'other configurations' policy continues to apply , and IBM will apply reasonable effort to support your configuration. Liberty will not be tested with co-requisite or prerequisite products that are no longer supported.
Was this topic helpful?
01 November 2023