In a remote application, the Edit Lockout Manager service can be configured to run on a workstation other than the primary configuration server. As discussed in Designate Primary and Backup Service Servers, 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.
When a server has been specified for the Edit Lockout Manager, it runs as a server on one workstation and as a client on the other workstations in the system.
It is recommended that at least two servers be arranged: one as the primary Edit Lockout Manager server; the other as a backup server in the case that the primary Edit Lockout Manager server fails. The servers you choose must be added to the Config.INI configuration file under the [EDITLOCKOUTMANAGER–Servers] section. Workstations not specified as Edit Lockout Manager servers will act as clients.
The following example demonstrates the correct way to configure the Config.INI file when designating servers to manage the Edit Lockout Manager for the application.
[EDITLOCKOUTMANAGER-Servers]
Name = JOHNSON
Name = MCNEIL
In this example, the results will be that workstation "JOHNSON" will be the primary Edit Lockout Manager server, while "MCNEIL" will be the backup Edit Lockout Manager server; if "JOHNSON" should fail, "MCNEIL" will act as the primary Edit Lockout Manager server.
It is strongly recommended that you specify the servers and clients 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. In the case of remote applications, you can also use VTS's locking scheme to lock and update the modified Config.INI file, thereby propagating the changes to all clients (see Remote Configuration and the VTS Locking Scheme).
The primary server for any service is simply the workstation that is listed first under the service's server heading in the Config.INI configuration file; any subsequent workstations in the list are backup servers that will assume the role of primary server for the service in the event that the specified primary server experiences a failure.
In the case of the Edit Lockout Manager, there is an exception to this procedure. Information is provided in the section that follows.