Configuration File Hierarchy for Networked Applications with Workstation.ini Files
When dealing with a remote, layered application that does not have workstation.ini files that specify configuration variables for different workstations, VTS follows the same procedure it would for a layered application; it searches for configuration variables starting from the application layer down to the VTS layer (see Configuration File Hierarchy for Applications Based on Multiple Layers (Custom OEM Layers).) However, the presence of a workstation.ini configuration file in a layer changes the way that VTS searches for configuration variables: if a workstation.ini file named after the local workstation is detected in the application layer, VTS loads its configuration variables prior to reviewing those in the Config.ini file in the same application layer.
Note: VTS will only read and load variables from workstation.ini configuration files with the same name as the workstation on which they exist (for example, a client named Workstation6 will only recognize a workstation.ini file named "Workstation6.ini"); all other workstation.ini configuration files will be ignored.
If VTS finds configuration variables have been declared in a workstation.ini file, it ceases to search for the same variables in any configuration file in this or any lower layer. VTS continues its search for configuration variables that were not declared in the workstation.ini file by first searching the Config.ini file within the same layer.
VTS loads any additional configuration variables it finds in the Config.ini file in the application layer. VTS ceases the search for the same variables in any configuration file in any lower layer. VTS continues to search the next layer for those configuration variables it did not find using the same process. Finally, VTS loads the default values for any configuration variables that were not identified in higher layers from the master Config.ini file in the VTS layer. This process is illustrated below.
A solid understanding of the hierarchy of configuration files and VTS layers will help you to customize your applications.
When you are configuring non-default values for a remote application's variables, place those variables whose values you wish to be universal across the network in the Config.ini file in the uppermost application layer. Place those variables whose values you wish to be specific to a workstation in a workstation.ini file in the same application layer.
Forthcoming sections describe each of the configuration files in detail, along with their variables and default values; however, it is first important to understand the appearance and arrangement of configuration files.