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 Jul 29, 2013

RELATED IDEAS

ESQL Scalability & Transactionality Enhancement Required

To assure trasactionality, and scalability, we have converted all database access performed by our large WMB application from ODBC to JDBC - except for a fairly significant portion of the code using ESQL ODBC-only nodes (Database, DataDelete, DataInsert, DataUpdate). Since these ESQL nodes only supports ODBC, this code still uses ODBC. The key advantages of JDBC for the rest of our code are:
1) Support for an XA-compliant Global transaction - thus assuring that different resources managed by different resource managers remain properly synchronized.
2) Support for a connection pool - thus assuring that the solution remains scalable and can operate effectively for high transaction volumes.

We need to see these same capabilities made available to our ESQL code. Thus, we are requesting that ESQL be enhanced to support:
1) Connection pooling
2) Global Transaction participation.

We note that the two obvious ways to go about doing this are:
1) Allow all ESQL statements to use JDBC - and allow the definition of the underlying JDBC connection pool to address the issues
2) Add connection pooling and Global Transaction support to the ODBC code

Either solution is acceptable to us. We prefer the JDBC approach, since it would allow all resources to be administered via JDBC, which would simplify administration.

Idea priority High
RFE ID 37551
RFE URL
RFE Product IBM App Connect Enterprise (formerly IBM Integration Bus)
  • Guest
    Reply
    |     Oct 14, 2020

    RFE Review. Apologies for the length of time this RFE has been in status of Planned for Future Release. Whilst we still approve of this idea, we have not yet managed to prioritize its inclusion in the product. We will continue to monitor. For now, status is updated to Uncommitted Candidate. It should also be made clear, just in case other users are in doubt on this point, that the product does support the use of ODBC when executing global transactions. This aspect does not detract from the wider issues around connection pooling and developer flexibility around mixing ESQL with JDBC.

  • 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

  • Guest
    Reply
    |     Aug 31, 2013

    Thanks for raising this requirement. We very much desire to add flexibility in our database access so that, for example you could use JDBC and ODBC in any of the supported database-capable nodes. This is a high priority candidate for a follow-on release.

  • Guest
    Reply
    |     Aug 31, 2013

    Thanks for raising this requirement. We very much desire to add flexibility in our database access so that, for example you could use JDBC and ODBC in any of the supported database-capable nodes. This is a high priority candidate for a follow-on release.

  • Guest
    Reply
    |     Aug 31, 2013

    Thanks for raising this requirement. We very much desire to add flexibility in our database access so that, for example you could use JDBC and ODBC in any of the supported database-capable nodes. This is a high priority candidate for a follow-on release.

  • Guest
    Reply
    |     Aug 30, 2013

    Thanks for raising this requirement. We very much desire to add flexibility in our database access so that, for example you could use JDBC and ODBC in any of the supported database-capable nodes. This is a high priority candidate for a follow-on release.

  • Guest
    Reply
    |     Aug 30, 2013

    Thanks for raising this requirement. We very much desire to add flexibility in our database access so that, for example you could use JDBC and ODBC in any of the supported database-capable nodes. This is a high priority candidate for a follow-on release.

  • Guest
    Reply
    |     Aug 30, 2013

    Thanks for raising this requirement. We very much desire to add flexibility in our database access so that, for example you could use JDBC and ODBC in any of the supported database-capable nodes. This is a high priority candidate for a follow-on release.

  • Guest
    Reply
    |     Aug 30, 2013

    Thanks for raising this requirement. We very much desire to add flexibility in our database access so that, for example you could use JDBC and ODBC in any of the supported database-capable nodes. This is a high priority candidate for a follow-on release.

  • Guest
    Reply
    |     Aug 30, 2013

    Thanks for raising this requirement. We very much desire to add flexibility in our database access so that, for example you could use JDBC and ODBC in any of the supported database-capable nodes. This is a high priority candidate for a follow-on release.

  • Guest
    Reply
    |     Aug 30, 2013

    Thanks for raising this requirement. We very much desire to add flexibility in our database access so that, for example you could use JDBC and ODBC in any of the supported database-capable nodes. This is a high priority candidate for a follow-on release.

  • Guest
    Reply
    |     Aug 30, 2013

    Thanks for raising this requirement. We very much desire to add flexibility in our database access so that, for example you could use JDBC and ODBC in any of the supported database-capable nodes. This is a high priority candidate for a follow-on release.

  • Guest
    Reply
    |     Aug 30, 2013

    Thanks for raising this requirement. We very much desire to add flexibility in our database access so that, for example you could use JDBC and ODBC in any of the supported database-capable nodes. This is a high priority candidate for a follow-on release.

  • Guest
    Reply
    |     Aug 30, 2013

    Thanks for raising this requirement. We very much desire to add flexibility in our database access so that, for example you could use JDBC and ODBC in any of the supported database-capable nodes. This is a high priority candidate for a follow-on release.

  • Guest
    Reply
    |     Aug 30, 2013

    Thanks for raising this requirement. We very much desire to add flexibility in our database access so that, for example you could use JDBC and ODBC in any of the supported database-capable nodes. This is a high priority candidate for a follow-on release.

  • Guest
    Reply
    |     Aug 30, 2013

    Thanks for raising this requirement. We very much desire to add flexibility in our database access so that, for example you could use JDBC and ODBC in any of the supported database-capable nodes. This is a high priority candidate for a follow-on release.

  • Guest
    Reply
    |     Aug 30, 2013

    Thanks for raising this requirement. We very much desire to add flexibility in our database access so that, for example you could use JDBC and ODBC in any of the supported database-capable nodes. This is a high priority candidate for a follow-on release.

  • Guest
    Reply
    |     Aug 30, 2013

    Thanks for raising this requirement. We very much desire to add flexibility in our database access so that, for example you could use JDBC and ODBC in any of the supported database-capable nodes. This is a high priority candidate for a follow-on release.

  • Guest
    Reply
    |     Aug 30, 2013

    Thanks for raising this requirement. We very much desire to add flexibility in our database access so that, for example you could use JDBC and ODBC in any of the supported database-capable nodes. This is a high priority candidate for a follow-on release.

  • Guest
    Reply
    |     Aug 30, 2013

    Thanks for raising this requirement. We very much desire to add flexibility in our database access so that, for example you could use JDBC and ODBC in any of the supported database-capable nodes. This is a high priority candidate for a follow-on release.

  • Load older comments

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.