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 Review. ACE was enhanced in 12.0.2.0 to record the BAR file deploy time and filename info. More details here: https://community.ibm.com/community/user/integration/blogs/ben-thompson1/2021/09/27/ace-12-0-2-0
RFE Review. Apologies this RFE has been in the status of Submitted for a while. On the face of it, this request seems very straight forward, and certainly its external benefit is recognised - this would definitely enhance the use of the product. Unfortunately there are some complications which we need to ensure are given proper consideration before we can make this request a reality. We are keen not to break some of the architectural foundations on which we based our v10 to v11 evolution... specifically:
i) We don't want the product runtime to have to reserialize artifacts stored on the file system on start-up. This was the way IIBv10 worked and for large deployments can become a performance inhibitor.
ii) The artifacts stored in the run directory should be the same as the source artifacts used in the toolkit where-ever possible. This allows for all kinds of great reuse and copying of source without the need for a complex build process.
iii) To make DIFFing simple (for future expansion of impact analysis tools etc) we really want to limit metadata differences.
In ACEv11 we also have an administration log as a relatively new feature which helps with unifying WHAT was deployed WHEN and by WHOM, so part of this overall use case has been solved in that fashion. All this said, we are keen to address this in future, but discussions are still ongoing regarding the best way of achieving the outcome. Status of the RFE is updated to Uncommitted Candidate.