What's new in IBM Cloud Pak for Integration 16.1.2

Find out about new features and improvements in IBM Cloud Pak® for Integration.

New features

Cloud Pak for Integration version 16.1.2 adds the following enhancements:

The IBM Cloud Pak Platform UI can now be installed on Azure Kubernetes Service

The Platform UI is now available to install on Azure Kubernetes Service ( AKS ) to manage the integration products and instance types that are already supported on AKS . You can install the IBM Cloud Pak for Integration operator by using a Helm chart. For more information, see Operating environment and Installing on Azure Kubernetes Service ( AKS ).

Manage instances across multiple locations

Use a single Platform UI to view instances across multiple locations (OpenShift clusters and namespaces) where those instances are deployed, with a minimal footprint for your OpenShift clusters. Each instance is listed on the home page of the Platform UI with its corresponding location name. For more information, see Managing instances across multiple locations.

Use Automation assets templates to create nodes on the canvas

A new Add node from template button on the canvas allows you to create a node (an instance or resource) by using a template from Automation assets. For more information, see Using the assembly canvas.

Managing Event Processing instances in the Platform UI

You can now access, create, view, and manage Event Processing instances in the Platform UI without having to open the Red Hat OpenShift console.

Authorization roles for instance types are recognized by the Platform UI

The Platform UI allows users to administer or view instance types that they have been given access to. In previous fix packs, these roles were not honored by the Platform UI. This feature restores use cases that were possible before Cloud Pak for Integration began using Keycloak for identify and access management. For more information, see Cloud Pak roles and permissions.

Fine-grained access control for instances in the Platform UI

New granular roles and permissions apply to specific instances and resources in the Platform UI. These permissions allow users to administer or view content for those instances and resources. Also, users with viewer permissions can get the instance definition by opening the overflow menu for a given instance. For more information, see Cloud Pak roles and permissions.

New remote repositories are available by default in Automation assets

Two remote repositories are now automatically available in Automation assets. One repository provides APIs and event-driven flows for use with Integration design instances; the other provides tutorials and example templates for developing integrations. For more information, see Using Automation assets.

Managing API Connect subsystems in the Platform UI

You can now create, view, and manage API Managers, API Analytics, API Portals, and API Gateways in the Platform UI without having to open the Red Hat OpenShift console.

API Connect subsystems are nested under their respective API Connect cluster. They appear as stand-alone entries if they are not part of a specific API Connect cluster.

Keycloak 26 is now available for identify and access management

When you update the Cloud Pak for Integration to version 16.1.2, Keycloak upgrades to version 26. For more information on release notes for Keycloak 26, see Release Notes in the Red Hat build of Keycloak documentation.

Enhancements to the upgrade plan

The upgrade plan now ensures that the required Keycloak version has been applied by Cloud Pak foundational services. It also incorporates upgrades to Event Processing and Flink during the upgrade process.

To get updates between releases:

Important announcements - Sign up at My Notifications.

Tips on getting the most out of Cloud Pak for Integration capabilities - Go to Cloud Pak for Integration Community Blog.

The latest fix pack versions - See "Catalog sources for operators" in Adding catalog sources to an OpenShift cluster.

Product changes

Cloud Pak for Integration can now be installed on Azure Kubernetes Service

You install IBM Cloud Pak for Integration on Azure Kubernetes Service (AKS) by using Helm charts to install the operators.

Documentation updates

This release includes a number of improvements to the Cloud Pak for Integration documentation, including:

  • Documentation of "New features" as described in the previous section. For more information, see the links to the applicable topics.

  • A new guide to installing IBM Cloud Pak for Integration on Azure Kubernetes Service

  • Topics explaing the new capability to manage instances across multiple instance locations, and on how create a node by using a template from Automation assets.

  • The Cloud Pak for Integration roles topic has additional information about fine-grained permissions; grouping of roles are now in table format for easier scannability.

  • New Node licensing topic to help you to maximize CPU usage across the containers on your cluster.

  • The "Building integrations" section is renamed to "Using the Cloud Pak".

New releases of instances

Instances are listed by their product operator names (for example, Queue manager is listed as "IBM MQ").

This release of Cloud Pak for Integration includes the following updates to products:

For information about previous releases, see the Cloud Pak for Integration documentation.