In addition to the basic configuration files within the installation's /config directory, there are additional properties in the following locations:
Both of these locations are dynamically created during a deploy, so any changes made directly to these configuration files are lost during a deploy. Therefore, it is not recommended to directly edit these configuration files. Whereas, using config overrides allows you to modify these properties and have them persist after a deploy.
Setting up overrides
There are two ways to override properties:
- Leverage the CONFIG_OVERRIDE functionality within the appserver.properties config file
- Create an override.properties file within your configuration directory
Instructions on using override.properties are found in our Using override.properties to modify product configuration article.
Instructions on using CONFIG_OVERRIDE are found in our Using CONFIG_OVERRIDE to modify product configuration article.
CONFIG_OVERRIDE overrides properties on a file-by-file basis, while override.properties overrides properties on a property-by-property basis.
If a property override exists in both locations, override.properties will take priority over CONFIG_OVERRIDE.
Custom properties made with CONFIG_OVERRIDE and override.properties will persist after an upgrade if the migrate-config script is used.