Overriding Properties

Installation typically makes all of the modifications needed to properties files, but if your installation customizes some properties, best practice is not to change default properties, but to override them. This eliminates updates or new installations overwriting property files you have configured. Best practice also includes backing up the override file(s) as described below.

To override a property, put the property itself in installed.properties under owareapps\installprops\lib. You can override selected (high availability) mediation server properties in owareapps\installprops\medserver\lib. Application property values are loaded first and you can override those values here.

Installation updates or refreshes the appropriate properties in installed.properties, but does not overwrite the file. This means property additions you make are safe from installation changing them in this override file. New properties coming from an installation are appended to the files.

The following is an example of property file content to override an application

cache time-out:

#============================================

# Dependencies

#============================================

product.dependencies=redcell

 

#============================================

# Application Overrides

#============================================

# set event template cache timeout to 1 minute

redcell.assurance.batch.processing.event.template.cache.expiration=60000

If any of the dependency directory names (for example, owareapps/redcell) do not exist, then the application does not load override file.

Consult the comments in the properties files you are overriding for further information about specific properties.

You can also override properties by renaming the provided file \oware\syn­ergy\conf\server-overrides.properties.sample to server-overrides.properties, and enable the properties within it by uncommenting them, and altering them to fit your needs. The comments in this file provide more information.