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. This capability (extra tag information referred in last comment) has now been provided in ACE 11.0.0.11 ... Status is updated to Delivered.
RFE Review. Thank you for taking the time to raise this RFE and apologies it has been in submitted status for so long. In IBM Integration Bus v10, the data of the initial disk location of the BAR file was stored as metadata alongside the deployed artifacts in the integration node's internal configuration store (back further in history with much older versions of the product, this originated in the configuration manager database). However, in ACEv11 the product architecture has evolved and we have deliberately moved away from storing meta-data along side deployed artifacts for a number of reasons. For example it is no longer necessary for deployed artifacts to have been deployed via a BAR file. Despite there being good reasons for this change, we acknowledge that this data was of value for IIBv10 users so we would like to help with this RFE ... The likely implementation here will be to furnish our new Administration log entries with tag information about the BAR file. The admin log was new in ACEv11.0.0.10 and the tag information about the BAR file has not yet been provided but is likely to come in a future ACEv11 fix pack. Status of the RFE is updated to Uncommitted candidate.