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 Planned for future release
Created by Guest
Created on Nov 9, 2022

Enhance patch automation to support tWAS instances installed by IM in Admin mode

Many tWAS instances were installed by IM in Admin mode. During WSA patch installation, the playbook terminated with error message: >>> ValueError: Installation directory is not owned by wasadmin but IM accessRights is admin The tWAS was installed by IM with 'admin' mode, however the owner of $WAS_HOME does not have root privileges. With the current design, to get around the problem, either the tWAS instances have to be re-installed by IM with non-Admin mode or to add root privileges to all the owners of different tWAS. instances. A solution is required to address the restriction without re-installing tWAS and have the playbook 'become_user' of the $WAS_HOME owner to complete the patch installation.
Idea priority High