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 Usability
Created by Guest
Created on Jul 25, 2018

Segregate PR and PP JMS properties instead of overloading them into one and forcing 2 copies of MountFiles

If embedded JMS is used, the Partner Repository and Partner Provisioner use different values in the same property "enable_jms_features" in Setup.cfg file. This makes it imperative to create two distinct copies of the entire MountFiles directory to make this one parameter distinct for Partner Provisioner. Instead, it would be a good design to have the PR and PP look up distinct parameters in Setup.cfg which would make one copy of MountFiles work. This will then be a viable option for embedded JMS as well as WSMQ.

What is your industry? Non-Industry Specific
How will this idea be used?

This will make the deployment foot print smaller and more manageable. The customer does not have to install two copies of the same MountFiles with one distinct parameter that will be different. It will also avoid explaining to the customer why this should be done for keeping one property value distinct for sake of one container.

  • Guest
    Nov 5, 2020

    his only affects embedded JMS which we are not recommending. It would be a nice to have option, but it is not something that we expect to be able to address within the medium term (next two years).