As with many of VTS's services, it is possible to designate a workstation other than the primary configuration server to manage the Modem Manager Service.

In a remote application, the Modem Manager is configured to run on one workstation that has been designated as its server. This server can be a workstation other than the primary configuration server; as indicated in the topic, Primary Service Servers, it is prudent to spread services out over several different workstations to distribute the load on a larger application.

The Modem Manager 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 Modem Manager server; the other as a backup server in the case that the primary Modem Manager server fails. Whatever servers you choose must be added to the Config.ini configuration file under the [MODEMMANAGER–Servers] section. Workstations not specified as Modem Manager Servers will act as clients.

The following example demonstrates the correct way to set up the Config.ini configuration file for your application when designating servers to manage the Modem Manager for the application.

Config.ini

[MODEMMANAGER-Servers]

Name = LEBLANC

Name = PETERS

Name = CURRIE

When required, backup servers are called to take over the role of the active server in the order in which they are listed.

In this example, the workstation "LEBLANC" will be the primary Modem Manager server, while "PETERS" will be the first backup Modem Manager server; if "LEBLANC" should fail, "PETERS" will act as the Modem Manager server. Should "PETERS" fail, then the second backup server ("CURRIE") will act as the Modem Manager server.

The same configuration of the Config.ini file must be present on every workstation that is running the remote application.