Overriding properties

To change properties, use the customer_overrides.properties file, sandbox.cfg file, and log4j.custom.xml file.

Even though it is recommended that you do not change property files directly, situations do occur that require property changes. For these situations, use the customer_overrides.properties file, sandbox.cfg file, and log4j.custom.xml file, which are described below.

• customer_overrides.properties – If you need to change the value of a property that is not parameterized in the .in file(s), you can override that property by adding an entry for it to the customer_overrides.properties file. Making changes to this override file instead of individual property files ensures that none of your changes are lost in an upgrade or fix pack installation, and lets you see most of the overrides in your configuration at a glance, rather than having to check each property file individually. This file is not delivered with the product; you must create it the first time you have a need for it.
• sandbox.cfg – Contains name-value parameters that are merged with each *.in file to create the final properties files. For values that are parameterized in the *.in files, you can supply that parameter in the sandbox.cfg file.
• log4j.custom.xml – For changes to logging properties, you create a file called log4j.custom.xml. You make changes to basic logging properties in this file. There are additional logging properties in the yfs.properties.in file. To make changes to these, you create entries in the customer_overrides.properties file.