Skip to Main Content
Cloud Platform

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:

Post your ideas

Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive a notification on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

If you encounter any issues accessing the Ideas portals, please send email describing the issue to for resolution.

For more information about IBM's Ideas program visit

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?