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.
I have interest in seeing MESNS-I-155 integrated into MQ. The ability to refresh SSL without affecting many channels would greatly help environments that need to be highly available. This can be the case where external partners need an updated CA chain added to the MQ Keystore to continue encrypting their channels.
It would be interesting if an expiry mechanism could be integrated into the processes that contain static copies of the MQ Keystore. This could provide a solution where pooled connection processes like amqrmppa are marked "old" during a refresh, and new Receiver channel connections are directed to a new amqrmppa process with a new static copy of the MQ Keystore.
This is still something we'd like to do, but it's likely to be a different solution than the 9.2.5 client-side implementation. The need for I-96 might diminish if this is done, but it still has some independent validity so we didn't want to merge the two records completely.
Hi Mark,
The 9.2.5 CD release saw a feature for MQ clients allowing for TLS keystore updates to be picked up by any new TLS connections made by the client. Could this functionality be ported over to the server side as well? That would negate the need for this idea of the -r, because it eliminates the connections dropping out entirely, but at the expense of additional system resources being used (therefore meaning customers will need to weigh up the performance considerations vs the security concerns associated with longer lived certificates).
Please ensure any solution does not require changes to the MQ client applications code (such as a new option on MQCONNX) as this is hard or impossible to achieve, especially with vendor supplied packages.
Unmerged from 217 as the solutions to each have now diverged. But we still hope to deliver a solution for this independently of 217 in a future version of MQ.
This has been merged with MESNS-I-217 (MQCONNX not able to use alternative SCO) as our expectation is that our ideas on how 217 could be implemented conveniently go a long way to meeting the need for this one as it would actually remove in most cases, the need to run the REFRESH command.