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 Oct 14, 2016

Liberty: Allow variables expansion in jvm.options

Please allow variables expansion in jvm.options of WAS liberty profile the same way it is possible in server.xml

Idea priority Medium
RFE ID 95894
RFE Product WebSphere Application Server
  • Guest
    Feb 1, 2017

    Simple use case (from many more complex uses cases):
    We have in
    We need to have a that is
    and {http.port} is also used in server.xml
    Q: how to we do that without repeating the values of the "http.port" and "https.port"?
    (again this is a simplified use case)

  • Guest
    Oct 20, 2016

    All the properties in are already available as System properties. For example if you have a property in 'bootstrap.prop=value' that is valid in server.xml using ${bootstrap.prop} and in an application using System.getProperty("bootstrap.prop"); There is no need to put the property in jvm.options as well.