What's new in IBM Cloud Pak for Integration 16.1.0

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

New features

Cloud Pak for Integration version 16.1.0 adds the following enhancements:

Messaging server and messaging custom resources added to address key integration use cases

A Messaging server supports a Cloud Pak-specific set of messaging use cases. Use the new Messaging custom resources to create and configure users, channels, and queues. Messaging servers seamlessly integrate with Integration design and Integration runtimes. For more information, see Using a Messaging server.

Assets can be marked as "Approved" in Automation assets

Administrators can now mark assets as "Approved", to indicate to users in your organization that an asset is endorsed according to specific criteria. For example, you can apply the label to templates for deploying instances that meet your organization's guidelines and best practices. For more information, see Using Automation assets.

Policy enforcement

Administrators can create and apply policies. Applying policies to instances ensures that those instances are not deployed or updated unless they comply with the policy. While this feature was a Red Hat OpenShift Technology Preview in the 16.1.0.0 Platform UI fix pack, it is now a fully-supported feature and can be used in production environments. The feature is automatically available if two requirements are met: 1) the cluster runs Red Hat® OpenShift® Container Platform 4.17 or later, and 2) the fix pack for version 16.1.0.8 (or later) of the Platform UI is applied. For more information, see Applying policies. (16.1.0.8)

Enhancements to the assembly canvas experience

Updates to the canvas experience make it even easier to build instances, including:

  • A Build with assembly canvas button on the IBM Cloud Pak Platform UI home page that provides direct access to canvas authoring.

  • The new "Import existing instances" button on the canvas helps you import previously deployed instances into any canvas, to facilitate building additional integrations with those instances.

  • The table on the home page now shows which independent instances are being used inside a given assembly canvas.

For more information, see Using the canvas to create instances and integrations.

Enhancements to the Platform UI

The following enhancements are made to the Platform UI:

  • Updated visual design.

  • More fields are available for you to filter the instances list. You can now filter by name, type, namespace, version, creation date, status, and labels.

  • The "Versions and upgrades" page is updated to make it even easier to manage versions and upgrades. For more information about the process, see Managing versions and upgrades by using the Platform UI.

New instance types supported for disaster recovery by using OADP

You can now backup and restore these additional instance types by using Red Hat OpenShift API for Data Protection (OADP):

Operator Instance type
IBM Cloud Pak for Integration
  • API
  • API Product
  • Assembly
  • Messaging server
  • Messaging queue
  • Messaging channel
  • Messaging user
IBM API Connect
  • API Connect cluster
  • API Manager
  • API Analytics
  • API Gateway
  • API Portal
IBM DataPower Gateway
  • Enterprise gateway
IBM MQ
  • Queue manager
IBM Cloud Pak foundational services
  • Keycloak

For more information about backing up these and other intances in Cloud Pak for Integration by using OADP, see Backing up and restoring IBM Cloud Pak for Integration.

Event Gateway instances can be managed from the Platform UI

You can now create, edit, view, and delete Event Gateway instances in the Platform UI.

Preview Cloud Service - Integration assistant available in the Platform UI

The integration assistant is a conversational interface that can help you with tasks such as deploying instances and integrations. You can enable the integration assistant in the Platform UI as a technology preview. The assistant is available for online OpenShift clusters only. For more information, see Using the integration assistant (Preview Cloud Service).

Managing Integration runtime instances in the Platform UI

You can now create, view, and manage (for example, edit or delete) Integration runtime instances in the Platform UI. Previously, you could use Cloud Pak for Integration to manage Integration runtime instances only if they were part of an assembly. This feature makes managing your Integration runtimes easier because you no longer have to open an Integration dashboard to manage them. Also, you can use Integration runtimes with other Platform UI features such as sharing templates and managing upgrades. Additional management features can be accessed from the Integration dashboard.

An Integration runtime instance can appear in multiple places in the Platform UI. For example, the Platform UI shows Integration runtime instances that are managed by an assembly under that assembly. Other Integration runtime instances are shown either under an Integration dashboard instance, if one exists in the same namespace, or as a stand-alone entry. (16.1.0.1)

Saving instances as drafts

When you create a new instance, you can save a draft version of it. Saving as a draft preserves your configuration without you having to deploy the instance to your OpenShift cluster. You can continue editing your draft until you are ready to deploy the instance. For more information, see Saving drafts of instances. (16.1.0.2)

Event Manager instances now support Keycloak for identity and access management

Event Manager instances now support authentication and authorization by using Keycloak in the Cloud Pak for Integration. Keycloak is an identity and access management system in IBM Cloud Pak for Integration. For more information, see Identity and access management. (IBM Event Endpoint Management 11.3.0 and 16.1.0.4).

Improved performance in the Platform UI

The Platform UI is faster and more responsive. (16.1.0.5).

Managing Kafka topics and Kafka users in the Platform UI

You can now create, view, and manage Kafka topics and Kafka users in the Platform UI without having to open the Red Hat OpenShift console or a Kafka cluster instance. You can also integrate Kafka topics and users with other Platform UI features, such as sharing templates and saving drafts. Additional management features can be accessed from the Kafka cluster.

Kafka topics and users are available in multiple places in the table of deployed instances in the Platform UI. For example, Kafka topics and users that are part of an assembly canvas are shown with that assembly (click to expand the contents of the assembly). Other Kafka topics and users are listed either for a corresponding Kafka cluster instance, or as a stand-alone entry. (16.1.0.6)

Managing Kafka connect runtimes and Kafka connectors in the Platform UI

You can now create, view, and manage Kafka connect runtimes and Kafka connectors in the Platform UI without having to open the Red Hat OpenShift console or a Kafka cluster instance.

Kafka Connect runtime instances can be nested under their respective Kafka cluster instance. They can also appear as stand-alone entries if they are not linked to a specific Kafka cluster instance. Similarly, Kafka Connectors can be nested under their associated Kafka Connect instance, or they can be listed independently if not tied to a particular Kafka Connect runtime. (16.1.0.7)

Create instances by browsing templates in Automation assets

Administrators can now create integrations by browsing for templates in an Automation assets instance, then using those templates to create instances in the Platform UI. Any instance you create or manage can be stored as a template in Automation assets. Share and reuse templates with your team and organization within Automation assets, and create them in the Platform UI. For more information, see Using Automation assets. (16.1.0.7)

Easily connect Event Streams resources to App Connect resources, with just a few lines of code

The IntegrationBinding Kubernetes resource allows users to easily connect integration design and integration runtime instances with Event Streams resources. For more information, see "Binding Event Streams resources with App Connect resources" in Connecting different instance types. (16.1.0.8)

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 by using a template from Automation assets. For more information, see Using the canvas to create instances and integrations. (16.1.0.9)

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. (16.1.0.9)

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 (16.1.0.9)

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. (16.1.0.10)

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. (4.1.2)

Note: Cloud Pak for Integration version 16.1.0 is a Support Cycle-2 release, which means that it is the first long term support version since version 2022.2. For an overview of all product updates since then, see the blog post on IBM Community. You can also review the prior release notes:
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 fixpack versions - See "Catalog sources for operators" in Adding catalog sources to an OpenShift cluster.

Product changes

New versioning scheme for Cloud Pak for Integration

In previous releases, Cloud Pak for Integration versioning referenced the "Year.Quarter.Release-Fix" (as in version 2023.4.1-0). With the current release, version 16.1.0 , Cloud Pak for Integration moves to the VRMF (Version.Release.Modification.Fix) versioning scheme, which is consistent with other products across IBM. For more information, see IBM Software product versioning explained.

Support for IBM zCX Foundation for Red Hat OpenShift

Cloud Pak for Integration supports installation on IBM zCX Foundation for Red Hat OpenShift. For more information, see Operating environment.

Support for OpenShift odd numbered minor releases

In addition to the current support for even-numbered minor OpenShift releases, Cloud Pak for Integration is adding support for installation on odd numbered minor OpenShift releases, starting with OpenShift 4.15. For more information, see Red Hat OpenShift Container Platform Life Cycle Policy in the OpenShift documentation.

Support for Event Endpoint Management on s390x

The IBM Event Endpoint Management operator, and the associated Event Manager and Event Gateway instance types, are now supported on s390x in addition to amd64. For more information, see Operating environment.

Change in version support for Linux on IBM Power

Linux on IBM Power 8 hardware is no longer supported. Versions 9 and 10 are still supported.

Removal of AI test generation

AI test generation is permanently removed in the current release. If you already have AI test generation deployed, it will be removed when you upgrade Cloud Pak for Integration.

Removal of NLP-powered App Connect flow recommendations in Automation assets

Following its deprecation, the NLP-powered App Connect flow recommendations feature has been removed in the 4.0.6-sc2 release the Automation assets.

Removal of Experimental Flow Generator service

The Experimental Flow Generator service for building App Connect flows has been removed. Users will no longer be able to access the service from integration design instances.

Streamlined process for adding catalog sources

You can now add the catalog source for an operator with a single command.

Event Processing Add-on

The new "IBM Cloud Pak for Integration Event Processing Add-on” entitles you to deploy and run the Event Processing component previously only available in the IBM Event Automation offering. This add-on provides both the Event Processing component and Red Hat OpenShift entitlement.

The add-on is a stand-alone component that is not a part of Cloud Pak for Integration. You can use the add-on to deploy and run Event Processing even if Cloud Pak for Integration is not installed. However, you need at least 1 VPC of Cloud Pak for Integration entitlement to purchase and use the add-on.

For more information about licensing, see the License Information document for license LZUJ-BAKE2S. For more information about using the Event Processing component, see Licensing reference ("Event Processing add-on for IBM Cloud Pak for Integration" section) in the IBM Event Automation documentation.

Documentation updates

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

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.