In remote applications, many workstations run a VTS application. Each workstation sharing the application must have the ability to make changes to the files, pages and tags; to enable this process to occur, VTS provides a locking scheme.
When one workstation wants to make a change to an item, it must first obtain a lock on that item so that no other workstation can make changes to the same item at the same time. Once an item becomes locked, all other workstations on the network are kept informed, and no other workstation can change that item until the lock is freed. The locking scheme is handled by VTS's Remote Configuration tool.
The Remote Configuration tool stores the locking information for a standard, remote application in the configuration database named "Config.db".
Stored for each item are:
• The name of the item;
• The workstation that has the item locked;
• The server that allowed the item to be locked;
• Various lock classifiers; and,
• The date and time of the last modification of each item (known as a "revision value").
Note: It is strongly recommended that you do not modify the configuration database directly, as it is strictly for use by VTS; you should never edit Config.db
Configuration Database Regeneration
In the event that a remote application is experiencing client synchronization problems, and the configuration database has become corrupted, you can command VTS to regenerate a client's configuration database using the server's copy. This is known as forcing synchronization.