Customization and Advanced Configuration

The following list provides a summary of some of the more important RiskVision Server customizations that customers can tailor based on their own requirements. For more information, contact Resolver Support:

• RiskVision Server configuration and optimization; certificates and Apache SSL/https setup;

• Default virtual group setup;

• Custom entity definition;

• Some GUI customization;

• Mapping the RiskVision server data folder to an external drive; and

• Run system jobs on a separate machine.

The RiskVision Server uses a number of different server property and XML configuration files to set parameters and customize operations. These files are stored on the machine where the RiskVision Server is installed. This directory contains all default property and configuration settings: 

%AGILIANCE_HOME%\Tomcat\webapps\spc\WEB-INF\classes

This directory is used to optionally store files that overwrite default configuration settings: 

%AGILIANCE_HOME%\config

This directory is the root location where the RiskVision Server is installed: 

%AGILIANCE_HOME% 

The properties file in the %AGILIANCE_HOME%\config directory overwrites values from the corresponding files in the %AGILIANCE_HOME%\Tomcat\webapps\spc\WEB-INF\classes directory. You only need to specify those properties where you want to overwrite the default property settings. That way, you can easily change a few properties without having to specify the entire collection of properties in the overriding file. In these cases, you will create a properties file with only the changed properties and leave out the rest to default to their default values. Thus, the resulting effective properties used by are a combination of the two files.

Other key points about configuration:

1. The file names of the properties files in the two directories are different. For example, agiliance.properties in the %AGILIANCE_HOME%\config directory overrides the agiliance.default property settings in the agiliance.default.application.properties and agiliance.default.system.properties files.
2. For XML configuration files, the file names in the two directories are similar. If a file with a similar name exists in %AGILIANCE_HOME%\config, it will be used to replace the corresponding default configuration file. So, it’s important that the replacement configuration file contain all the settings of the original default file. You may want to backup the original default XML file and make changes to the copied file to override the settings in the default XML configuration files.
3. There are three XML configuration files - TextAttributes.xml, UICustomization.xml and SchedulerConfiguration.xml - that are exceptions to the processing rule described in item 2 above. For these three files, the entire contents of a new file do not replace the entire contents of the default configuration file, so you can simply include the elements that you want to override in a new XML configuration file. The only requirement is that you need to use complete XML path.

The following table lists the property and XML configuration files most commonly customized for specific RiskVision Server installations: