Skip to Main Content
Cloud Platform

This is an IBM Automation portal for Cloud Platform products. 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 (

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 updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.

Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal ( - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal ( - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM. - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Created by Guest
Created on May 17, 2018

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.

Idea priority Medium
RFE ID 120204
RFE Product WebSphere Application Server
  • Admin
    Graham Charters
    Mar 15, 2022

    Thank you for the suggestion. The requirement does have merit, but looking at it with respect to our total backlog of requests we do not see sufficient interest in this enhancement to merit delivery any time in the foreseeable future. Given the unlikelihood that we would deliver this, we are declining the request rather than leaving it in an uncommitted state for an extended period of time. If you would like to discuss this decision further, please contact Graham Charters <>.