Startup Synchronization

Startup synchronization is the second stage of remote configuration (for information on the first stage, please refer to Get From Server). Startup synchronization is the process whereby the application data is transferred from the server to the client so that both workstations have up-to-date copies of tags and files.

The first time that the application is run (or compiled – see note below) on the client workstation, the primary configuration server makes a copy of its tag properties database ("Points.mdb"), strips out the data so that the database is empty, and then transmits the empty tag properties database to the client. Next, the primary configuration server packages the tag data from its copy of the tag properties database and sends it to the client workstation where it is added to the client's copy of Points.mdb. Tags are sent in blocks on a per table basis; then application files are transferred.

The primary configuration server also sends a complete copy of the configuration database ("Config.db") to the client the first time the application is run.

The client generates its own blank copy of the replica tag database ("SCT.mdb"). When the application is run for the first time, the primary configuration server populates the client's SCT.mdb database with a copy of its data.

The ongoing synchronization process that occurs each time a VTS application is run is described in the section that follows.