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
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
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.
RFE Review. As part of our standard approach to RFEs we regularly re-assess those in Uncommitted Candidate status for continued relevance. Despite this request being open for several years, and supported by a relatively small number of votes, we still wish to preserve the status as we feel this would add long-term value to the product. Currently there is a parameter on the API method getJDBCType4Connection which takes an enumeration (JDBC_TransactionType.MB_TRANSACTION_AUTO) which could perhaps be extended with further values to help us with this use case. Also, taking note of the recent comment on this RFE from April 2020, if / when implementing, we would also keep the current default the way that it is right now, whereby database actions across multiple nodes in a flow are coordinated in the same way as they are right now - new settings to commit transactions at the end of the JCN's activity outside of the flow's global commit. Status remains as Uncommitted Candidate.
Output nodes (MQ, SOAP Reply, etc.) should obviously do their work just after commit of database changes, produced by JavaCompute node, and not earlier.
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
Thanks for raising this requirement. We have investigated the engineering required and have a good understand of what is necessary; we will look to schedule this in a follow-on release or fixpack.
Would like a general ability to control when commits takes place whether at the end of a java compute node or elsewhere in other nodes or esql