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.


Add a new idea Subscribe
Status Not under consideration
Workspace App Connect
Created by Guest
Created on Jul 23, 2025

RELATED IDEAS

Support for Native Active/Passive (Active/Standby) High Availability Mode in App Connect Enterprise Operator Deployments

We request IBM to enhance ACE Operator-based deployments on OCP to support a native Active/Passive (or Active/Standby) High Availability deployment model, similar to the existing IBM MQ Native HA architecture.

Currently, ACE Operator deployments operate in an Active/Active model by default when multiple replicas are configured, all Integration Runtime (IR) pods run simultaneously and accept traffic. While this is suitable for stateless, HTTP-based integrations with built-in client-side failover, it does not meet the requirements of TCP/IP-based server applications that require strict single-endpoint connectivity and zero-downtime failover.

This limitation creates critical challenges in regulated environments where service continuity and connection persistence are mandatory.

Use Case:

Our organization deploys ACE-based integrations for financial institutions that interface directly with central banking systems (State Bank). In one such integration:

  • ACE acts as a TCP/IP server using a TCP Input node .

  • The external client establishes a single, persistent TCP connection to the ACE pod.

  • The client does not support reconnection logic, multi-homing or failover to alternate endpoints.

  • Any service interruption (even for 10 - 15 seconds during pod restart) is detected as downtime and may result in regulatory penalties .

To ensure continuous availability, we require a standby ACE pod that is:

  • Pre-initialized and ready to take over instantly.

  • Not actively accepting traffic until failover occurs.

  • Automatically promoted to active upon failure of the primary pod.

  • Seamlessly accessible via the same service endpoint (e.g., using a shared virtual IP or service routing).

This behavior is already achievable with IBM MQ Native HA, where one Queue Manager runs active while others remain in standby, with automatic failover orchestrated by Kubernetes. We are requesting a similar capability for ACE.

Idea priority Medium
  • Admin
    Atif Siddiqui
    Apr 6, 2026

    Muhammad,
    Thank you for taking the time to raise this request to IBM App Connect Enterprise (ACE) team. We recognize the importance of high availability and service continuity in regulated environments, particularly for TCP/IP–based integrations that require persistent connections and minimal downtime.

    After careful review, this RFE will not be pursued. The request, as described, seeks a native Active/Passive (Active/Standby) high‑availability model for ACE Operator deployments. Currently, there is not enough demonstrated demand for this stateful processing approach in containerized ACE workloads to move forward with an enhancement.

    In addition, while the request is framed as an Active/Passive HA requirement, the underlying need appears to center on continuity of TCP server connections. Alternative architectural approaches (such as active/active deployments with centralized or external TCP routing) may be more appropriate to address that requirement and would be better evaluated through a more narrowly scoped, TCP‑focused enhancement request.

    If TCP connection continuity is the primary concern, we recommend raising a more specific RFE focused on that capability for further consideration.

    Reply

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.