IBM Cloud Pak for Integration 2023.4.1 – when bigger is not always better.

Some good news that Cloud Pak for Integration 2023.4.1 announced today. And there are many different enhancements and new features. Let’s start by looking at the benefits of being small.

Many businesses are seeing the benefits of deploying in Red Hat OpenShift Container Platform for resilience, scalability and availability by taking advantage of a multi-node cluster. But while this delivers multiple benefits, it can be much larger and deliver more than is always needed. When resources are more constrained but you still want to take advantage of OpenShift, that’s when you might explore Single Node OpenShift. This extends the OpenShift experience with the same skills and tools but with a smaller footprint.

And this smaller footprint is one you can now take advantage of with the latest release of Cloud Pak for Integration, which now supports deployments on Single Node OpenShift. Now, whether deploying in a manufacturing location, or a retail store, or even your own server machine, you can look at how Cloud Pak for Integration can meet your needs while requiring fewer resources.

Also helping reduce the need for resources in Cloud Pak for Integration 2023.4.1 is a change in how the included foundation services can be used and installed. As well as themselves requiring fewer resources, their deployment is now more optional giving customers more choices in how and where they might use Cloud Pak for Integration given the reduced resource requirements. Another change in foundation services is that Keycloak is now used for Identity Management.

As well as the reduced resources and simplification in the need of foundation services, there have also been improvements and simplification when configuring and deploying integrations. For the last few releases Cloud Pak for Integration has delivered automated deployments using Integration Assemblies. This allows multiple separate integration configurations and deployments to be defined in single document, accelerated by providing defaults for many of the steps. The integration assembly therefore not only simplifies the definition of the different integrations needed in a solution, but then makes the deployment and management of these steps simpler through being able to handle them all in a single object.

In the latest release of Cloud Pak for Integration these assemblies have been further enhanced. The integrations now can be ‘labelled’ so that when deployed as part of a solution, each deployed component can be identified with the label ensuring that there can be improved visibility and awareness as well as enhancing management and monitoring, as these labels can be tracked using Instana.

An additional and significant enhancement to the Integration Assemblies is that as well as holding the definitions in a YAML document, the integration can now be created and displayed using a graphical canvas approach. This can help new integrations to be created more easily, as well as being simpler as a way to get visibility of the integrations that make up a solution.

Federal Information Processing Standards (FIPS) are issued for US federal government systems to help to confirm to specified security requirements. The latest release of Cloud Pak for Integration can be deployed in an OpenShift cluster that has been deployed in FIPS mode. All the pods deployed will be FIPS-tolerant.

Customers also get a wider choice of simpler deployment options into Microsoft Azure and Amazon AWS public clouds. Many customers have already deployed Cloud Pak for Integration in Azure and AWS, but Cloud Pak for Integration is now available in the Azure Marketplace offering very simple deployment of existing Cloud Pak for Integration entitlements (BYOL). Customers in the US can also purchase Cloud Pak for Integration directly from the Azure Marketplace. IBM will also make Cloud Pak for Integration available on the AWS Marketplace, simplifying deployment, and will also add the option for purchasing directly from the AWS Marketplace for customers in a limited number of countries.

Over the last 3 years, customers have been able to take advantage of various time-limited offers providing access to Software-defined storage from IBM. As part of the latest release of Cloud Pak for Integration, customers deploying this new release get entitlement to IBM Storage Fusion Essentials. This provides up to 12TB of Block, Object or File storage per OpenShift cluster, and this is available as long as the customer has entitlement to Cloud Pak for Integration. This offer replaces the previous offers once customers move to Cloud Pak for Integration 2023.4.1.

Included in Storage Fusion Essentials through Cloud Pak for Integration entitlement:

• Fusion Data Foundation internal deployment node up to 12TB per cluster. This includes compression, cluster-wide encryption and cross-availability zone HA.
• No usage time limit.
• Fully supported by IBM.

Customers who see the benefit of IBM Storage Fusion Essentials might want to upgrade to IBM Storage Fusion Advanced.

Clients may choose to purchase IBM Storage Fusion Advanced for the following additional features:

• Capacity requirements above 12TB per cluster
• External mode deployment
• Backup
• Disaster Recovery
• Global Data Platform (Storage Scale)
• Data Catalog
• Advanced encryption with external key management

Customers who are keen to try this release of Cloud Pak for Integration can take advantage of a 60 day trial entitlement here.

And if you are ready to deploy Cloud Pak for Integration on Azure Marketplace today you can go here. And stay tuned for a link to easily deploy Cloud Pak for Integration on AWS Marketplace.

Cross the river without falling in. Modernize your business with IBM Cloud Pak for Integration.

Modernizing your integration is a journey

Modernizing your business sounds exciting, maybe even necessary, but also scary. Does it mean replacing all the things you have today? Things which you are both comfortable with, but also likely frustrated by. The goal is to transform your business to become more agile. Not everything you have is broken. It just needs to be used more effectively. Where something is broken – fix it. If it works keep it. And it’s probably a good time to stand back and figure where you want to make improvements, and maybe what you want to be able to do afterwards. Not everything you need to change is technology-based. There will be many processes that you might want to revisit as part of this modernization. Additionally, the people in your organization will also need to see what you are trying to achieve and to participate to enact the changes.  

What are businesses trying to overcome and change? Applications and systems need to connect and to access and exchange data to drive business activities. This connectivity is described as integration. Today any integrated IT infrastructure is likely already highly inter-connected to ensure the rapid and secure movement of data to power their business activities. But as businesses look to build new or replace applications to enhance their existing operations or to respond to new and changing business opportunities, they may find their existing architecture and integration approach slows them down, or even prevents them from making changes faster or doing business in new ways.

Their existing integrations might be too interconnected and tightly-coupled, with any change or version update at all impacting too many other systems, and requiring months or years of testing.

Or perhaps the current way of building and deploying integrations is too slow, with too many manual steps and key staff always pressured by competing priorities. This slows down the ability of the business to add new applications and integrate them quickly to the rest of their business.

Even if spending was available to add new skilled resources to the team, additional people would not necessarily make a material difference to how quickly new integration deployments could be achieved due to the systemic inefficiencies in the implementation. The extra cost would also be hard to justify with budgets mostly allocated to business unit projects rather than integration teams.

Instead, what is needed is to approach integration in a new way. How to achieve many of the same integration outcomes without a lot of the same overheads and complexity? And how to build and deploy brand new applications and capabilities integrated seamlessly, securely, and rapidly to the rest of the business? To do this you need to modernize your integrations. You might think how do I get started? Just as if you were looking to cross a river. You want to get to the other side. But how?

Imagine integrations that were simple to build, and not just easy to deploy, but with updates that can be added to your CI/CD pipeline. Where any integration, using any style of integration, can be deployed using the same skills and techniques, to a runtime environment that is the same wherever it is deployed. A runtime environment that would be the same on-premises, or in the cloud. An environment that can scale up and down automatically with each component scaling up and down individually rather than the whole environment. Integration environments which are simple to update, decoupled from each other and from the deployed infrastructure, and migrate without impacting up-time. And integrations that are individually deployable, scalable and can operate and be updated without impacting any other integration deployment or application.

Line of business application teams can request new integrations, and even design them without coding and without waiting for individual help from the integration specialists. And integration specialists can spend their time adding value, solving complex issues or enhancing the wider infrastructure instead of churning through multiple repeated requests and following time-consuming resource-intensive step-by-step processes. Existing integration deployments can still provide the same value and capabilities by connecting and moving data, but the complexity of configuration, deployment and operation can be greatly reduced.

This modern approach to integration is the value proposition behind IBM Cloud Pak for Integration. The most complete set of integration capabilities, all engineered and optimized for cloud-native container deployment, built to exploit the resiliency and scalability of the Red Hat OpenShift Container Platform, deployed on-premises or on public cloud. All integration components are deployed using the same approach, through Kubernetes Operators, to simplify, automate and provision without manual intervention.

While the deployment and management might be designed for cloud-native environments and requirements, the functions are going to be familiar to many customers. And your business will see these familiar, and easy to adopt steps as achievable and accessible. Like stepping stones helping you to cross the river. You can move forward, without getting into difficulties, and without losing what you already have.

If deploying new IBM MQ instances to provide assured once-and-once-only message delivery with transaction integrity, the new container runtimes will still work seamlessly with existing MQ deployments on any other platform or environment. But the new container MQ gets the options of a self-contained container-native high availability option providing seamless uptime, continuing access to messages, all at a lower cost and with reduced complexity. And customers can build new applications to benefit from being able to deploy new Queue Manager instances in minutes rather than months.

Connecting different applications together can be hugely complex. But IBM App Connect as part of Cloud Pak for Integration has smart connectors for almost every application and comes with AI powered assistance to help you connect and map fields. And each integration flow you deploy can run in a separate container runtime, reducing inter-dependencies, and increasing scalability without needing to scale up the whole environment.

Your enterprise data can be widely shared through APIs using IBM API Connect with new APIs created simply without coding. APIs which can then be tested automatically through AI powered ‘Auto Test Assist’, and then socialized through a portal to provide access more widely.

And business events can be distributed, discovered and real-time responses triggered into action with Event Streams and Event Endpoint Management. Again deployed into containers, under a consistent deployment and update framework, without creating a complex framework of deployments. Keeping your business agile.

With fully containerized integration to meet all business needs your business is now modern, adaptable, and agile. You can take it anywhere you want to go. At scale and securely. Cloud Pak for Integration helps you move forward with every step. Get started now with a 60 day trial. And check out the easy deployment option on Azure Marketplace.

More workload, less work with Cloud Pak for Integration 2023.2.1

Each day, no matter the job, there is a challenge to do better. Can you be more efficient? Can you be faster? Can you do more, with less? These challenges apply everywhere, but for years we have been talking with customers about their integration needs and this is exactly what we have heard from them.

Trying to enhance your enterprise integrations can seem to be a near impossible task. You have skilled people, but probably never enough, and they are always busy keeping the existing implementations running to power your business so that they never can take the time needed to deploy new implementations fast enough to meet the needs of the business, to try something new or to overhaul the existing integrations.

Over the last few years IBM has invested heavily in this area to overcome these issues and to deliver increased value to customers, enabling them to create, deploy and update integrations with less effort. Their businesses can move faster and they can even reduce their costs. IBM has an integration solution that can address any customer need, and as part of Cloud Pak for Integration they have been re-engineered to be cloud-native, deployable in containers. Customers can now deploy the integration components they need anywhere that runs Red Hat OpenShift Container Platform. Every product can be deployed using Operators as part of a CI/CD DevOps strategy making it faster and easier to not only get integrations into production, but to keep them running and to update them.

The latest release, Cloud Pak for Integration 2023.2.1, announced here takes this even further, adding additional enhancements and new capabilities to what has already been delivered in past release.

One of the most notable new features builds on the prior ‘automated deployment’ feature. This feature allows integration solutions to be defined and managed as a single deployable object. Not only does this make it easier to define an entire integration solution, with suggested default values being supplied for many of the options, but it is then easier to move forward through development, test and production cycles with all components managed together. The initial release provided this feature for MQ and Event Streams deployments. In the latest release this now adds API Connect and App Connect deployments. Additionally, when creating these new deployable integration solutions, adding High Availability is as simple as selecting an option which will then ensure the integration solution is deployed as a highly available configuration.

Another enhancement in the latest release provides additional value when using IBM Instana with Cloud Pak for Integration deployments. In previous releases customers could use IBM Instana to provide monitoring across integration components, as well as providing tracing for MQ and App Connect deployments. In the latest release IBM Instana can now offer tracing for Event Streams and API Connect deployments. And any new purchases of Cloud Pak for Integration still benefit from 6 months free entitlement to IBM Instana for use with entitled Integration products.

Other enhancements in the most recent release include updated deployment options for Event Endpoint Management which can now be deployed independently of API Connect deployments in OpenShift environments. This will make it simpler for customers to make use of Kafka events by exposing them as APIs using the AsyncAPI standard.

Also the IBM Integration product teams have been working with IBM Turbonomic team to enhance the Resource Management suggestions that IBM Turbonomic will offer to ensure that they are tailored to match the environment and the specific integration product requirements.

The announcement letter also covers a number of other exciting new products and updates to existing products. New offerings include IBM Event Automation an Noname Advanced API Security for IBM. There is also a new API Connect as a Service Advanced tier option, and the latest IBM MQ 9.3.3 release.

With improvements such as the update to the automated deployment feature, the latest Cloud Pak for Integration will enable your integration team to move faster, and deploy richer, more complete integration solutions with High Availability, without adding complexity or overloading your skilled team members.

You can request trial entitlement of Cloud Pak for Integration here but the latest release won’t be available until June 16^th 2023.

Seeing is believing with the latest updates to IBM Integration including Cloud Pak for Integration 2022.4.1 and MQ V9.3.1

Sometimes pictures on their own can be underwhelming. They might lack something. But then you put that picture in the right frame, and it suddenly seems to be transformed. It needs to be presented with a frame in order to really show off the best aspect of the picture.

The integration running in your business can be like a painting hanging in a gallery but it’s in a dark room, surrounded by other paintings and just pinned up on the wall. It’s there but anything in the picture is lost.

But take that picture and put it in the right frame and hang it in a well-lit room and suddenly you realise what the picture is, and it becomes the star of the gallery. Integration is key to your business moving and using the data behind every transaction, every query from customers and partners, every update to business records and a thousand other activities. But do you really know what’s happening with your integration products?   Are they running? What are they doing? Do you know what their key status indicators are showing?

Sure, you can dive into the tooling that comes with each product, but wouldn’t it be good if you could see it all on a single screen, and dive into any aspect easily? Would that not be showing you what’s happening in the best way and ensuring you see what you want to see? This is now what’s available with the latest release of Cloud Pak for Integration which was announced on November 22^nd 2022. For customers buying new entitlements to Cloud Pak for Integration, there is 6 months of entitlement to Instana Observability (self-hosted). This comes with a specific set of Instana sensors to enable monitoring and tracing for the integration products and some additional components or functions. This will allow customers to get a clear understanding of what is happening with their integrations and in their business.

What else is new in latest release of Cloud Pak for Integration? It’s now easier and quicker to build, deploy and manage integrations. When defining integration capabilities as part of a solution, customers using the latest release can now deploy and manage these as a single unit. So, when building integrations that might comprise multiple separate MQ instances and Event Streams deployments, these can be handled as a single unit of integration.

Additionally, if you use Aspera to move data rapidly over long-distance or lossy networks, the new inclusion of the Aspera Proxy Gateway enables its use in a wider range of deployment configurations beyond the enterprise.

The IBM Integration portfolio includes so many capabilities – what else is new?

One of the core products – IBM App Connect is now available as a managed service: IBM App Connect Enterprise as a Service on AWS. This leading enterprise integration product is now available as an iPaaS. Whether looking to connect to cloud apps, or multiple enterprise applications and systems, IBM App Connect Enterprise offers a fast track to integrating your business needs. Pre-built templates of integrations, no-code integration design, and AI powered mapping and transformation assists accelerate your integration solution from none to done. As a fully managed integration offering on Amazon Web Services (AWS) IBM App Connect Enterprise SaaS is provisioned, patched and upgraded for you without service downtime. Find out if it meets your needs with a free trial.

In addition to these important new capabilities there are also enhancements for IBM MQ which has announced MQ V9.3.1. This is the newest Continuous Delivery release with enhancements to the MQ Web Console, and also improvements to allow message expiry to be set on a streaming queue which creates new ways to leverage this feature.

And customers using z/OS solutions benefit from enhancements to both IBM MQ on z/OS V9.3.1 and IBM Integration Bus for z/OS V10.1. For MQ customers there are SMF enhancements delivering improved queue analytics. Client channel buffers now use 64-bit storage increasing concurrent client numbers, and there is also streaming queues support for shared queues. Integration Bus customers get access to VSAM and QSAM datasets directly from integration flows. Additionally there are z/OS Explorer plugins providing access to z/OS assets from the Integration Bus Toolkit.

With so much new content delivered you have to see it to believe. And so it’s a good job Instana is there to help with Observability.

The new Cloud Pak for Integration 2022.2.1 delivers years of support for your business

Everyone has their own tastes in music. It could be classical, or 80s power ballads, or some heavy rock, or maybe some indie music. (80s music is clearly the best). But picking a selection of music that works together can be tricky. You don’t want to just listen to the same song. But equally a totally random set of discordant music and tunes doesn’t work well. You might create different playlists to meet your moods. In the old days the album (LP) would have been designed for listening to as a complete item. Some of these will have greater staying power than others. You are unlikely to listen to Christmas music playlists in July, but you might have a ‘mixtape’ playlist that works for lots of different uses: working out, cooking, driving, chilling. And you can come back to that again and again as it always has the right mix of music.

That’s what IBM has just announced with Cloud Pak for Integration 2022.2.1. Normally I would blog about the announcement on the day the letter is published. This week also saw the Hursley Summit for European customers which was very well attended with no far off 100 customers and partners as well as numerous IBM experts together in Hursley House. It was just like past events and we even had some nice weather too.

This latest Cloud Pak for Integration release is a new Long Term Support Release (LTSR). Unlike application versions which can be more rapidly deployed and removed, the integration connecting core parts of the business infrastructure tends to be more long-lived and even if integration components have been containerized and are completely decoupled, there can be a preference to reduce the number of migrations to apply to the integration instances. Having the ability to deploy integration components and get support on them for up to 2 years helps address this. As part of this move, it will be possible to move between supported OpenShift EUS releases (even numbered OCP releases) to ensure that the complete stack is supported for 2 year period. And if you want to continue to deploy the integration products ‘standalone’ not as part of Cloud Pak for Integration on OpenShift you can continue to benefit from each product’s support lifecycle (including those with a 5+3 policy).

Aside from Cloud Pak for Integration being now available as a LTSR what else is part of the announcement? There are a number of additional enhancements and new features covering both Cloud Pak for Integration itself, the components within Cloud Pak for Integration and also the separate integration product offerings.

For Cloud Pak for Integration customers, they will find it easier to deploy as the requirement for the Platform Navigator to have access to RWX storage has been removed. This could be an issue in the past when deploying on public cloud, so by enabling deployment with RWO storage this restriction is removed. Also in the storage area there is a new offer for software-defined storage. There is now 12 months access to Spectrum Fusion (6TB primary storage including OpenShift Data Foundation essentials, 6 TB backup storage and 6TB metadata management). This doesn’t impact existing customers with access to the previous offer. This offer is only available for new customers of Cloud Pak for Integration for their initial purchase.

Also, for Cloud Pak for Integration customers there are enhancements that provide new value when deploying API Connect under the Cloud Pak for Integration entitlement. There is now the option to deploy the API Connect Portal and Manager on z IFLs running OpenShift. This allows customers who are providing API-led access to z assets and data to have the API access closer to the assets. Additionally, there are improvements to the co-authoring support, making it easier when creating new APIs and the associated access to data. And for API test generation there are new features extending the ‘auto test assist’ capability to make it possible to run more tests automatically with targeted data to provide more extensive test coverage without taking additional resources or skills. Deployments of API Connect can now take advantage of 2-site DR configurations.

Customers deploying App Connect under the Cloud Pak for Integration entitlement get additional Smart Connectors, including the ability to use Connectors with the Toolkit and not just Designer. And for some outstanding innovation we would encourage customers to look at ‘Goal Oriented Flow Assist (GOFA)’. Imagine your business needs a new integration flow created to meet a business need. Your business team knows what they want, but there are only a few integration specialists and getting time with them will delay progress. With GOFA the business team can simply write in English text what they want to do and the desired flow will be created as they type to match their description. This will help to accelerate progress, and the integration specialists will now have much less to do when they are available to work on this integration.

For Event-led integration there are updates to align with the latest levels of Open Source components. A later version of Kafka is now supported as well as newer versions of APICurio and Strimzi support is updated for use with OAuth for identity and authorization checks.

Aspera High Speed Transfer Server gets updated to V4.3 and also now leverages the Foundation Services Audit Logging which ensures that Aspera logs can be collected and reviewed alongside other logs.

As well as updates to Cloud Pak for Integration as described above there are additional new enhancements and updates to the integration components outside Cloud Pak for Integration. IBM MQ announced V9.3 which is also a new LTSR, making the many new features delivered in the 9.2.x CD stream available for the LTSR customers.

For API Connect customers they have a new LTSR release as well (10.0.5) and also API Connect will be available as a SaaS offering on AWS at the end of June.

DataPower have announced a new physical appliance – the X3.

App Connect for Manufacturing gets an update to support App Connect 12 and to offer new license terms and deployment options.

And finally, Aspera Enterprise on Demand gets an update to align better with other IBM subscriptions.

Going back to our music analogy, this is an incredible ‘full-stack’ playlist. Good for every occasion, every integration need and every season. With this you won’t be forced to listen to Christmas music in July. Or find your business trying to update resources using APIs, or deploying Java gateways in the DMZ.

Interested and want to know more?

Try Cloud Pak for yourself in a free 2 week hosted trial
Read more about automation and integration at this Integration content hub 

Think or Listen? It’s better to do both.

IBM Think 2022

It was good to see IBM get back to holding in-person conferences this week with ‘Think 2022’ taking place in Boston. Think is the current incarnation of a public conference covering all IBM technology and solutions that has been running for many years. This year the launch Think event will be following up with multiple ‘Think on Tour’ events, perhaps coming to a city near you. Check out the list of cities at the bottom of this blog.

In addition to Think there are other in-person events happening, like the Hursley summit I mentioned in my previous blog, and hopefully many more events as well, as we get back to seeing each other not just on our laptop screens.

I didn’t get to Think in Boston, but I am certainly hoping to get to a few different Think on Tour events. You might expect I would want to be there to present some of our latest integration solutions, but that’s not the highlight for me. Instead, it is those discussions you have before or after presenting that make it a successful event for me. It best when you are able to have a conversation in the corridor, or over a meal or a drink with a team from one of our IBM customers. Those times where I don’t have a presentation ready, but instead the customer will talk about their business, and what they are trying to do. And I am there to listen.

Only by listening to the customer can we really understand what they need and figure out what the best path forward for them might be. I have been lucky enough to be attending conferences and travelling around the world to visit customers for more than 2 decades. And while I might be invited to these locations to speak to customers, in truth I am going there to listen. By listening to what our customers have to say, we can both better understand the issues they are hitting now, as well as the future goals they want to achieve. And once we understand those, then we can have more meaningful discussions about how IBM can help them, both today and tomorrow.

Having listened I then share these experiences with my product management and engineering colleagues to help us better shape tomorrow’s products.

The last 2 years have been a big change in how we work, and while it has been good to be able to have some online calls with customers to present to them about Cloud Pak for Integration, and how they can transform their businesses with IBM Integration solutions and Red Hat OpenShift and the flexibility of DevOps and CI/CD, it has not been the same. I don’t want to present to a customer, but to talk with them, and to listen to them. Together we can then both benefit, and together we can both succeed.

This benefit of listening doesn’t only apply to me. I know that for many customers, the benefit of events is talking to their peers at other businesses who will be experiencing many of the same issues, but might be at a different stage of their journey or addressing slightly different concerns. Sharing knowledge and encouragement helps everyone, and provides valuable insight beyond even the best presentation session. I hope you make it to a Think event this year, or some other in-person event with IBM. But don’t just Think. Be sure to listen as well and have those conversations that matter the most. If you are reading this, maybe we will both be at an event together this year. Come and tell me what you are trying to do in your business. I promise to listen.

Integration is infrastructure. Does your infrastructure scale? Learn more about IBM Cloud Pak for Integration at the Hursley Summit (June 8th-9th 2022)

It’s often said that it can be hard to show the value of integration because the point of integration is for something to simply work. It typically is designed to ensure the flashier parts of the business (the applications) deliver value to the business, and it does this by ensuring that behind the scenes applications seamlessly connect and exchange data.

A common analogy for integration is the plumbing and electrics in the house, with the applications representing the appliances that might use the plumbing or electrics. You might change the appliances frequently, but you are unlikely to want to rewire or redo the plumbing in the house very often. It’s your infrastructure, not a temporary patched solution. It has to be ready and adjust to different needs.

A typical UK kettle

However, there can be challenges. In a house in the UK a kettle typically draws up to 3KW. But imagine having a need to power more and more kettles. You would soon face a problem supplying enough power through your existing electrical wiring. You are unlikely to need more than one kettle, so you might think the problem doesn’t arise, but there are new high devices that require high amounts of power: Electric Vehicle chargers and air-source heat pumps. Both can require high power rates, such that your home supply might need to be upgraded to cope. This can be disruptive and expensive, and not something you can do easily or quickly.

Electric Vehicle chargers

Now let’s consider the similarities with integration deployments. Imagine the following scenario: You have deployed a set of applications, and have used some integration products to tie them together, exchanging the data and ensuring each application is delivering value and meeting needs. Then as business needs change you replace one or more of the applications. Maybe to meet new business opportunities or to respond to changes in customer behaviour.

The new application has really met the market need and seems to be really popular. You are seeing increasing growth. More instances of it get spun up, and these are driving more connections and more data to the other applications and back-end systems. You start to see that those applications need to be scaled up as well. But with more and more data being requested, exchanged, transformed and updated, everything is slowing down as it moved through the integration components. You look at whether you can deploy more instances of the integration components, but the product has not been designed to scale efficiently and would consume more resources for little benefit in scale if deployments were increased.

You now are faced with the need to change integration products to better meet the growing needs of your applications, all initially sparked by growth in a single area of the business, but because everything is connected, the growth impacts all systems. And if you change the integrations which connect all parts of your business, you need to update every part of your business as part of the roll-out of a new integration layer. Even when there might be one component of the integration solution that can’t scale, all parts of the business can be affected by this issue.

This issue is why it is critical to choose an integration solution that meets needs of not just a single project but is designed for the longer term.  One that can scale, but can also solve different integration needs. Sometimes data needs to be simply and rapidly moved between systems. Other times it needs to be transformed between applications. Or maybe the data needs to update a system of record. And maybe it needs to be available for users anywhere in the world. Not just scaling to any volume or speed, but securely managing all connections and data movement. If your integration solution of choice fails in these areas, then just as you become successful is when you will find you will hit problems.

If this makes you think more closely about integration, then maybe you should take a closer look at IBM Cloud Pak for Integration. It’s a comprehensive integration solution, designed to scale, with security built-in, and with resiliency and high availability for deployment anywhere.

If you are based in Europe you might want to come and hear directly from the experts in IBM Hursley who have built and support much of Cloud Pak for Integration. We are delighted the Hursley Summit is back on June 8^th-9^th in 2022. These dates are for European customers, and the hope is to offer North American customers their own summit later in the year. Don’t forget we have an excellent customer briefing centre in Hursley and you can arrange to see our experts 1-1. If you are interested, the event page is here, with details of the agenda and how to register for the limited number of places. I hope we see you there.

Can automation really improve my integration deployments? Find out what Cloud Pak for Integration can do today.

It feels like we have been hearing about Automation for years. Whether various human like robots in science fiction to more everyday examples like the automated production lines you see in sophisticated factories, there is a fascination in seeing jobs that previously were complex, time consuming and needed human input being simplified, and automated, with associated benefits in time and expense.

Automation is now increasingly being applied to computing tasks throughout the infrastructure for multiple reasons:

• Faster development/deployment cycles
• Error reduction
• Reducing skills requirements
• Cost reductions
• Repeatability/reusability

However, a crucial step in automation is not trying to address the problem as a whole but rather to break down the entire process to individual steps and to apply automation to each individual step. Much of the focus of IT automation over the years has been at the business process level, whereas the key to implementing achievable and sustainable automation is in applying automation to the multiple low-level steps essential to actually progressing a business process. These steps are the individual applications interactions and data movements that underpin business activity, and which typically are the focus of integration in IT infrastructure.

Integration has been seen as a burden for many years due to the high level of skilled resource needed to implement any new integration, or even to maintain existing deployments. And for businesses to take advantage of new opportunities by taking advantage of API-led integration, it is critical to ensure that the cost and time involved in building out and deploying these API integrations is kept as small as possible.

This is one of the reasons that IBM has been focused on optimizing, decomposing and automating integrations as part of Cloud Pak for Integration and one of the concrete ways in which this is demonstrated is through automation of API Test generation.

When a business is looking to expose data through an API they create the definition using an OpenAPI schema, allowing them to describe the data to be accessed, who can access it, and other mechanisms to provide and control that access. It’s important to keep this creation simple, but there is a key need to then ensure that the systems respond as expected, and this requires testing. Building out and running tests for any new integration is a substantial effort and APIs are no exception.

What IBM has done is to break down the need for testing into a number of different steps and to apply both automation and AI to those steps with a view to solving the problem as completely and comprehensively as possible. By training the Watson AI engine that comes with Cloud Pak for Integration, it can analyse the OpenAPI Schema and automatically create tests to provide coverage of the expected use of the API once it goes into production.

The next clever step is that once it is in production, the AI engine will continue to review the workload using the new API, comparing it to the schema and the tests already created and will add new tests to fill any gaps it sees, as well as helping to train the engine better for the next API. Not only are new tests created but usable data to run through the tests as well. Plus, there is setting and tearing down the testing environment as another automated step.

Now let’s consider what would have been the challenge of building a new API and moving it to production. A substantial part of the effort involved in that would have been in testing it effectively and thoroughly. IBM Cloud Pak for Integration can automate a large part of that for you. Think of a factory moving from assembling everything by hand and compare that to where you have automated manufacturing with an assembly line and machine tools performing most of the tasks. Finally your business can leverage that same advantage.

Check out this video to see a demo

Now try it for yourself with our free 2 week trial of Cloud Pak for Integration hosted on IBM Cloud. What are you waiting for?

The gift of choice with Cloud Pak for Integration 2021.4.1

Whatever you celebrate at the end of the year, you will want to choose what you do, and where you do it. The freedom to choose puts you in control. And that freedom to choose is at the heart of the latest release of Cloud Pak for Integration 2021.4.1. Read the announcement here.

The last 12 months have seen tremendous innovation delivered in Cloud Pak for Integration, with new features, and existing features getting enhanced and improved in each release. But if I had to give a single theme to this release it would be the increase of customer choice.

Choice can of course be a bad thing if it is overwhelming, but in considering this enterprise deployment of integrations, this is more about ensuring that a considered choice can be made between specific set of alternatives, with likely clear preferences. Let’s look at the features and see why.

The first new capability to call out is the Event Endpoint Management feature that was first delivered in the initial Cloud Pak for Integration release in 1Q 2021 and has been enhanced in each release since then. 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 back-end 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.  

Options for chargeable entitlement

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 as well as 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.

Next up is choice of a different sort. This time it is the freedom to choose suggestions enhanced by AI. Once again this is an additional enhancement to the AI powered API Test Generation feature introduced earlier in the year. 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 increasing burden on the business. AI-driven API Test generation is designed to automate the process of generating these API test cases by using 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 which makes it easier to stand-up and tear down tests, but key in this latest release is the use of deeper AI. The 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. These Watson insights suggest what tests to create from the templates it offers to give the best coverage. The top 3 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.

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. In order 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 to provide assistance using AI suggestions for mapping and transformation. Something else to help with building integrations more quickly is the Automation Assets component (previously called Asset Repository). 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.

As with increasing customer choice by enabling 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 included Kubernetes operators, MQ and MQ Advanced must be deployed using a customer-built container image.

Finally, in terms of new features available in the Cloud Pak for Integration 2021.4.1 release, there is a new feature to add choice and additional capabilities around 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 IBM License Management Tool for non-container deployed software. While these tools report on deployment for audit as required, the information isn’t typically easy to access for any of the users of the software. This can lead both to lack of visibility when customer deployments reach entitlement limits, and also lack of ready access to the information can hamper the ability to implement departmental cross-charging, or even understanding different workload deployment patterns. With the latest release, 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.

Whatever you celebrate this holiday season, there is plenty to enjoy in Cloud Pak for Integration 2021.4.1, with the question being which gift will you unwrap first? Why not give yourself a gift of a trial use of Cloud Pak for Integration. Explore the hosted trial environment here.

A time for gift giving. Why using Cloud Pak for Integration can be rewarding.

We are told that feedback is a gift. What’s also a gift is a gift card. IBM is giving you the chance to both give and receive. You give IBM feedback about your use of Cloud Pak for Integration. IBM then rewards that feedback with a $25 Visa gift card.

IBM Cloud Pak for Integration is a cloud-native integration platform designed to deploy in any environment simply and repeatably by taking advantage of Red Hat OpenShift, and to enable any integration to be developed and deployed quickly and without specialist skills needed across the integration lifecycle. Integration is essential to move your critical business data from where it is created to where it needs to be consumed. With your business depending on it, you need the secure, reliable, robust and scalable Cloud Pak for Integration connecting your infrastructure.

To provide feedback, you need to follow the link below to Gartner Peer Insights. There, once you sign up with your business email, you can simply leave a review with feedback about Cloud Pak for Integration. And your reward for this would be a $25 Visa gift card. It is the gift giving season after all.

Here’s the link to review CP4I on the Gartner Peer Insight page – then click the sign up for free button on the page to quickly create a Gartner Profile. You can then complete the survey. Remember to use your corporate email, and verify this. Then write a unique review of your own, using complete sentences. And check your review status here .

If that weren’t enough, maybe you are a customer who uses IBM App Connect or IBM API Connect and haven’t yet made the leap to Cloud Pak for Integration? We also have links for you here:

IBM App Connect Reviews

IBM API Connect Reviews

IBM wants your feedback, so remember to use these links and provide your honest comments, and the gifts should then follow.

’tis the season after all.