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 Mar 23, 2021

Enable tracing nodes per flow, not per integration server

In ACE v11, you can only enable trace nodes for an entire integration server, not just at a flow or application level (as you could in iib v10).

As not all customers that migrate to v11 will choose to adopt the small container approach, enabling trace nodes at an integration server basically makes this feature useless since there is to much data generated.

Since node managed environments are still supported, customers should have the option to enable trace nodes at the level that fits them. Regardless of the size of the integration server (at least provide the option to enable it per application).

Support's reply was "we would expect a single application per container" that is fine on it's own, but that doesn't fit with everyone's environment. More logically the customer has the option to choose this level. Even a single application with multiple flows can generate to much output to make trace nodes usefull.

Idea priority High
RFE ID 149450
RFE Product IBM App Connect Enterprise (formerly IBM Integration Bus)
  • Guest
    Jul 28, 2021


    One of GTS customer requested this feature to be added on ACE as it was on IIB.
    This will give them better results when they need to trace a flow.

  • Guest
    Apr 19, 2021

    RFE Review. Thank you for taking the time to submit this idea for enhancement, which we agree would improve the product. Historically, the "-f" flag on the mqsichangetrace command was only reliably used for trace nodes rather than for the usertrace and servicetrace options on the command … so when ACEv11 was released it was easiest to remove this capability rather than establish it consistently for flow only usage. To reflect our approval of the idea, the status of the RFE is updated to Uncommitted Candidate.