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.
Perform checkouts before actual upgrade
Please consider to move or duplicate some of the checks before actual upgrade action. For example - cfgcheck can be initiated before upgrade action, this will eliminate situation where e.g. error in netmap.cfg/userfile.cfg causes rollback action ...
Add Management of Non-Stop C:D Nodes to Control Center
Right now Control Center lacks the ability to be able to manage C:D nodes running on nonstop systems. We would like to utilize Control Center as a centralized management system for C:D running on all platforms.
Prevent Netmap Node deletion if node is referenced by a Functional Authority
When an admin retires a netmap node that is no longer needed, sometimes we end up with an orphaned Functional Authority (FA) referencing a now non-existent netmap node. To prevent this from occurring, a new functionality could be created where Con...
More granularity on scheduling of Control Center configuration updates
The ability to run configuration updates in Control Center needs to have more options than run daily at a specific time or never.Large environments cannot handle daily runs and should be able to be scheduled via a calendar option. It would also be...
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 importe...
Add equivalent of cdai_verifyUpgrade parameter
For silent install, users get a chance to set upgrade options (parameters). One of those is cdai_verifyUpgrade which enables/disables step that performs loopback transfer after upgrade to verify if upgrade was successful. If loopback transfer is...
Manage/Configure iSeries from ICC
Configuration of Connect Direct and secure+ should be a standard across all supported platforms.
Allowing centralised configuration off all connected nodes from within ICC, as to tool was intended for...
Refresh all configurations of managed servers on Control Center
Currently, you can have Control Center check for configuration changes daily at a specific time. However, if an authorized user is making multiple configuration changes to multiple servers, they may want to be able to refresh all of the configura...
An enhancement request with Product Management to add support for AWS RDS SQL*Server and/or AWS RDS Postgres with Kerberos authentication.
We are migrating existing SQL*Server database (w/ Kerberos authentication) to AWS RDS platform. Current C::D Control Center does NOT support AWS RDS (any databases, such as Postgres). We won;t be able to configure Control Center as IT IS NOT MEET ...
BYO (Bring Your Own) Certificate with CRL checking
For "New Install" tasks - instead of using self-signed certificates, Control Center Director should allow to use user's certificate for the communication between Connect Direct server and Control Center Director.
Do not place IBM confidential, company confidential, or personal information into any field.