Skip to Main Content
IBM Sterling

This portal is to open public enhancement requests for IBM Sterling products and services. 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 Nov 3, 2022

Cleanup prior version .jar files

The install/upgrade/patch/hotfix process should cleanup the prior version .jar files.

We have been running since 2016 and every .jar file from upgrades are in the <install>/packages folders as well as other folders having years worth of backups.

We create a tar file prior to doing any upgrades and it is over 14Gb

What is your industry? Travel & Transportation
How will this idea be used?

Prevent upgrade issues by having old .jar files left behind and save time to backup the filesystem

  • Guest
    Aug 9, 2023

    Additionally, any old jar file backups with known vulnerabilities are being flagged by software security scanning tools, and these ancient jar files make the product look like it has tons more unmitigated and un-remediated vulnerabilities than it does. This is not a good look for IBM and it makes it difficult for SI/B2BI platform admins who constantly have to "explain away" these vulnerable jar files which are no longer being used, but yet still exist on the filesystem under an installed directory structure.