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 review. Thank you very much for taking the time to raise this suggestion, but unfortunately on this occasion we will not be taking the idea forward. ACE has a very large number of possible configuration properties which particular users may want to specify for their own purposes and in general our architectural direction these days is to embrace declarative styling (defining properties up front in the server.conf.yaml file before starting a server) so that ACE can be a first-class citizen in cloud-native/Kubernetes environments. Controlling ACE behaviour in this way avoids the need for such a large number of dynamic options (ie those options not requiring server restart to take effect) and also avoids the need for a user to "log on" to an environment and make a change - using operator code and pre-declared yaml files with property settings is a much more efficient way of driving consistency through a set of installations. There are some cases where dynamic / command-based control is still required but this is a diminishing set of usecases, and choosing whether a JCN is allowed to retrieve a particular type of credential is more fringe than mainstream. Sorry we won't be taking this one any further. Best Regards, Ben