Convert an Existing Remote Application into a Local Application

When you initially create a remote application, a file named Sync.WIF is created and is added to your application directory. Within this file the primary configuration server (see Primary Configuration Server) and backup servers (see Backup Servers) for the application are identified in a section like the one displayed below.

[Configuration-Servers]

Name = WatchKeeperStation 

Name = Chief 

Name = EngineRoom 

 

A local application is one that does not have a designated primary configuration server or backup servers. To convert your remote application to a local application, you must stop your application, open the Sync.WIF file, and disable the [Configuration-Servers] list by placing a semicolon before each workstation reference. An example is displayed below.

;[Configuration-Servers]

;Name = WatchKeeperStation 

;Name = Chief 

;Name = EngineRoom 

 

In addition to editing the Sync.WIF file for your application, you must edit your application's "Config.INI" file to clear any service server lists that may be saved within it.

When you first create a remote application, a section like the example displayed below is added to your application's Config.INI file.

[RPCManager-Servers]

Name = Chief 

Name = EngineRoom 

Additionally, your application may have been configured with additional sections identifying the servers for different VTS services. An example is displayed below.

[SecurityManager-Services]

Name = WatchKeeperStation 

Name = EngineRoom 

To clear these service server lists, place a semicolon before each section and workstation reference. An example is displayed below.

;[RPCManager-Servers]

;Name = Chief 

;Name = EngineRoom 

;[SecurityManager-Services]

;Name = WatchKeeperStation 

;Name = EngineRoom 

 

Once you have edited the Sync.WIF and Config.INI files, you may run the application. It will load and run locally.