Name

The Name field defines the name of application as it appears in the VAM. You can change the application's name using this field (see Changing an Application's Name).

Path

The Path field identifies the name of the directory where the application and its resources exist on the local workstation. This path name is relative to the VTS installation or product directory. This field was designated when the application was created, and it cannot be changed using the Application Properties dialog.

Note: If you find it absolutely necessary to change the name of an application, there is a method to doing so. Instructions appear in Renaming an Application Directory.

Type

The Type field indicates the layer upon which this application is based. This will be one of:

Standard Application: If the application is based on the VTS layer, the Type field will display Standard Application

Script Application: If the application is a script application, the Type field will display Script Application.

Layered Application: If the application is based on a custom OEM layer, the Type field will display the name of the application upon which this application is based (e.g. "Custom Tags and Tools").

The Type field was assigned when the application was being created, and it cannot be changed. Please refer to VTS Application Types for further information on application types.

AutoStart Application

The AutoStart Application checkbox sets the application to start automatically when the VAM runs. Information on auto-starting applications can be found in Controlling Closure of a VTS Application and the VTS Program.

Last Revised

The Last Revised text displays the last time and date this application's AppMod.src root file was modified. Information on the AppMod.src root file can be found in the VTS Programmer's Guide.

 Username:

The Username field enables you to specify the username that will enable you to access this application's tag properties database (Points.mdb) via the ODBC connection (see Tag Properties Database and Security).

Note: If your application is a remote application, the Username field is only enabled in the Application Properties dialog on the primary configuration server. This prevents unauthorized access to the tag properties database (Points.mdb) by clients.

Password

The Password field enables you to specify a password that will enable you to access this application's tag properties database (Points.mdb) via the ODBC connection (see Tag Properties Database and Security).

Note: If your application is a remote application, the Password field is only enables in the Application Properties dialog on the primary configuration server. This prevents unauthorized access to the tag properties database by clients.

Configuration Server Choices

The Configuration Server Choices list indicates the names of the workstations running VTS that will serve as the primary configuration server and backup servers for the application. The workstation at the top of the list is the primary configuration server with subsequent workstations being the backup servers. The configuration servers for the application are stored in the Sync.wif file under the [Configuration-Servers] section.

When the application is created, this list of servers is initially used as the default server list for all VTS services such as communications, alarms, and data logging. The VTS service servers are stored in the Config.ini configuration file under the [RPCManager-Servers] section.

After the application has been created, you can modify the configuration servers for the application using the Configuration Server Choices list (see Changing the Configuration Server for a Remote Application), however, if you wish to modify the default server list for all VTS services, or specify different servers for different VTS services, you must do so manually (i.e. modify the [RPCManager-Servers] section and any other service servers sections (e.g. [AlarmManager-Servers]) within your application's Config.ini file. Instructions on doing so appear in Designate Primary and Backup Service Servers.

Add

The Add button enables you to add workstations to the Configuration Server Choices list (see Designate Primary and Backup Configuration Servers ").

Delete

The Delete button enables you to remove workstations from the Configuration Server Choices list.

This Workstation is Server 

When the This Workstation is Server checkbox is selected, the name of the current workstation is automatically added to the top of the Configuration Server Choices list, and the local workstation becomes the primary configuration server for the application.

Please refer to see Designate Primary and Backup Configuration Servers " for further information.

Move Selected

The Move Selected arrow buttons enable you to change the order of the workstations as they appear in the Configuration Server Choices list. The workstation at the top of the list is the primary configuration server with subsequent workstations being the backup servers.

Force Clients to Synchronize: Files

The Force Clients to Synchronize: Files checkbox only appears on the primary configuration server for your application, and can only be selected once the application has been stopped. When selected, all clients will be forced to stop and restart their applications in order to gain the most recent copy of the configuration database (Config.db) (see Configuration Database (Config.db)).

This operation should be performed when clients appear to have a corrupted version of application data. Detailed instructions appear in Force All Clients to Synchronize with the Primary Configuration Server.

Force Synchronization Of: Files

The Force Synchronization Of: Files checkbox appears on each client running a remote application, and can only be selected once the application has been stopped on the client. When selected, this client will be given the most recent copy of the configuration database (Config.db) (see Configuration Database (Config.db).

This operation should be performed when a single client appears to have a corrupted version of application data. Detailed instructions appear in Force One Client to Synchronize with the Primary Configuration Server.

Force Clients to Synchronize: Tags

The Force Clients to Synchronize: Tags checkbox only appears on the primary configuration server for your application, and can only be selected once the application has been stopped. When selected, all clients will be forced to stop and restart their applications in order to gain the most recent copy of the replica tag database (SCT.mdb) (see Replica Tag Database (SCT.mdb).

This operation should be performed when clients appear to have corrupted tags. Detailed instructions appear in Force All Clients to Synchronize with the Primary Configuration Server.

Force Synchronization Of: Tags

The Force Synchronization Of: Tags checkbox appears on each client running a remote application, and can only be selected once the application has been stopped on the client. When selected, this client will be given the most recent copy of the replica tag database (SCT.mdb).

This operation should be performed when a single client appears to have corrupted tags. Detailed instructions appear in Force One Client to Synchronize with the Primary Configuration Server.

OK

The OK button saves any modifications made to the application's properties on this workstation.

Cancel

The Cancel button aborts any modifications made to this application's properties.