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.
Thank you for taking the time to raise this enhancement request. We'd like to ensure that the current capabilities of mqsicredentials are understood ... When dealing with node-owned servers, although the vault key used in the administrative commands is "node-wide" in terms of where credentials are stored, we have a separate vault on disk per integration server in addition to one for the integration node itself. Each of these vaults share the same vault-key. This reinforces the architectural model whereby integration nodes manage a set of servers ... but also allows flexibility when defining credentials using the mqsicredentials command to target a specific integration server for the credentials, or all servers owned by the node. With this understood, we are keen to learn more about the specific use case - we acknowledge that the credentials vault could be improved in terms of some of its dynamic behaviours when adapting behaviour to take account of updated credentials which currently requires a restart. Currently, new credentials are used immediately but changed credentials are not used until restart. Is this the core behaviour which you'd like to see changed through this RFE? Perhaps you could expand on the use case by explaining the precise commands you've tried to execute and how you were hoping behaviour might be different.