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 Delivered
Workspace App Connect
Created by Guest
Created on Jul 10, 2017

Combine monitoring events with test injections

I like the ability to use the flow exerciser to create the possibility of test injections (for a limited set of nodes)

But, I want to combine the monitoring events in a running environment with the possibility of use those recordings doing test injections for all possible input nodes. That what open up a whole other world of testing in every perspective.

So basically, form my perspective the flow exerciser is used by the developer, and the functionality of test injection is dependent of what the developer has tested and not tested. So instead, when combining the nice feature of monitoring events from a running environment (so we can record the truth) and being able to reuse that as injections makes testing any solution super simple.

To enable this test injections needs to be supported by all nodes (today injections are only supported by a limited amount of nodes) and the ability to actually record real traffic to reuse with injections.

Idea priority High
RFE ID 107522
RFE Product IBM App Connect Enterprise (formerly IBM Integration Bus)
  • Admin
    Ben Thompson
    Sep 19, 2022

    Idea / RFE Review. Since the last comment in 2020, in ACEv12 we have now shipped the unit testing feature which provides the ability to capture messages ready for reinjection in the form of .mxml files which represent the logical tree after transport and protocol parsing has occurred. This is a much more efficient way of capturing test material than relying on Record & Replay which brings with it a pre-requisite of database and MQ infrastructure. Status of the suggestion is updated to Delivered.

  • Guest
    Oct 5, 2020

    RFE Review. Thank you for taking the time to raise this enhancement suggestion and apologies it has been in Submitted status for a while. This is a very interesting idea. We are looking deeply into how to improve our unit testing experience with future versions of the product, which is likely to include better mechanisms for recording unit test data which represents the logical message tree at various points in a message flow. Generating these message assembly views based upon recorded monitoring events sounds like a reasonable use-case. Status of the RFE is updated to Uncommitted Candidate.