Startup Synchronization of Client Workstations

Each time you start a remote application on a client workstation, VTS must go through the startup synchronization process with the primary configuration server. During the startup synchronization process, VTS compares the application files and data on the client with the application files and data on the server. If the client application files and data are not up-to-date with those on the server, the server transmits the updated application files and data to the client. While this process is occurring, a dialog similar to the one shown below is displayed.

After the initial transference of application data (on the first occasion the application is run on the client following a "Get From Server" action), the startup synchronization process is incremental to reduce network traffic and the startup time for remote applications. This means that each time the application is run on the client workstation, the client and server compare application files and data; however, only those files and tags that the server determines to be outdated are sent to the client.

 

Run-Time Configuration

You now know that synchronization ensures that a remote application and its files and data are kept current each time the application is run, but you may wonder how this process is accomplished for those changes that occur while the application is running on both the server and client workstations. VTS keeps the application synchronized during run-time using a built-in locking scheme.

The locking scheme employed by VTS is controlled by the use of the "Remote Configuration" dialog that can be run from the configuration toolbox. The "Remote Configuration" dialog and the VTS locking scheme that is employed to keep all application data up-to-date are described in Remote Configuration and the VTS Locking Scheme.