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 Delivered
Workspace WebSphere Liberty
Created by Guest
Created on Apr 4, 2017

Allow the use of host sytem environment variables in server.env: Shell and variable expansion should be supported

System: WebSphere Liberty Profile
Actor: Automated deployment relying on config information provided by runtime platform (i.e. linux server or container)

As WebSphere Liberty is heavily used in cloud contexts, configuration options that need to be configured in the server.env file should allow the use of shell variables.

Currently this is not supported:

Description: As we do not want to create custom packaged servers that require different config in server.env (e.g. hostName, rack, logDirectory, etc.), it should be able to consume them from the servers environment.

Idea priority Medium
RFE ID 103332
RFE Product WebSphere Application Server
  • Guest
    Jan 18, 2022

    You should open a new RFE for your alternative solution. This RFE is implemented in

  • Guest
    Jan 7, 2022

    I have an alternative view on this: Remove server.env completely in cloud environments and inject all of the environment variables you need into the JVM at runtime. This has served us well except for desktop environments. There, you need to specify the environment variables somehow and the tooling has no way to do this as there are no launch configurations to start Liberty. Our only alternative is to create a server.env and then DO NOT package it into the usr package for distribution. Perhaps the "server package" command can be enhanced for this?