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 Future consideration
Workspace App Connect
Created by Guest
Created on Jan 24, 2013

Deploy individual flows in an Application (a check box that allows to select individual flows when building the bar file)

In the "Prepare" tab of the bar file create a check box before every flow (other resources also) that makes it possible to select which message flows (resources) should be included when deploying the bar file to the broker.

I think that implementing this feature for the other resources in the application (maps, message sets, XSD and WSDL files) should be very good also.

Idea priority Medium
RFE ID 30569
RFE Product IBM App Connect Enterprise (formerly IBM Integration Bus)
  • Guest
    Sep 7, 2020

    Thank you for raising this RFE and apologies the status has remained in Under consideration state for so long. Typically an Application holding multiple message flows is used when those flows have some kind of established relationship to one another (eg used for a request-reply scenario, or processing steps utilised by a particular LoB application etc.) ... and typically due to the application deploy behaviours, the flows tend to be updated at the same time, deleted at the same time etc. In other words in many ways you can consider an application as a set of inter-related artifacts with the same lifecycle. That said, there are some situations where you may want to preserve the status of some message flows (such as stopped / started) within the application. The concept of only updating certain flows at the server level (which used to be the product approach in earlier versions where the entire server is seen as a single "bucket" with "top-level content") also appears to be a diminishing use case with the popular rise of containers. That said, the possibility for "delta deploy" of only certain flows in an application, is technically feasible with the architecture improvements that came with ACEv11, so we intend to retain a watching brief on this RFE. For now the 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

  • Guest
    Jan 24, 2013

    Attachment (Description): Example file