In a remote application, the Log Manager service can be configured to run on a workstation other than the primary configuration server. Spreading services out over several workstations rather than having the primary configuration server manage them all, can reduce the down time for your applications and can prevent data loss in the event of a server failure. (See: Primary Service Servers)
It is recommended that two servers be configured: one as the primary Log Manager server and the other as a backup server in case the primary server fails. The computers you choose must be added to the Config.ini configuration file under the [LOGMANAGER–Servers] section. Workstations not specified as Log Manager servers will act as clients.
The Log Manager’s data files and log files will be recorded on the hard drive of the workstation designated as the primary server. If the primary is offline, data will be recorded to the backup server until the primary server returns. When the primary server is restored, all data collected on the backup server will immediately be transferred to it.
The following example demonstrates the correct way to configure the Config.ini file when designating servers to manage the Log Manager for the application.
Config.ini
[LOGMANAGER-Servers]
Name = TONNET
Name = LAMBTON
Here, workstation "TONNET" is the primary Log Manager server, while "LAMBTON" is the backup server. If "TONNET" should fail, "LAMBTON" will act as the primary Log Manager server. When “TONNET” is brought back online, all data collected on “LAMBTON” will be immediately transferred to “TONNET”.
Servers and clients should be specified by name rather than by IP address. This is particularly important in networks where workstations may be dual-homed, or where dynamic IPs are assigned.
The same configuration of the "Config.ini" file must be present on every workstation that is running the remote application.
Note: In larger remote applications with a number of workstations, it might be wise to configure the "Config.ini" file prior to adding the application to all of the workstations that will be running it. This way identical "Config.ini" files will get copied to each of the workstations when they receive all of the application files from the server during synchronization.
Developers accustomed to early versions of VTS should note that the name of the Logger service has changed from "Logger" to "LogManager". Any section headers for entries in configuration files that are intended for the former Logger service will have to be updated to reflect this change (e.g. [LogManager-Servers], not [Loggers-Servers]).