Configuration Files and Variables

VTS includes several configuration files that can be used to set variable values. Some configuration files are used to change the appearance and behaviour of the VTS software, while others are used to set the appearance and behaviour of a specific application. The table below identifies the available VTS configuration files, identifies their scope, and indicates their location. It should be noted that literal file names are displayed in quotes below.

File Name	Purpose
Setup.ini	VTS product directory System-wide configuration: Affects behaviour and appearance of VTS program
Config.ini	Application directory Application-specific configuration: Affects behaviour and appearance of VTS application
workstation.ini	Application directory There is no template workstation.ini file. You must generate a text file, name it appropriately, and specify the proper sections and variables within it. The naming convention for workstation.ini files is the name of the workstation, followed by the .INI extension (e.g. "FREDSPC.INI") A workstation will only obey workstation.ini file with its own name plus the .ini extension; you may therefore store several workstation.ini files on a single workstation. Application-specific, workstation-specific configuration: Same sections/variables as Config.ini. Affects behaviour and appearance of VTS application on a per-workstation basis.
SecurityManager.ini	Application directory. Formerly "SecMgr.ini", this file has now been renamed "SecurityManager.ini". Any configuration sections applicable to the Security Manager have been changed from the prefix [SECMGR–…] to [SECURITYMANAGER–…]. It should be noted that the Security Manager's data file "SecMgr.dat" remains unchanged. Additionally, existing applications using a "SecMgr.ini" configuration file will still work. Application-specific configuration: Affects behaviour of VTS security options for a VTS application
AlarmManager.ini	Application directory There is no template AlarmManager.ini file. You must generate a text file, name it AlarmManager.ini, and specify the appropriate sections and variables within it. Application-specific configuration: Affects behaviour of alarms for a VTS application
service.ini	Application directory There is no template service.ini file. You must generate a text file, name it suitably, and specify the appropriate sections and variables within it. The naming convention for service.ini files is the name of the service, followed by the .INI extension (e.g. "MYSERVICE.INI") Application-specific configuration: Allows you to create custom services for a VTS application
ToolExt.ini	Application directory There is no template ToolExt.ini file. You must generate a text file, name it "ToolExt.ini", and specify the appropriate variables within it. Application-specific configuration: Allows you to expand the configuration tools for a VTS application.

The syntax and hierarchy of configuration files are described in the sections that follow.

Topics in this section:

Configuration File Hierarchy

Configuration File Composition

Configuration File Editing

Config.ini configuration file sections

Introduction to Setup.ini

Introduction to SecurityManager.ini

Introduction to Workstation.ini

Introduction to AlarmManager.ini

Introduction to Service.ini

Introduction to ToolExt.ini