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 Jan 9, 2018

Enable wildcard MSL with multiple Launchers as with single Launcher

When setting up a single Launcher source directory there is no need to specify which MSL files to run. The single Launcher event will go to the assigned directory and find/run all MSL files found.

This is effectively a wild card usage of *.msl.

We have taken great advantage of this behavior in order to change which MSL files are launched, especially during testing. We can target a specific workflow by removing all other MSL files, or test variations on an existing workflow, without having to change the Launcher setup in any way.

But when running multiple Launchers as built using launcheradmin, the source targets are no longer directories but specific MSL files. While a directory is still selected, each MSL file must also be added to the set that will be launched.

This effectively eliminates the wild card *.msl feature and demands a list of specific MSL files when running a multiple Launcher session.

With multiple Launchers there is no capability to change the launched MSL files by simple adding or removing them from the directory.

It would greatly simplify the construction of environments using multiple Launchers if the user selected a directory for each system to be launched and gave the collection a processing name. Nothing more is required. As with the single directory selection, any MSL files found in the system source dirs are loaded at startup.
DeveloperWorks ID DW_ID71924
Link to original RFE
  • Guest
    Oct 8, 2019

    Future direction fo Launcher will negate this requirement