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
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,
Post an idea
Upvote ideas that matter most to you
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 a notification 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.
If you encounter any issues accessing the Ideas portals, please send email describing the issue to email@example.com for resolution.
For more information about IBM's Ideas program visit ibm.com/ideas.
Confirmation dialog box before stopping an cluster in console
In the WAS console, when we try to stop a cluster(s), we select the cluster, and click on Stop, and BOOM, the cluster stop gets initiated and there is no way for us to stop that process in case we have stopped it by mistake. In the case of Application server(s), we do get a dialog box that if we really want to stop the selected application server(s), which at least gives us a chance to check and revise. My customer feels that even if an application server is stopped by mistake, there would be others in the cluster which can still serve, but if the cluster itself is stopped accidentally, the whole app is down at least until the servers come back up. While having the double confirmation for Application Server stop is good, it is very much needed to have the similar feature for cluster stop as well. It would definitely give a second chance to review and revise if needed. Also, if something else can be added along with this, that would be great. For example, if admin wants to stop Cluster XYZ, a message would show up, asking, **Do you really want to stop XYZ cluster in 'AppName-Environment'**. The AppName-Environment is something admins give in Custom Identity String. With this, Admin would be really cautious when it reads Production Environment. If nothing is present in Custom Identity String, the message would simply be ** Do You really want to stop cluster XYZ**. But having a double confirmation for STOP really really helps a great deal.
Do not place IBM confidential, company confidential, or personal information into any field.