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 (https://ideas.ibm.com).


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 (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.


Status Needs more information
Workspace WebSphere Liberty
Created by Guest
Created on May 5, 2025

Install diagnostic features by default when using features.sh with the Liberty kernel base image

If the Liberty kernel base image is used to build a container (e.g. icr.io/appcafe/websphere-liberty:kernel-java17-openj9-ubi) and features.sh is used to install the necessary features from the server XML file(s), then, usually, potentially required diagnostic features won't be installed such as localConnector-1.0, requestTiming-1.0, monitor-1.0, osgiConsole-1.0, etc. This is particularly painful with containers and production issues because rebuilding and redeploying a container image is usually a complex and lengthy process.

This enhancement request is for features.sh to automatically install certain features by default even if they are not specified in the server XML file(s). The ones that come to mind are localConnector-1.0, requestTiming-1.0, monitor-1.0, and osgiConsole-1.0, though others can be considered (e.g. restConnector, mpHealth, mpMetrics, etc.). This behavior can be disabled with a variable before features.sh; for example:

# Default setting for installing diagnostic features. Set it to false to only install the features specified in the server XML file(s)
ARG INSTALL_DIAGNOSTICS=true

RUN features.sh

Idea priority Medium