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 Nov 9, 2021

Not able to delete the components running under Default_Application on Integration server in App connect

Hi , Recently we have migrated our integration Nodes from IIB to ACE , post migration we have observed that the independent messageflows and dependents were all running under Default_Application and there is no option to delete the msgflows/jar/msgset files from this defaut application. The delete option would be needed for developers and for adminstrators which will be veyhelpful to delete the respective flows and dependents from UI and toolkit rather deleting complete defautl_application , as defualt_application contains many flows and other dependents. .
Idea priority Medium
  • Admin
    Ben Thompson
    Nov 25, 2021

    Idea / RFE Review. Thank you for taking the time to raise this enhancement request but unfortunately on this occasion we do not intend to take this idea forward. Applications and libraries as groupings for artifacts deployed to the product runtime have been a core part of our architectural strategy since they were first introduced ten years ago as part of WMBv8. Since that time, we have tried to encourage the use and adoption of applications by all users who have previously used independent resources defined in integration projects. As noted, in ACEv11 and ACEv12 you can still deploy older BAR files that contain independent resources, but these are deliberately placed into the default application - whose name you can control through the server.conf.yaml file. We believe there are many advantages for the adoption of applications and libraries. Some of these are outlined in this topic from the IIBv10 documentation:

    If you adopt Applications and libraries to group your deployed artifacts, you can successfully undeploy or change one application without influencing another. The product's Toolkit also provides a helpful tool for converting your projects (right-click your integration project and select "Convert to Application or Library" and then choose either "Analyse and Convert multiple projects" or "Convert single project").