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.


Add a new idea Subscribe
Status Future consideration
Workspace App Connect
Created by Guest
Created on Sep 25, 2013

RELATED IDEAS

Optimized database connection management

Currently WMB ODBC connections are limited in the sense that all database transactions by default are contained within the scope of the message flow transaction boundary. ESQL Compute nodes have a 'Transaction' property which can be set to Automatic or Commit. In the case where multiple downstream calls need to be repetitively made, using PROPAGATE in an ESQL Compute node, to an HttpRequest node for example, and the result of each of those calls be stored in a database with immediate COMMIT, it is not possible to do so unless multiple DSNs are used. To overcome this, a command other than UNCOORDINATED needs to be used to COMMIT each database INSERT or UPDATE immediately without the need for additional DSNs.

Idea priority High
RFE ID 39605
RFE URL
RFE Product IBM App Connect Enterprise (formerly IBM Integration Bus)
  • Guest
    Reply
    |     Sep 15, 2020

    RFE Review. Apologies for the length of time this RFE has been in the status of Under Consideration. At the heart of this request is really the idea of giving a user of Compute node ESQL, a function which can be called to COMMIT database work prior to reaching the end of the logic of the Compute node and moving the message flow thread to the next node in the flow. In the use case presented, the Compute ESQL is using the PROPAGATE verb to pass the thread on to downstream nodes multiple times ... but the user desires to commit the database work before doing so. This use case can be achieved by separating the PROPAGATE functionality from the database update functionality, and placing them in two separate Compute nodes... thus allowing the "database update functionality" to reach the end of its node processing (and thus be committed) before the next propagation occurs. Despite the product meeting the use case as expressed, we acknowledge that it would be a nicer solution to allow intermediate COMMIT to be forced from an ESQL command within the Compute node. For this reason we are updating the RFE to status Uncommitted Candidate and we will continue to monitor for signs of popularity.

  • Guest
    Reply
    |     Jun 16, 2017

    This is Salla from UMB Bank EBI Team. We second this RFE and please consider this as a high priority item. We see this could be a major block at some point.

    Regards,
    Salla

  • Guest
    Reply
    |     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

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.