Skip to Main Content

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 (

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 ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Workspace App Connect
Created by Guest
Created on Aug 28, 2015

Clustered Deployment

Deploy bar file to multiple brokers at same time

where we can group nodes under a cluster and deploy and it should be easy to remove the cluster when needed.

Idea priority Low
RFE ID 76287
RFE Product IBM App Connect Enterprise (formerly IBM Integration Bus)
  • Admin
    Ben Thompson
    Aug 15, 2021

    Idea / RFE Review. Apologies for the length of time this RFE has been held in Uncommitted Candidate / Future Consideration status. When this suggestion was initially raised, the architectural topic of federating multiple message brokers across a network was a regularly discussed design pattern. Over the last 5 years, with the explosion in container-based architectures, the thinking around how to easily deploy and maintain multiple replicas of an integration has evolved and rather than "clustering" using built-in product logic, we are now pursuing a strategy of relying on a common kubernetes layer in the architecture to assist with this kind of use-case. Given this, and the very low votes on this request, unfortunately on this occasion we will not be taking this idea any further.

  • Guest
    Jul 5, 2016

    Thanks for raising this RFE. We are interested in cloning behaviour more easily across multiple affiliated integration servers with features similar to the suggestion. Status is updated to Uncommitted Candidate.

  • Guest
    Oct 7, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - WebSphere
    Product family - Integration
    Product - IBM Integration Bus (WebSphere Message Broker) - IIB

    For recording keeping, the previous attributes were:
    Brand - WebSphere
    Product family - Connectivity and Integration
    Product - IBM Integration Bus (WebSphere Message Broker) - IIB