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 Future consideration
Workspace App Connect
Created by Guest
Created on Oct 4, 2012

Cloned message flow application across execution group

message flows that leverage aggregate control/request/reply nodes in WMB 7.x and beyond cannot scale across EGs within the same broker unless changes are made to the aggregate reply node to differentiate reply node "name" per EG.

Idea priority Medium
RFE ID 27184
RFE URL
RFE Product IBM App Connect Enterprise (formerly IBM Integration Bus)
  • Guest
    Reply
    |
    Jan 8, 2021

    RFE Review. Although the product has evolved to allow independent integration servers running in containers to use a remote default queue manager for the purpose of defining the queues used by aggregation nodes, we still have not allowed users to be able to scale multiple servers to use the same queue so that servers can pick up one another's in-flight aggregations. So - despite being open for several years now (and with relatively meagre community votes), there remains value in this use case especially in more modern container based architecture topologies. We will continue to monitor and status is maintained as Uncommitted Candidate.

  • Guest
    Reply
    |
    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

  • Guest
    Reply
    |
    Apr 15, 2013

    Thanks for raising this requirement. We'd like to be able to process aggregations across multiple execution groups in time, to allow for the scaling scenarios you mention. In the mean time, do take a look at the embedded cache support in MB 8001, which allows you to share transient/cached state across multiple execution groups and brokers. The aggregation nodes do not currently take advantage of this, but we would like them to. Regards