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.

Enabling customer override properties as -D argument

We would like to have option of enabling customer_override properties as -D argument for java application, it will allow apps to support different combinations for different environment.

In todays world everyone wants to deploy same artifact accross all environment from dev till prod, changing artifact for environment specific property raise risk of manual mistakes.

For example for by QA testing i need log4j with DEBUG enabled while for my prod i need log4j with INFO. Now since in sterling OMS i need to mention my log4j file name in cutomer_override like "yfs.log4j.configuration=/resources/log4jconfig.custom.xml" i cant have different version for prod and qa without updating ear again.


Another example is jms pooling ; if i have two apps with sterling code one is used for sterling Application console and other service layer with same code however i want jms pooling to be enabled for one of them. I need to set yfs.jms.session.disable.pooling in customer override, again i cant have it on for one and off for one. I have to maintain two artifact for just one property change.


It would have been easier if these parameters are supported as -D arguments for java opts.

We know we have some properties part of customer override do support -D arguments and wanted to have same features for others as well

Example :

yfs.logall (-Dyfs.logall)

yfs.log4j.configuration (-Dyfs.log4j.configuration) this works for sterling agents but not for jboss app

rmi.portrange(-Dsci.rmi.portrange)


  • Guest
  • Feb 9 2021
  • Future consideration
What is your industry? Retail
How will this idea be used?

We would like to have option of enabling customer_override properties as -D argument for java application, it will allow apps to support different combinations for different environment.

In todays world everyone wants to deploy same artifact accross all environment from dev till prod, changing artifact for environment specific property raise risk of manual mistakes.

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.