What's new in the current release (version 2020.3.1)

Deprecated features

Support for Helm-based deployment and management of capabilities

Cloud Pak for Integration 2020.3.1 deprecates the deployment and management of Helm-based capability deployment. The ability to deploy and manage Helm-based capabilities will be removed in Cloud Pak for Integration 2020.4.1.

New features

Support for Operators and improved Operator installation

Cloud Pak for Integration 2020.3.1 builds on and enhances the existing support for Operators, which enable the simplified deployment and operation of components on the Red Hat OpenShift Container Platform. Updated tooling and UI improvements enable users to install Cloud Pak for Integration with minimal user expertise. Operators now allow organizations to define Cloud Pak for Integration capabilities and then deploy them as required, with added user assistance and feedback to reduce errors.

Support for deployment on Linux on IBM Z IFL engines

Organizations can now deploy some components of Cloud Pak for Integration 2020.3.1 on Linux on IBM Z hardware. Cloud Pak for Integration 2020.3.1 runs on Red Hat OpenShift in this environment, and provides many of the same features as Cloud Pak for Integration running on x86 hardware.

These components are available on Linux on IBM Z:
  • Platform Navigator
  • App Connect Dashboard
  • Event Streams
  • Aspera HSTS
  • MQ

These components are not available on Linux on IBM Z:

  • API Connect
  • DataPower Gateway
  • Cloud Pak for Integration Asset Repository
  • Cloud Pak for Integration Operations Dashboard
  • App Connect Designer

Access to demo examples

Cloud Pak for Integration 2020.3.1 introduces a new repository of demos to help organizations configure and run real integration examples easily and quickly. These are self-contained examples with a set of instructions that not only help explain how to run the demo, but also how to use the demo example to build the organization's own working integration deployment, using the included features of Cloud Pak for Integration.

Support for Portworx as a storage provider

Access to storage is a critical part of an integration solution. Cloud Pak for Integration 2020.3.1 adds support for Portworx across Cloud Pak for Integration components. This lets organizations make their choice of a Kubernetes native storage provider, which can be deployed in their environment of choice and used by Cloud Pak for Integration components.

App Connect Designer assets now displayed in the Asset Repository

In the Asset Repository, an App Connect Designer asset now includes a graphical representation of the flow and metadata to help you easily identify the target apps in the flow.

Custom label support for Cloud Pak for Integration pods

Custom labels and annotations can be specified in the custom resource when deploying Cloud Pak for Integration components that are applied to the Kubernetes pods that are created by the operators.

Custom node placement support for Cloud Pak for Integration pods

Custom node placement can be achieved by specifying either custom node selectors or custom node affinity rules in the custom resource when deploying Cloud Pak for Integration components.

New releases of Cloud Pak for Integration components

This release of Cloud Pak for Integration includes the following component product versions:

For information about previous releases, see the Knowledge Center for release 2020.2 and earlier.