Blogs

Automating IBM Cloud Pak for Integration on CodeReady Containers with GitOps
This article details how to automate the setup of IBM Cloud Pak for Integration on local OpenShift using Red Hat CodeReady Containers and ArgoCD. By combining custom shell scripts with a GitOps App-of-Apps pattern, the framework replaces manual CLI installation with a repeatable, single-command deployment workflow. Developers and integration architects can fork the repository to easily provision production-inspired environments for testing, demos, and workshops.

Connect Bob to Your Local OpenShift Cluster Using the kubernetes MCP server
This article explains how to connect the AI coding assistant Bob to a local OpenShift or CodeReady Containers (CRC) cluster using the Kubernetes Model Context Protocol (MCP) server. By leveraging the uvx package executor, Bob automatically utilizes your existing kubeconfig and active authentication context without requiring dedicated plugins or complex credentials. Once configured, developers can query their OpenShift environment, inspect custom resources, and troubleshoot failing pods using natural language.

Containerizing IBM ACE: A Blog Series - Container Startup Optimization
This article explores techniques to optimize container startup performance for IBM App Connect Enterprise (ACE) integration servers. It compares three distinct container setup strategies—a cold-start base image, a prebaked warm-start image, and an init container approach—to minimize heavy resource usage and boot times during runtime.

Creating a generic log node using context trees
This article demonstrates how to build a dynamic, reusable logging subflow in IBM App Connect Enterprise (ACE) using ESQL context trees and CONTEXTREFERENCE. It explains how navigating the context tree enables automatic extraction of runtime metadata—such as node names, execution paths, and payloads—without manually wiring data across flow nodes.

Building a Generic Connector Between IBM App Connect Enterprise (ACE) and Azure Service Bus
This technical article details how to build a custom, generic integration connector between IBM App Connect Enterprise (ACE) and Azure Service Bus using JavaCompute nodes and the official Azure Service Bus Java SDK [1]. It walks through overcoming legacy JMS client instabilities, handling idle connection drops, and bypassing limitations of out-of-the-box connectors to dynamic payload and property handling across multiple queues

Containerizing IBM ACE: A Blog Series - Scoping your runtimes
This article explores strategic criteria for bundling and isolating IBM App Connect Enterprise (ACE) applications within container runtimes. Written by Matthias Blomme and Kim Meynendonckx, it provides practical guidelines on how to group integration flows based on team ownership, deployment cadences, security boundaries, resource consumption, and failure domains to avoid common architectural pitfalls in containerized environments.

Containerizing IBM ACE: A Blog Series - Things to Consider in Containers
This article outlines essential architectural considerations when containerizing IBM App Connect Enterprise (ACE). It addresses challenges with state persistence, networking, autoscaling costs, resource management, and configuration injection, providing a practical "heads-up" guide for developers moving traditional ACE workloads to Kubernetes or other container platforms.
.png)
