IBM Sterling Ideas

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:

Post your ideas

IBM is transforming its request for enhancement (RFE) process. The purpose of the transformation is to provide a more consistent experience for you to submit requests and to enable IBM product owners to respond to your requests more quickly. For more information click here.

Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,
1. Post an idea
2. Upvote ideas that matter most to you
3. Get feedback from the IBM team to refine your idea

Help IBM prioritize your ideas and requests

The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.

Receive notifications on the decision

Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.

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.
  • Guest
  • Jan 9 2018
  • Not under consideration
DeveloperWorks ID DW_ID71924
Link to original RFE
  • Guest commented
    8 Oct, 2019 05:25pm

    Future direction fo Launcher will negate this requirement

By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.