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.
Need Control Center to support OID/LDAP for connecting to Oracle Database. This feature is available in B2Bi/ SFG, but not in Control Center and impacts USAA when they fail over the ICC database.
|What is your industry?||Insurance|
How will this idea be used?
Right now when the USAA application's database fails over between primary/standby for maintenance, etc. most of USAA products follow the database just fine because they connect via OID/LDAP. But for Control Center, USAA has to manually shut down the application (all nodes, one by one) and re-run the setup scripts to provide new connection details for the new database location. These setup scripts are fairly complicated, with configuration for a lot more than just the database, which often times leads to inadvertent misconfigurations that cause system issues. The application should just follow the database when it fails over, without downtime, manual intervention, etc.
Do not place IBM confidential, company confidential, or personal information into any field.