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.

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.

  • Guest
  • Jul 25 2018
  • Not under consideration
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.

  • Admin
    Greg Russell commented
    5 Nov, 2020 08:17pm

    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).

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.