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 Aug 28, 2015

Logging Renderers

Logging in Trace nodes can be very time consuming to develop. For example, to log the XMLNSC structure as a human readable XML string the following must be written in the trace node.


This becomes very cumbersome. Also there is no easy way to format the XML with line breaks and tabs. In the Java world this is called 'pretty print'.

In other modern languages and frameworks, this is very trivial. In many cases a ToString() is simply called on the object.

Idea priority Medium
RFE ID 76271
RFE Product IBM App Connect Enterprise (formerly IBM Integration Bus)
  • Admin
    Ben Thompson
    Oct 3, 2021

    Idea / RFE Review. Apologies for the length of time this RFE has been in Uncommitted Candidate status. Further to the earlier commentary on this RFE, the product has actually evolved significantly in this area with several features. The new unit testing framework which was introduced in ACE 12 provides a new Message Assembly file format (with extension .mxml) which allows data representing the logical message tree to be created and captured for unit testing purposes. We also have the ability to push data to an ELK stack (we began with flow statistics, and then later in ACEv12.0.2.0 we have added monitoring message event distribution too), and also provided JSON formats for logging renderers too. Given these large advances, and a lack of any further detailed feedback on the earlier questions posed, we are now closing this idea as delivered. On the off chance that you feel something else specific is still needed then please feel free to raise a new idea against the latest software levels and we would be happy to consider.

  • Guest
    Jul 11, 2016

    Thanks for raising this RFE, and apologies for the delay in responding. We're updating the status of this RFE to Uncommitted Candidate to reflect that we're open to future improvements for helping users log data which is sent to backend systems for purpose of easy mocking during unit testing. The trace node is specifically intended to trace the logical tree structure which is passed between flow primitives rather than an on-the-wire serialized format, so we're not necessarily in favour of using the trace node for this purpose as this could easily confuse users. We also have the unit test feature available in IIB which provides a test data capturing mode (a nice write-up is available here: which might be the best place to cater for this high level requirement. Also note of course we have the Monitoring tab which can be used to capture a serialized form of the data from a particular point in a message flow.
    Status of the RFE is updated to Uncommitted Candidate, but any further information that you can provide to outline how we might meet this need but in areas other than the Trace node would be much appreciated. Best Regards, and thanks once again for raising this.

  • 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