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. Thank you for taking the time to raise this enhancement request, and apologies for the length of time it has been held in the status of Uncommitted Candidate / Future Consideration status. This is an area of the product we would like to enhance, and although there have only been 3 votes against this item, a duplicate RFE has currently received 26 votes in favour:
https://integration-development.ideas.ibm.com/ideas/APPC-I-163
Given this more recently raised request with the far greater support, we are choosing to close down this item and will continue to track this topic using 163 moving 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 requirement. We'd like both JDBC and ODBC to be equivalent in terms of capability, and extending the cvp command to include JDBC connections would be a good step forward.
Thanks for raising this requirement. We'd like both JDBC and ODBC to be equivalent in terms of capability, and extending the cvp command to include JDBC connections would be a good step forward.
Thanks for raising this requirement. We'd like both JDBC and ODBC to be equivalent in terms of capability, and extending the cvp command to include JDBC connections would be a good step forward.
Thanks for raising this requirement. We'd like both JDBC and ODBC to be equivalent in terms of capability, and extending the cvp command to include JDBC connections would be a good step forward.
Thanks for raising this requirement. We'd like both JDBC and ODBC to be equivalent in terms of capability, and extending the cvp command to include JDBC connections would be a good step forward.
Thanks for raising this requirement. We'd like both JDBC and ODBC to be equivalent in terms of capability, and extending the cvp command to include JDBC connections would be a good step forward.
Thanks for raising this requirement. We'd like both JDBC and ODBC to be equivalent in terms of capability, and extending the cvp command to include JDBC connections would be a good step forward.
Thanks for raising this requirement. We'd like both JDBC and ODBC to be equivalent in terms of capability, and extending the cvp command to include JDBC connections would be a good step forward.
Thanks for raising this requirement. We'd like both JDBC and ODBC to be equivalent in terms of capability, and extending the cvp command to include JDBC connections would be a good step forward.
Thanks for raising this requirement. We'd like both JDBC and ODBC to be equivalent in terms of capability, and extending the cvp command to include JDBC connections would be a good step forward.
Thanks for raising this requirement. We'd like both JDBC and ODBC to be equivalent in terms of capability, and extending the cvp command to include JDBC connections would be a good step forward.
Thanks for raising this requirement. We'd like both JDBC and ODBC to be equivalent in terms of capability, and extending the cvp command to include JDBC connections would be a good step forward.
Thanks for raising this requirement. We'd like both JDBC and ODBC to be equivalent in terms of capability, and extending the cvp command to include JDBC connections would be a good step forward.
Thanks for raising this requirement. We'd like both JDBC and ODBC to be equivalent in terms of capability, and extending the cvp command to include JDBC connections would be a good step forward.
Thanks for raising this requirement. We'd like both JDBC and ODBC to be equivalent in terms of capability, and extending the cvp command to include JDBC connections would be a good step forward.
Thanks for raising this requirement. We'd like both JDBC and ODBC to be equivalent in terms of capability, and extending the cvp command to include JDBC connections would be a good step forward.
Thanks for raising this requirement. We'd like both JDBC and ODBC to be equivalent in terms of capability, and extending the cvp command to include JDBC connections would be a good step forward.
Thanks for raising this requirement. We'd like both JDBC and ODBC to be equivalent in terms of capability, and extending the cvp command to include JDBC connections would be a good step forward.