Supplementary Property Files
Supplementary property files can be used in addition to be-engine.tra (or the alternate file you specified using --propFile).
In TIBCO BusinessEvents 4.0 and later versions, property files are less likely to be needed, because only system level configuration is done in the TRA files. Configuration formerly done in TRA files is now done using the Cluster Deployment Descriptor file. Supplementary property files typically have a .cfg or .tra extension. Properties are defined as a list of name-value pairs. If a property name includes spaces, escape them using a back slash (\).
Order of Precedence
Values in supplementary property files override the values in the startup property file. Values provided at the command line override values in the supplementary property files. If you specify multiple property files that include different values for the same parameters, TIBCO BusinessEvents uses the value in the left-most file in the command line.
For example, consider this command line:
be-engine -p first.cfg -p second.cfg -p third.cfg
If second.cfg and third.cfg set different values for (as an example) tibco.clientVar.MyVar, and first.cfg does not include this parameter, TIBCO BusinessEvents uses the value in second.cfg. However, if first.cfg also includes a value for tibco.clientVar.MyVar, TIBCO BusinessEvents uses the value in first.cfg.