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.
A shared repository is a possibility but it comes with additional costs and risks. I'm pretty sure that most DataPower users would prefer a pure on-box solution. There's a kind of common workaround by using an on-box service to provide the files (e.g. an HTTP Service), but solution comes with the additional TCP/HTTP overhead. A file system based solution would be faster and easier.
By the way, even the quick-and-dirty alternative with the subfolders in the store directory is better than an external shared repository.
Thank you for the suggestion. Fundamentally this is not a bad idea. You can also fetch the files that are used across many domains from a shared repository. We have had that functionality built in just for this reason for many years.
We're going to decline this idea for now but will continue to monitor for more comments and alternatives. It might be reassessed or reopened for additional feedback in the future.