IBM DataPower Operations Dashboard (DPOD) uses the standard version format for Maintenance Delivery Vehicle (MDV). The product numbering is based on the IBM Version, Release, Modification and Fix Level structure within the V.R.M.F format. More information is available at https://www.ibm.com/support/pages/ibm-software-product-versioning-explained.

Release Strategy

• Refresh packs / Fix packs are released at least twice per quarter.

• Only the latest 2 refresh packs are supported.

• Support for older refresh packs (refresh packs that are no longer supported) is limited to solving upgrade issues only, and for a duration of 6 months after a refresh pack is no longer supported.

• Fix packs and Interim fixes (iFixes) with security fixes (vulnerability remediation) and bug fixes will be provided for the latest refresh pack only.

Support Prerequisites

• The hardware and software requirements of DPOD are met, as documented in the product documentation.

• The firmware versions of the DataPower Gateways monitored by DPOD are supported by IBM (more information is available at https://www.ibm.com/support/pages/ibm-datapower-gateways-firmware-support-lifecycle).

• The versions of API Connect monitored by DPOD are supported by IBM (more information is available at https://www.ibm.com/support/pages/ibm-api-connect-support-lifecycle-policy).

• The customer will need to provide a MustGather file for the analysis of the support team (more information is available at Generating MustGather).

• Security vulnerability issues should follow the procedure at MustGather: Security Vulnerability Issues.

• DPOD and Red Hat OpenShift version compatibility objective:

  • The DPOD Cloud Agent will support the latest OpenShift EUS minor version (e.g. 4.14) within 90 days of its release, for the duration of its support period.

  • To stay current with the updated Red Hat OCP lifecycle policy (https://cloud.redhat.com/blog/time-is-on-your-side-a-change-to-the-openshift-4-lifecycle), EUS versions are even minor releases beginning with 4.8.

Releases

DPOD customers can use the following tables to track how long their version, release and modification are supported. By using the information in this table, customers can effectively plan their investment without gaps in support. Customers are responsible for completing migration activities to currently supported levels before a release or modification level reaches end-of-support.