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 May 22, 2019

"Soft Stop" functionality for SSP engines for upgrading without service interruptions

Currently even though we have multiple SSP engines it isn't possible to perform a true "high availability" upgrade of the engines because anybody who is connected to an individual SSP engine will be disconnected when the engine is taken down for patching, even though the other engine is still online and available.

We need to be able to shut down engines in a manner that allows "in-flight" connections to finish while preventing new connections from starting,

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

Upgrade SSP with 2+ SSP engines:

1. Shut down first SSP engine.  Engine will immediately stop listening for new connections which will cause Load balancers to redirect new inbound connecitons to other nodes.  Existing sessions are allowed to complete before engine completes shut down.

2.Upgrade first engine to new version

3. Restart first engine

4. Repeat steps 1-3 for each remaining engine.


This allows upgrades to be completed with no interruptions to our end-users.  Current design results in many users being disconnected mid-transfer at the moment the SSP engines are stopped.

  • Guest
    Nov 16, 2022

    Hi Vijay,

    I just want to bring another use case in to this idea. Any SFTP adapter configuration changes requires a SFTP server adapter restart, when user choose "stop" adapter, adapter should stop accepting new sessions and allow the existing sessions to finish with in a timelimit.



  • Guest
    Nov 11, 2022

    Hi Vijay,

    This functionality is a must have in certified container world; I want to balance it by adding timelimit so it gives that time to finish existing sessions as much as possible; OCP cluster upgrades may stop the worker nodes by evicting the pods running in a worker node, inclusion of this functionality will be less disruptive;