Brand-new features, reduced deployment footprint and, of course, even more automation and AI capabilities — all in IBM Cloud Pak® for Integration 2021.2.1.

More than ever before, this release of IBM Cloud Pak for Integration makes AI-powered Automation a reality. There are now five major ways that Cloud Pak for Integration’s AI-powered Automation improves your outcomes:

  1. Natural language integration: This new feature allows users to describe their desired integration flow simply using natural language. (Watch demo here.)
  2. Transformation generator: This new feature enables users to define the format of source and target data and automatically generates the complex mapping transformation. (Watch demo here.)
  3. AI for API testing: This feature (upgraded from the Q1 release) automatically observes the API traffic in a production environment, identifies where it lacks test coverage and builds tests with no human input. (Watch demo here.)
  4. Mapping assist: This feature (upgraded from 2020) automatically maps a source to target using semantic understanding. This intelligent automation gets better the more it’s used, learning from previous experiences and becoming more familiar with an enterprise’s environment. (Watch demo here.)
  5. Cloud-native HA for MQ: This feature (now fully released following early access in Q1) automatically replicates message data between a set of IBM MQ instances deployed into the cloud, maintaining continual availability of the messaging service in the event of individual failures — all without the cost and complexity of shared external storage. Using the MQ automatic client reconnection capability, there’s also no need to rewrite your applications to take advantage. The MQ you have relied on for years is now always on, in any cloud, with no application change needed. (Watch demo here.) 

Additional updates and features

These new AI features are just the beginning. In addition, we’ve added Event Endpoint Management, a new feature that extends our multi-form API management capabilities to also allow users to manage Kafka endpoints. And, with this release, we’ve added a new gateway service that enhances those Kafka endpoints with additional security. This feature will complement any organization’s EDA strategy and Kafka distribution. (Watch demos here.) 

Also, API Connect and DataPower delivered a major release on delivering feature parity and easing the upgrade progress, enabling v5 and V2018 customers to easily migrate to v10. Additionally, a new Upgrade Central site was published, providing a one-stop start for all API Connect upgrade/migration projects.

The news doesn’t stop there. These upgrades recently culminated in a “Watson Moment,” which is a branded, in-product experience with impactful Watson use cases, providing tremendous user value. In this release of IBM Cloud Pak for Integration, a Watson Moment was implemented that allows developers to quickly and easily create an integration flow. Developers can simply type a few words describing their integration scenario, and Watson will recommend existing assets that best match their needs. By using IBM Watson NLP technology to extract keywords, entities, intents and relationships, Watson is able to identify which flows will meet the developer’s goals. This Watson Moment not only saves time but also increases accuracy in the flow creation process. 

Get started with IBM Cloud Pak for Integration

Above all else, remember the following:

  • Regardless of the industry, there is no automation without integration; it enables the movement of data that makes automation opportunities possible.
  • IBM Cloud Pak for Integration is the most deployed Cloud Pak on OpenShift.
  • It’s extremely easy to trade up to IBM Cloud Pak for Integration from existing technologies, as you can continue running in your old environment until you’re ready to make a full move.

So what are you waiting for? Click here to get started with IBM Cloud Pak for Integration today. 


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…