Skip to Main Content
IBM Sterling


This portal is to open public enhancement requests for IBM Sterling products and services. 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
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. 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.

Status Not under consideration
Created by Guest
Created on May 12, 2021

Ability to update the "bootstrap.truststore" with the new public keys of CD nodes without running configCC.sh that mandates to stop ICC

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.

  • Admin
    Chris Sanders
    Sep 9, 2021

    Thank you for opening this enhancement request with IBM. I have reviewed it thoroughly with my team. Unfortunately we don't believe that this request will be applicable to the majority of our customers. Because of that we'll need to prioritize where we allocate our resources and must decline this request. I do appreciate you opening this request and would encourage you to use the tool again moving forward if there are other ideas we should consider.


    Sincerely,

    Chris Sanders

    CCD Product Manager