Using override.properties to modify product configuration

The instructions below demonstrate how to use override.properties within Assure, Assure Client, Insight, Perceive and ER to modify product configuration.

Overriding Server properties

1) If it doesn't exist already, add a file named override.properties into the same location of your IA.properties. For example, this would be within:

<installation directory>/config/<jvm name>/IA

2) Add the property to override into the override.properties file. For example: 

UPDATE_SHARED_API_PHIST_COUNTS=false

If you have multiple properties to override, then add one per line:

UPDATE_SHARED_API_PHIST_COUNTS=false
MAX_CP_RUNDEPTH=100

3) Run the validate-config-values script from the installation's bin directory. A sample syntax of this script is below:

./validate-config-values -c IA IA

4) Run the update-config script from the installation's bin directory. A sample syntax of this script is below:

./update-config -c IA IA

Overriding Assure Client properties

1) If it doesn't exist already, add a file named override.properties into the same location of your IA.properties. For example, this would be within:

<client_install_home>/config/<jvm>/IA

2) Add the property to override into the override.properties file. For example: 

log4j.appender.iitap.MaxFileSize=10MB

If you have multiple properties to override, then add one per line:

log4j.appender.iitap.MaxFileSize=10MB
log4j.appender.iitap.MaxBackupIndex=15

3) Run the deploy-client script from the client installation's bin directory. A sample syntax of this script is below:

./deploy-client.sh -c JVM1 IA