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 Future consideration
Created by Guest
Created on Sep 20, 2014

Change CreateWSRuntime to accept an SDK ID instead of a Java version

The CreateWSRuntime task supports an attribute, "javaVersion", which can contain either the value "6.0" or "7.0" for WAS 8.5.

However, recently, IBM released JDK 1.7.1. There is no way, using CreateWSRuntime, to add a WAs 8.5 runtime that uses JDK 1.7.1.

This exposed a design flaw in CreateWSRuntime. In my mind, the approach of specifying a "javaVersion" doesn't "scale" well for forward compatibility. It would be much better if, instead of specifying a java version, the developer could specify the WAS SDK ID ("1.7", "1.6", "1.7_64" etc), when the SDK ID is one of the values currently listed as part as the "managesdk -listAvailable" command.

Alternatively, in order to not break existing clients, you could add an attribute called "sdkId" that the user can use in lieu of "javaVersion".

That would ensure that the CreateWSRuntime task supports any SDK in the future. No need to edit CreateWSRuntime every time IBM adds a new JDK.

Idea priority High
RFE ID 59449
RFE Product Rational Application Developer
  • Guest
    Sep 24, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - WebSphere
    Product family - Application Platform
    Product - Application Developer

    For recording keeping, the previous attributes were:
    Brand - Rational
    Product family - Design & development
    Product - Application Developer

  • Guest
    Jan 15, 2015

    For what it's worth, Java 7.1 support does existing with the CreateWSRuntime Ant task included in Rational Application Developer / Rational Build Utility 9.1.

  • Guest
    Jan 13, 2015

    Although the theme of this request is consistent with our business strategy, it is not committed to the release that is currently under development.

  • Guest
    Oct 20, 2014

    A preliminary evaluation of this request indicates that it is consistent with our business strategy. Further evaluation of this RFE is underway.