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 May 18, 2012

Record and Replay functionality - Inserting more message fields into the recording table when an event monitor gets triggered

Other than the monitoring fields that are currently available (when we create an monitoring event), is there any other way we can insert data into the recording table? Our requirement is that, when we record the incoming message, we need to insert some specific fields in the message to the recording table, so that our custom web admin GUI can display them..

When we created the monitoring event, We could configure Event name, Local transaction correlator, parent transaction correlator, Global transaction correlator to map from some specific fields from the message body. This gets mapped to the table columns EVENT_NAME, LOCAL_TRANSACTION_ID, PARENT_TRANSACTION_ID, and GLOBAL_TRANSACTION_ID respectively when a monitoring event is generated.

The ddl file provided by WMB product (present under the broker installation directory: MQSI\\ddl\db2\DataCaptureSchema.sql) has many unused columns (like KEY_FLD*). There should be some way where we can map the user data while we configure the event monitor or the broker should map it to the table by taking the fields present under some fixed LocalEnvironment section.

Idea priority Urgent
RFE ID 22695
RFE Product IBM App Connect Enterprise (formerly IBM Integration Bus)
  • Guest
    Sep 25, 2020

    RFE Review. Although we have not yet managed to prioritize the implementation of this feature we continue to monitor its popularity. Status of the RFE is maintained as 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
    May 13, 2013


    I use WMB and we also have a similar requirement in our logging framework. Currently, the product only allows the entire message bitstream to be logged. But there is no option to log key fields for each message flow transaction. Without this, it is very hard to search and locate a particular transaction that was processed by a message flow for analysis and replay purpose.

    It would be very good to have this functionality available in the broker record and replay.


  • Guest
    Aug 23, 2012

    Good requirement; thanks for raising. We're keen to make the record and replay feature as flexible as possible, and what you suggest is consistent with this aim. We'll investigate the ability to add custom fields to the record DB for a follow-on release or fixpack.