When you create a new remote application by specifying a primary configuration server and backup servers, VTS automatically assumes that the specified servers are also to be the primary and backup service servers for all VTS services for the application. A section similar to the one displayed below is written to your application's Config.INI configuration file:
[RPCManager-Servers]
Name = Chief
Name = EngineRoom
Name = WatchKeeperStation
If this arrangement is appropriate to your system, you need not reconfigure it.
You may however, wish to change the designation of the primary and backup service servers or add new servers. You might also want to define primary and backup servers for specific services.
The following steps will guide you through the process. Note that the process starts inside the running application, not with simply opening the Config.INI for editing. Since the application must have been created before it can be running, there is no distinction in the steps between new and existing applications as there was in the steps for designating primary and backup configuration servers.
1. [If security has been enabled] While the application is running, logon with a user account that has at least the "Configure", "Lock Item", and "Update" privileges.
2. Click the "Configure" button in the Display Manager's title bar.
The Configuration Toolbox opens.
3. Click the "Remote Configuration" button (labeled with a key).
The "Remote Configuration" dialog opens.
4. Select "Config.INI" in the list of resource items.
5. Click the "Lock Item" button.
The "Config.INI" resource item is marked as locked for modification by your workstation.
6. Click the "Close" button to close the "Remote Configuration" dialog.
7. Close the Configuration Toolbox.
8. Open the VAM.
9. Stop the application.
10. Navigate to your application directory.
11. Locate the "Config.INI" configuration file.
12. Open "Config.INI" using a text editor.
13. Locate the "[RPCManager-Servers]" section.
14. Modify this section so that the workstation you wish to be the primary service server for the RPC Manager Service is named first in the list, and the backup service servers are listed subsequently in hierarchical order.
15. [Optional] If you wish to designate primary and backup servers for various services, add a section header for each appropriate service (*) and add the server names to that list. An example of a service section is displayed below.
[AlarmManager-Servers]
Name = EngineRoom
Name = WatchKeeperStation
16. Save and close the "Config.INI" configuration file.
17. Open the VAM.
18. Run your VTS application.
19. [If security has been enabled] Logon to the application with a user account that has at least the "Configure", "Lock Item", and "Update" privileges.
20. Click the "Configure" button in the Display Manager's title bar.
The Configuration Toolbox opens.
21. Click the "Remote Configuration" button (labeled with a key).
The "Remote Configuration" dialog opens.
22. Select "Config.INI" in the list of resource items.
23. Click the "Update Item" button. The modified "Config.INI" file is propagated to all clients running the application.
This step is required even if the application has not yet been added to any clients. Only those files that have been “updated” will be transferred to new and existing clients.
24. Close the "Remote Configuration" dialog.
25. Close the Configuration Toolbox.
(*) Information on the appropriate syntax for the different VTS services can be found in the following sections:
• Alarm Manager (Designate Alarm Manager Server(s) for a Remote Application).
• Log Manager (Designate Log Manager Server(s) for a Remote Application).
• Security Manager (Designate Security Manager Server(s) for a Remote Application).
• Modem Manager (Designate Modem Manager Server(s) for a Remote Application).
• RPC Manager (see RPC Manager Service).
• Edit Lockout Manager (see Designate Edit Lockout Manager Server(s) for Remote Applications).
• In the event that you have created your own service, you can configure the primary and backup servers for the custom service using the same syntax.
[MyServiceName–Servers]
Name = WorkstationA
Name = WorkstationB