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 updateson 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
Currently with Control Center a keystore and a truststore have to be setup in order to allow secure connections. Once both have been setup, the configCC.bat or configCC.sh has to be run in order to tell the Control Center application the path location of both of the stores. However, in an environment that has multiple Event Processors (EPs), if a server where a particular EP crashes/becomes unavailable, the other EP doesn't have that information. Copies of the stores have to be available on the other EP and then configCC.bat/sh has to be ran to update the location of the stores. In addition, the other EP would need to be stopped in order to run the configCC.bat/sh. Once Control Center has been restarted on the EP that is available, and all of the monitored servers are assigned, hopefully it has secure connections to the servers that require. There needs to be a better way to manage/handle a situation like this if it was to occur. Please let me know if I did not explain properly.
What is your industry?
How will this idea be used?
Improve high availability/disaster recovery scenarios.
Do not place IBM confidential, company confidential, or personal information into any field.