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.
Idea / RFE Review. This capability has now been provided in ACE 11.0.0.11 ... Status is updated to Delivered.
Thank you for raising this RFE. Overall IBM agrees that this sounds like a reasonable request for the way in which we continue to evolve the App Connect Enterprise product. The level of detail provided is helpful as it gives us an idea of the use cases being considered. Increasingly, with the move to container based architectures as part of modernization to an agile integration architecture, we observe ACE users deploying fewer applications and flows per integration server. With this in mind, we expect over time, the need to distinguish unique settings for multiple MQ "apps" in the same runtime process to be a reducing need. That said, we understand the need for this kind of setting for users who wish to continue to deploy multiple flows with unique MQ connection desires in the same integration server. It is likely that this RFE will end up be delivered in a series of smaller stages - starting with formalized support for server-wide use of MQ Uniform clusters, potentially followed by separate settings for the use of "user" uses of MQ (such as MQInput/MQOutput/MQGet etc) versus the use of "system" uses of MQ (such as the aggregation nodes for example). We might then look further into usage of MQ APPLNAME. Meanwhile, also note that in recent fix packs we have also continued to make progress on the flexibility of using MQ Client bindings for some ACE uses of MQ which have previously been subject to server binding connection - ie the remote default queue manager capability which was introduced in 11.0.0.7.
So, in summary this is an area of the product likely to see enhancement in future, and we thank you for raising the RFE. Status is updated to Uncommitted Candidate.