Additional choices for deployment, licensing and API testing.

December 14, 2021, was the official GA date for IBM Cloud Pak® for Integration 2021.4.1, which included the following enhancements:

  • New licensing option to use Event Endpoint Management
  • Enhancements to API Test Generation
  • Additional components available for deployment on IFLs for IBM System Z
  • First availability of Cloud Pak for Integration components on IBM Power Systems
  • New options for IBM License Use Management

Some of these features are new and some build on the existing capabilities that have been delivered over the previous releases that have made Cloud Pak for Integration a powerful — yet simple-to-use — platform for seamless integration anywhere in your business. Read the announcement letter here.

New licensing option to use Event Endpoint Management

The Event Endpoint Management feature was first delivered in Cloud Pak for Integration 2021.1.1 and has been enhanced in each release since then. Apache Kafka is being widely adopted to ensure information about events can be rapidly moved across the business, allowing this information to be used in multiple different backend applications. At the same time, many businesses are focusing programming skills on API-driven access to data. Event Endpoint Management combines these different technologies in providing API-led access to Kafka data.  

Customers wanting to use Event Endpoint Management to expose their Kafka stream histories through API Calls using the AsyncAPI protocol could use Cloud Pak for Integration VPCs through the ratio table to deploy and use this feature. However, this would provide them with deployment costs aligned to the number of cores the function was deployed into, rather than aligned with the usage of this feature, as judged by the number of API calls made to retrieve Kafka events.

In this release, customers can instead use this increasingly important feature by using the Cloud Pak for Integration API Calls add-on. This allows the customer to buy a specified number of API Calls per month, for which they are charged relative to that number of calls. This can better align with the value of using this feature, independent of how many processors cores are needed for deployment. The API Calls add-on can be used for both regular API Calls using the API Connect component of Cloud Pak for Integration and the Event Endpoint Management component, which provides the AsyncAPI calls. The choice of how to pay for using AsyncAPIs is now up to the customer.

Enhancements to API Test Generation

This is an additional enhancement to the AI-powered API Test Generation feature introduced earlier in 2021. As businesses develop more and more APIs, there is a growing effort required to ensure these APIs are thoroughly tested. This growing testing requirement places an increased burden on the business. AI-driven API Test Generation is designed to automate the process of generating these API test cases by using artificial intelligence (AI) to intelligently create the best test cases and build test coverage based on the APIs being created.

There have been further enhancements to the test generation that make it easier to stand up and tear down tests, but key in this latest release is the use of deeper AI. Watson AI generates test insights through analysing production OpenTracing data. This helps to determine distinct behaviours in an API implementation, and these are then reviewed against the existing test coverage. Watson AI then suggests what tests to create from the templates it offers to give the best coverage. The top-three suggestions are offered to the customer. This choice can make it much faster and easier to provide effective test coverage of APIs without wasted effort.

Additional components available for deployment on IFLs for IBM System Z

Each business is different in terms of what assets it has, where it runs certain workloads and how it balances the different business needs against those assets. To support those customers running workloads on IBM Z Servers with IFL (Integrated Facility for Linux), the previous release of Cloud Pak for Integration delivered many components of the Cloud Pak for Integration 2021.3.1 release to be deployed on OpenShift on IBM Z IFLs. This helps customers make their own business decisions of where to run their workloads in support of their business needs.

Cloud Pak for Integration further extends this choice by delivering additional components for deployment on OpenShift on IBM Z IFLs. This release includes App Connect Designer and the Automation Assets component.

App Connect Designer makes it simple and quick to build and deploy integrations without coding to rapidly address business integration needs. Almost anyone can create integrations with the tooling designed to help pull in templates and provide assistance by using AI suggestions for mapping and transformation.

The Automation Assets component (previously called Asset Repository) also helps with building integrations more quickly. This enables integrations to be stored and reused, ensuring that new integrations don’t need to start from scratch and that an integration requirement can be solved by pulling a pre-built integration from the repository if it has already been built.

First availability of Cloud Pak for Integration components on IBM Power Systems

As with increasing customer choice by enabling the deployment of Cloud Pak for Integration on IBM Z IFLs, there is another extension of customer choice with Cloud Pak for Integration 2021.4.1. In this release, there is now — for the first time — the ability to deploy some components of the Cloud Pak on IBM Power Systems hardware running OpenShift on Power. In this release, the components available include Platform Navigator, App Connect (Runtime, Designer and Dashboard), Event Streams and MQ. It should be noted that while the rest of these components can be deployed with IBM-built container images using the included Kubernetes operators, MQ and MQ Advanced must be deployed using a customer-built container image.

New options for IBM License Use Management

IBM software is deployed using agreements between the customer and IBM and is subject to the customer using agreed software to report on deployment. This includes the IBM License Service for container-deployed software and the IBM License Management Tool for non-container deployed software.

While these tools report on deployment for audit, as is required, the information isn’t typically easy to access for any of the users of the software. This can lead to a lack of visibility when customer deployments reach entitlement limits, and the absence of ready access to the information can hamper the ability to implement departmental cross-charging or even understand different workload deployment patterns.

With the latest release of Cloud Pak for Integration, customers now have the option for both the License Service and IBM License Management Tool to publish this contractual usage data to their own page on IBM Software Central. By aggregating this install and deployment data in a single location, customers will benefit from increased transparency of usage and be able to respond faster to changes in usage patterns and align deployment to entitlement. To ensure that customer needs are met, the uploading of this information is optional and entirely for the customer to decide.

Get started

If you are keen to try some of these features for yourself explore the hosted trial environment here.


More from Automation

Observing Camunda environments with IBM Instana Business Monitoring

3 min read - Organizations today struggle to detect, identify and act on business operations incidents. The gap between business and IT continues to grow, leaving orgs unable to link IT outages to business impact.  Site reliability engineers (SREs) want to understand business impact to better prioritize their work but don’t have a way of monitoring business KPIs. They struggle to link IT outages to business impacts because data is often siloed and knowledge is tribal. It forces teams into a highly reactive mode…

Buying APM was a good decision (so is getting rid of it)

4 min read - For a long time, there wasn’t a good standard definition of observability that encompassed organizational needs while keeping the spirit of IT monitoring intact. Eventually, the concept of “Observability = Metrics + Traces + Logs” became the de facto definition. That’s nice, but to understand what observability should be, you must consider the characteristics of modern applications: Changes in how they’re developed, deployed and operated The blurring of lines between application code and infrastructure New architectures and technologies like Docker,…

IBM Tech Now: September 18, 2023

< 1 min read - ​Welcome IBM Tech Now, our video web series featuring the latest and greatest news and announcements in the world of technology. Make sure you subscribe to our YouTube channel to be notified every time a new IBM Tech Now video is published. IBM Tech Now: Episode 84 On this episode, we're covering the following topics: The IBM Security X-Force Cloud Threat Landscape Report The introduction of IBM Intelligent Remediation Stay plugged in You can check out the IBM Blog Announcements…

Debunking observability myths – Part 5: You can create an observable system without observability-driven automation

3 min read - In our blog series, we’ve debunked the following observability myths so far: Part 1: You can skip monitoring and rely solely on logs Part 2: Observability is built exclusively for SREs Part 3: Observability is only relevant and beneficial for large-scale systems or complex architectures Part 4: Observability is always expensive In this post, we'll tackle another fallacy that limits the potential of observability—that you can create an observable system without observability driven by automation. Why is this a myth? The notion that…