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 (https://ideas.ibm.com).


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 (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.


Add a new idea Subscribe
Status Not under consideration
Workspace WebSphere Liberty
Created by Guest
Created on Jun 12, 2025

RELATED IDEAS

InstantOn checkpoint.sh supported features validations to make developers life easy when adding to server.xml

InstantOn feature on Openliberty and WebSphere liberty is currently supported from version 23 and above, currently the supported jakarta features, microprofile features are listed per version and there are features which are not supported by instanton like IBM J2EE 8, EJB etc.,

Checkpoint.sh script has a way to validate the features added in server.xml file and throws an error when there are unsupported features present in it.
It is somehow validating the features with a list or some array.

If IBM can provide this feature to developers with some portal or some Advisor tool, it would make application teams easy to configure the features and make a decision if they can subscribe to InstantON or not.

Idea priority Low
  • Admin
    Jahnvi Bedia
    Oct 14, 2025

    Thanks for submitting your idea. We are not going to add this Idea to our roadmap right now, however we’ll keep it on record and revisit it if things change in the future.

    If you want to discuss this decision further, please contact Macdara Butler at macdara@ibm.com

    Looking forward to receiving more ideas from you on the IBM Ideas Portal.

    Reply
  • Admin
    Jahnvi Bedia
    Oct 7, 2025

    Hi,

    We’re currently holding off on implementation until we receive feedback, as it’s important to ensure the solution aligns with your specific needs. Could you please let us know if you’ve had a chance to review it? If there are any concerns or clarifications needed, please reach out to us to discuss this further. Thanks!

    Looking forward to your response.

    Reply
  • Guest
    Aug 18, 2025

    One way this could be solved is by adding a checkpoint option to the server script that allows a "dry-run" to be performed against a server configuration. For example, if you had a server named myServer and you wanted to confirm that server's configured set of features can be used for a Liberty InstantOn checkpoint then you could verify that with the following command:

    bin/server checkpoint myServer --dry-run=afterAppStart

    The --dry-run option for the checkpoint action may take beforeAppStart or afterAppStart.

    The checkpoint dry-run would start the liberty server as if a checkpoint is going to be done, similar to the checkpoint.sh script that is used during container image build. But the dry-run could be performed out side of a container image build against a local Liberty server configuration and the actual Linux process checkpoint would not happen during the dry-run. Any errors detected during the checkpoint dry-run prepare would be reported as errors in the logs and the console output. Upon failure the return code from the server script would indicate an error code when the dry-run failed to prepare for the checkpoint.

    Such a solution would require a server configuration to run against. At a minimum the server configuration would need to have enabled the <featureManager/> configuration with the list of <feature/> elements for the features that need to be validated for supporting Liberty InstantOn. Optionally the server configuration could contain application related configuration. The dry-run may also be used to validate some of the configuration for an application during a checkpoint operation.

    Before proceeding with this type of solution we would like confirmation that such a feature would solve the needs here to validate features for Liberty InstantOn support.

    Reply

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.