Configuration File Hierarchy for Applications Based on Multiple Layers (Custom OEM Layers)

When dealing with standard VTS applications based on multiple custom OEM layers, VTS searches the uppermost application layer for configuration file variables. VTS finds and loads configuration variables found in the Config.ini file in the application layer. VTS will no longer search for the same variables in lower layers; the first value found for a variable is the value loaded by VTS.

VTS searches the next layer's (custom OEM layer's) Config.ini file for any variables that it did not find in the application layer's Config.ini file. VTS loads any variables it finds in the custom OEM layer's Config.ini file that were not present in the application layer's Config.ini file, VTS. VTS will no longer search for the same variables in lower layers; again, the first value found for a configuration variable is the value loaded by VTS.

For any configuration variables VTS does not find specified in the second layer, VTS searches the next layer's Config.ini file and loads any configuration variables it finds there. This process continues down through all layers. Finally, VTS will load default values from the master Config.ini file for any configuration variables not specified in a higher layer. This process is illustrated below.