Resolution:
Description:
============
You can use the bwengine.exe named –p option to supply a properties file at runtime when you start bwengine from the command line.

Example:

"C:/tibco/bw/5.7/bin/bwengine.exe" --run --propFile "C:/tibco/tra/domain/user13/application/CreditCheck/CreditCheck-SlowCCProcess.tra" -p "C:/tibco/spm/1.2/plugins/bwserviceagent.properties"

You also can add the property to the tra file to archive the same result.

You can also use yje “-p” option in the tibco.env.APP_ARGS argument in the tra file.

Example:

tibco.env.APP_ARGS=-p C:/tibco/designer/5.6/properties.cfg in the deployed tra file.

You should then see “Using property file C:\tibco\designer\5.6\properties.cfg” in the log file. Note that some properties of the form 'java.property.*' needs to be specified in the designer.tra file as they are loaded by the wrapper in which case Designer must be restarted for the properties to take effect. In contrast, any changes made to the engine properties specified with the "-p" flag should take effect simply by restarting the tester.


Environment:
==========
ALL

Supplying the properties.cfg file to bwengine.exe at runtime?