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
Workspace WebSphere Liberty
Created by Guest
Created on Dec 11, 2018

Allow environment variables in the plugin-cfg.xml file

Our customer is evaluating WebSphere Liberty using the latest version v9.0.0.0 IHS + PLUGIN tar instalation package to develop an architecture for running WebSphere Liberty in a containerized environment. When we run the "pluginUtility generate ..." command we faced the problem that the hostname(s) etc. in the generated plugin-cfg.xml file are set to the host-name of the build host and can not be made variable. This is however not useable in a containerized environment when multiple containers are started as each of the containers has a different host names. Therefore extra code and plugin-cfg.xml manipulation is required before starting the containers.

Therefore it would be very helpful for us if the plugin code would be capable of processing (environment?) variables in the plugin-cfg.xml so that attributes in the plugin-cfg.xml can be easily adjusted to the currently running container.

Idea priority High
RFE ID 128155
RFE Product WebSphere Application Server
  • Admin
    Graham Charters
    Nov 5, 2021

    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 <>.

  • Guest
    Dec 12, 2018

    a few questions to get an idea of the scope/effort required and possible alternate ways to satisfy it.

    Does the solution use DNS for service discovery? Would it be sufficient for each server.xml to specify an explicit host:port rather than the servers own? I think this would survive merge-like scenarios better and not require runtime changes.

    Secondly, do you need environment variable interpolation for fields other than the host and port? And would you expect pluginUtility-like XML generation to populate these w/ the variables or is post-processing on the generation side acceptable?


  • Guest
    Dec 12, 2018

    Hi, If you are using Dynamic Routing with a controller and replica sets then an update to the plugin is not needed as App Servers will communicate with the controller/replica sets, and when the plugin communicates with the controller/replica sets it will update the routing rules automatically. This would be using stackGroups and the ND version is needed for the controller and replica sets, but not for the regular App Servers. Please see :

    The Plugin file will also be created when the server starts. It may be possible to transfer the plugin file after it is created to the Plugin itself.

    You can use the scripts needed for the scaling above and wrapper that with what you and and pass the variables you want to the script which will then launch the App Server.

    You could also update the file with variables that will be placed in the server.xml. This would require a wrapper script that would update that file before the App Server is launched.

    Regards, Brian