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)