Cloud Pak for Integration

Cloud Pak for Integration

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.

 View Only

Manage, Monitor, and Control: Cloud Pak for Integration 16.2.0

By CAROLE BADEN posted 07/22/26 05:51 PM

  

This release of IBM Cloud Pak for Integration 16.2.0, which is Support Cycle-2 (SC-2), includes two years of base support that can be extended after the initial time period. 

Since the 16.1.0 SC-2 release, IBM Cloud Pak for Integration has expanded on the promise of powerful, cohesive experience by delivered a new set of tools for monitoring and controlling all your deployments, wherever they may be located.

Key enhancements include:

  • A new, comprehensive set of Kubernetes resources for managing integrations

  • Making the Platform UI an easy way to deploy all the integrations you need, with almost no up-front configuration required

  • Ability to install the Platform UI on Azure Kubernetes Service

  • Deployment with a leaner architecture to reduce the footprint and decrease the time to getting up and running. This includes a less-resource intensive way to get Keycloak in your installation.

  • A Cloud Pak for Integration Agent with a conversational interface to get information and recommendations for user actions.

Managing instances across multiple locations, in the Platform UI

It can be frustrating to track multiple software deployments across all your clusters and other platforms. We have found a way to have that information available from a single deployment of the Cloud Pak:

  • In 16.1.2, we introduced the ability to view your deployed instances across multiple locations (OpenShift clusters and namespaces) from a single hub deployment of the Platform UI, which included the location information for where those instances were deployed. 
  • In 16.1.3, we added the ability to create, edit, and manage these remote instances. Additionally, a new Overview pane on the Platform UI home page summarizes the status of instances and locations that you manage from this Platform UI instance, and you can get details about any errors or warnings.
  • As of 16.2.0, this capability is no longer confined to Kubernetes deployments in your OpenShift cluster. By deploying an Integration dashboard as part of the hub Platform UI and enabling App Connect Private Networks feature, you can now view and manage non-Kubernetes App Connect runtimes from the Platform UI, as well.

            

The Platform UI home page has a dashboard of instance locations; also, each instance in the list of deployed instances has location information.

For more information, see Managing instances across multiple locations.


End-to-end monitoring


No organization confines their software deployment to just one product set. You have an entire integration ecosystem, and you need a low-overhead way to trace cross-product transactions. 

In 16.2.0, we introduced end-to-end monitoring, which uses Open Telemetry to provide tracing across a selection of Cloud Pak instances. This capability provides a centralized way to measure efficiency, locate bottlenecks, and identify and resolve issues.


You can configure any of these instances for end-to-end monitoring:

  • API Gateway
  • Event Gateway
  • Queue Manager
  • Integration runtime

For more information, see Using end-to-end monitoring.


Federated API management


Another new instance in the Cloud Pak is Federated API management, which lets you connect, manage, and monitor multiple distributed API runtimes and data planes from a single interface.

Federated API management can manage and monitor all the data planes and its associated assets, in all locations.


Federated API management can monitor and manage API Connect runtimes that support integration with subsystems such as API CMS Portal, API Gateway, API Developer Portal, and API Nano Gateway.

Benefits of using this capability include:

  • Discovery and inventory of all deployed runtimes and APIs

  • Centralized management of runtimes, data planes, and API assets

  • Unified monitoring of performance, usage, and lifecycle status

  • Role-based access and control

        

For more information, see Using Federated API Management.


Platform UI key enhancements

The Administrative section provides direct access to license usage, analytics, and other administrative tasks, while the full navigation also provides access to your instances.

Updates to the Platform UI include:

  • A greatly reduced footprint and operational overhead, improved speed and responsiveness

  • Direct access to license usage reporting and analytics

  • Stop and start instances, and save instances as drafts

  • Faster install times, which can be under 5 minutes

  • Reduced footprint and operational overhead for the Platform UI and Keycloak
    • Foundational services are no longer required for installing the Platform UI or any instance type that uses Keycloak for indentify and access management. They are only needed for deploying an API Manager instance type. This conveys the following advantage:

    •  Removal of the dependency on EDB Postgres for the Kubernetes operator and its catalog source pod.

     

Kubernetes resources

In each new version since 16.1.0, we have continued to bring in new product capabilities as instances that you can deploy and manage directly in the Platform UI.

16.1.1

  • Integration runtime

  • Kafka connect runtimes and Kafka connectors

  • Kafka topics and Kafka users

16.1.2

  • API Connect subsystems: API Manager, API Analytics, API Portal, and API Gateway

  • Event Processing

16.2.0

  • End-to-end monitoring

  • Federated API management

  • API Nano Gateway

  • API Developer Portals

Get all the details on “What’s new”

For more information about new features, product changes, and other updates since 16.1.0, see “What’s new in IBM Cloud Pak for Integration” for the release indicated:

Summary of product changes

For your reference, the following list describes key changes to product functioning (excluding the “Kubernetes resources” listed in the previous section), grouped by release version. You’ll find additional detail in the Product changes section for each “What’s new” page.

16.1.1

  • Streamlining of the upgrade process.

  • Easily connect Event Streams resources to App Connect resources,

  • Saving instances as drafts, without having to deploy them

  • Administrators can create and apply policies to instances

  • Instances of API Manager, API Analytics, and API Portal subsystems can be deployed on ppc64le

16.1.2

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

  • 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.

  • Keycloak 26 is available for identify and access management

16.1.3

  • Create, edit, and manage instances in other locations

  • Overview pane in the Platform UI

  • Support for deployment of the Platform UI supports deployment on Red Hat OpenShift Container Platform in a dual-stack (IPv4 + IPv6) network configuration.

  • Expanded support for FIPS 140-3 in the Platform UI and instances.

  • Accessibility enhancements, including keyboard shortcuts, screen reader functionality, and appropriate color contrast

16.2.0 

  • Enhanced awareness of deployed integration servers from the upgrade plan, with targeted instructions

  • Multi-replica support for instance locations to support high availability

  • Direct access to instance configuration from the Platform UI navigation panel

  • Ability to download the instances table as a CSV

  • Expanded layout for building and configuring integrations

  • Direct navigation to instances grouped by type, by clicking the main menu icon

  • Easy sharing of filtered views by means of an automatically updated URL

0 comments
49 views

Permalink

https://community.ibm.com/community/user/blogs/carole-baden1/2026/07/22/manage-monitor-and-control-cp-integration