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 ideasibm@us.ibm.com for resolution.

For more information about IBM's Ideas program visit ibm.com/ideas.

Status Not under consideration
Created by Guest
Created on Aug 20, 2019

Java 11 support for WAS ND

I'm working for an Insurance Group, currently responsible of the implementation of Guidewire Insurance suite (https://www.guidewire.com/products/insurancesuite), which is a World Class application developed in Java.

We'd implemented the Guidewire suite for one of our Companies, using IBM WebSphere Network Deployment, and we took advantage of some of their features like Cells, Intelligent Management and Dynamic Clusters.

The version we're running (10.0.1) is compatible with Java 8, but the new one (10.0.2) will work only with Java 11.

This means that, if Java 11 keeps supported only in WAS Liberty and not on WebSphere Network Deployment, we need to stay stuck on the current version (not a valid option from the business perspective) or change the application server, starting from scratch, and rebuild everything we did so far.

WebSphere Network Deployment solves a large part of the implementation, balance and high availability strategy in our company, and we need it to include official support for Java 11, in order to update our insurance core.

Idea priority High
RFE ID 135451
RFE URL
RFE Product WebSphere Application Server
  • Guest
    Sep 20, 2021

    Just to add additional clarification does this means that TWAS is not expected to support ANY version of Java past JDK8?

  • Admin
    Graham Charters
    Sep 20, 2021

    Thank you for the suggestion. The requirement does have merit, but our focus for traditional WebSphere is to maintain stability and security for existing workloads, and hence our commitment to support Java 8 till at least 2030. Implementing Java 11 would force applications to migrate in order to move to the latest runtime version.  Given the Java 11 migration costs, our recommendation is to move to Liberty, which is a much more modern, efficient runtime, optimized for modern architecture and environments.

    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 <charters@uk.ibm.com>.

  • Guest
    Oct 22, 2019

    Hi, and thank you for submitting this request for enhancement! Due to the very large work sizing for adding this support, we currently have no plans on implementing this in the short or medium term future. However, this is a valid request, and so I will leave it open for other users to potentially view and vote on. I just want to be very clear up front that this request is unlikely to be implemented.