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
Workspace Self Service Tool
Created by Guest
Created on May 11, 2023

Build and Deploy only the war needed + Build script per Env


Todays it is not possible to build only selected war of the application that requires rebuild. Every time whole ear is built with all the wars which takes quite a time.

It would be great if user can select the required war to be rebuild and redeployed from SST


I got to know that todays build script that runs on back of SST is multi tenant and it is one script that runs for all environments

Maintaing the build script per customer level may be lot of maintenance .

But maintaing build script per environment would certainly give us lot of flexbility to include the additional war like ISCCSDEV in the required environments.

Also it do not kill the PROD . In my opinion, maintaining build script at env level should not be overhead

What is your industry? Retail
How will this idea be used?

Saves lot of time