Skip to Main Content
Integration


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 (https://ideas.ibm.com).


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 (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - 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 Aug 26, 2013

Event monitoring generate alswas transaction.rollback with Excp in case of an error.

In some cases, for instance with the MQInput node, there is no transaction.rollback event emitted when the flow fails. When there is a validation error detected in the MQInput node (validate content and value with parse timing complete) there is a transaction.start event generated together with an transaction.end event with an empty exceptionlist.
Expected was a transaction.rollback with an exceptionList. Transection.end should only be emitted when a flow is successfull..

Idea priority Medium
RFE ID 38434
RFE URL
RFE Product IBM App Connect Enterprise (formerly IBM Integration Bus)
  • Guest
    Sep 23, 2020

    RFE Review. Apologies for the length of time this RFE has been in the status of Under Consideration. We have checked this behaviour on the latest release of the product technology, ACEv11. In this situation, the input message fails validation within the MQInput node, so no transaction.rollback event is ever needed (unlike if a failure occurred in a downstream node of the flow). If you wire the failure terminal of the MQInput node, and also turn on events for propagation from that terminal, then you will receive three events ... transaction.Start, Failure.terminal, transaction.End ... So - the product does provide a means of getting hold of the exception list reflecting the validation failure.
    That said, the RFE expresses disappointment that the Exception List is not available in the transaction.End event. This would be potentially possible, but would need to be a behaviour behind a new property flag as a non-default option in order to avoid breaking anyone relying on the current product behaviour. Given the existence of a serviceable workaround, and the low number of votes (1 vote since 2013) we are unlikely to progress this RFE into the product any time soon, but we will continue to monitor it. Status of the RFE is updated to 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