Configuration File Hierarchy
There are specific files and directories upon which VTS relies in order to function properly. Because applications are built in layers, with all applications being built on at least one layer (the VTS layer), VTS begins to search the uppermost application layer for the files and directories it needs. If it does not find them, it continues to search down through the layers until the appropriate files and directories have been located, and it runs the first instance of a required file that it finds.
Note: It is important to remember that VTS loads components from the application layer down. You might have multiple copies of the same file across several layers, but VTS will use the copy found in the uppermost application layer first. If VTS does not find a copy in the application layer, it will search the customized layer that appears next in the hierarchy and so on. VTS always runs the first instance of a file it finds.
The Setup.ini configuration file contains system-wide configuration variables that affect the appearance and behaviour of the VTS software; there is therefore only one Setup.ini file.
On the other hand, application-specific configuration files such as Config.ini and SecurityManager.ini located within your application directory can be configured with variables that affect the appearance and behaviour of a VTS application.
Because many of the applications you create may be based on multiple layers, multiple instances of configuration files and multiple configuration variables may exist. Further, a workstation.ini file with the same variables as the Config.ini file may exist within the same application layer on the same workstation; therefore, VTS follows a specific hierarchy when loading configuration files and their variables.
This hierarchy depends upon the configuration of the application, including the configuration of the layers, and whether the application is a remote application with workstation.ini files present.
The important thing to remember is that regardless of the number of layers upon which your application is based, VTS follows the same loading procedure for configuration files and their variables as it does for other files and directories: it loads from the top layer (application layer) down.
Configuration File Hierarchy
for Applications Based on the VTS Layer (Standard Applications)
Configuration File Hierarchy
for Applications Based on Multiple Layers (Custom OEM Layers)
Configuration File Hierarchy
for Networked Applications with Workstation.ini
Files