Skip to Main Content
Integration


This is an IBM Automation portal for Integration products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.


Status Submitted
Created by Guest
Created on Jul 15, 2025

Enhance webMethods CloudStreams Listener Support for Containerized MSR Environments

Currently, WebMethods CloudStreams listeners (e.g., for Salesforce) are designed to operate in traditional static Integration Server deployments. This architecture is not well-suited for containerized environments like Microservices Runtime (MSR) running on Kubernetes (e.g., AKS), where dynamic scaling and stateless services are the norm.

When an orchestrator scales out MSR containers, each replica independently activates its own listener instance. Since clustering mechanisms like Terracotta are not viable or recommended in containerized environments, this behavior leads to duplicate message processing, loss of message state, and configuration inconsistencies.

There is a pressing need to modernize CloudStreams listener behavior to align with container-native principles. Specifically:

  1. Prevent message duplication across replicas by enabling exclusive message consumption across MSR instances, possibly via distributed locking or a consumer-group-style mechanism.
  2. Enable externalized, declarative configuration management for listeners (using application.properties file), avoiding per-instance manual setup or workaround.
  3. Support persistence of the replyId in LAST-RECEIVED mode, allowing safe redeployments without reprocessing already handled messages.
Idea priority High