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).
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:
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 an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
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.
Idea / RFE Review. Apologies for the length of time this request has been held in the status of Uncommitted Candidate / Future Consideration. This request has not received widespread support. Whilst it would be possible to expand the DatabaseInput node into other technology spaces, if we were to functionally enhance this area, it is more likely that we would look into Change Data Capture technology rather than SQL polling as the mechanism through which we communicate with the database. The main motivation for this feature is really around usability and maintainability of the code used to access the database ... so it is also worth noting that other mid-flow workarounds are possible (GDM, JCN, .NETCompute etc) driven from a Timer input, which would provide these other coding alternatives. All things considered, unfortunately on this occasion we do not intend to carry this idea further forward.
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 (these?) requirements. We'd like to make the DatabaseInput node as accessible to a variety of technologies as possible. We started with ESQL because of its natural synergy with databases, but extending to maps, Java and .NET is highly desirable.
I realized after I submitted this RFE that map, .NET, and Java should be three separate RFEs.
I would say that map would be the top choice, to facilitate creating an Application table query that involved more than one table, with the tables having lots of columns.