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.
Monitor Aspera Nodes
It would be great idea if we can have monitoring enabled for Aspera Nodes and secure proxy, the reason I would say is as Aspera provides one of the MFT solution which enables us to transfer huge data and since it has the ability to do so lot of or...
Propagate configuration via batch
This new idea is to request that Sterling Control Center Director allow configuration propagation, in this case from Connect:Direct (userfile, netmap, InitPams, Secure+), via Batch, and not just via the graphical interface.
Add Link to Web Start Page for Control Center Director API's.
The current Web Start Page has a link for Control Center API's but the choices available only apply to Control Center Monitor and not Control Center Director
Make package.folderWatchDelayInSecs Available in System Settings
My understanding is that the settings for package.folderWatchDelayInSecs are only available through the RESTful API. This setting along with all settings should be made available in the system settings as well.
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 a...
Control Center Director/Monitor - Updating Key and Trust store databases
Currently in order for CCM/CCD to be "aware" of change made to the key and/or trust store databases, the event processors (application) must be down. The configCC.bat/sh must be run in order to make CCM/CCD aware of the changes. There needs to 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...
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...
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 ...
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.
Do not place IBM confidential, company confidential, or personal information into any field.