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 Not under consideration
Categories Launcher
Created by Guest
Created on Jul 24, 2019

WTX service discloses detail software versions & file system

WTX service discloses detail software versions & file system - Cases - IBM Support

The Launcher process uses three TCP/IP ports. The first port is for status, the second port is for monitoring and the third port is port control.


The Launcher does not have any check when traffic comes to the launcher monitoring port.


The Launcher monitoring port is used by the Launcher Monitor tool (Windows).


After any client connects to the monitor port, the Launcher process sends back the msl / system configuration information.


The assumption is that the launcher is behind a firewall and therefore uses http.


The firewall would prevent any external access to the information returned by the Launcher monitor port.


The current behavior has been part of the Launcher product since the initial code (over 20 years).


We have consulted with the development team and confirmed that a significant product enhancement would be required to several components of the Launcher product to change the current behavior.


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

To update security

  • Guest
    Aug 15, 2019

    Hello Luke - do we have any timeline for this yet?

  • Guest
    Aug 1, 2019

    Thanks Luke.

    Can you give us a timeline?

  • Guest
    Jul 30, 2019

    We are in the process of revamping Launcher including its the monitoring capabilities. This issue should be resolved with that implementation