IBM Sterling Ideas
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:
Post your ideas
IBM is transforming its request for enhancement (RFE) process. The purpose of the transformation is to provide a more consistent experience for you to submit requests and to enable IBM product owners to respond to your requests more quickly. For more information click here.
Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you, 1. Post an idea 2. Upvote ideas that matter most to you 3. Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notifications on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
Customers normally add/configure CD nodes whenever they are ready to manage the CD node from CCD. Hence configuring CD nodes in CCD is not one time activity and rather an ongoing activity.
CCD requires the public keys of all CD nodes to be imported in to its TrustStore. But, importing public keys into the configured TrustStore is not sufficient, and we need to run configCC.sh to update the internal "bootstrap.truststore" that is used by the ICC during the handshake.
ConfigCC.sh requires ICC to be stopped, which will lead to many restarts of ICC whenever there is a new public key to be imported in to ICC TrustStore.
Rather, it would be helpful for customers to have simple utility to refresh the "bootstrap.truststore" without having to run configCC.sh so that customers can avoid restart of ICC just for importing public keys.
|What is your industry?||Banking|
How will this idea be used?
Customer is having number of Windows and Unix C:D nodes and currently setting up CCD for the auto management of CD nodes. Customer needs to identify the CD nodes that are ready to be configured in CCD in terms of the compatible minimum version and Secure+ enabled. As all nodes cannot be upgraded to a compatible version and configured Secure+ at same time, customer does this task one at a time over few weeks.
Currently customer is importing the public keys into the TrustStore and then stopping ICC to run configCC.sh to get the "bootstrap.truststore" updated before testing the connectivity with the CD nodes.
Having a direct command to update ""bootstrap.truststore" helps customer onboarding CD nodes without bringing the ICC down for each CD node.
Though the main concern is about the mandatory restart of ICC, the other overhead is running configCC.sh which normally repeats a lot of questions where we just need to update the public keys.
The feature saves a lot of time for customers.
Do not place IBM confidential, company confidential, or personal information into any field.