Update Changes to Resource Items
If you intend to save the changes you have made to resource items and propagate those changes to all workstations running the application, you must update the applicable resource items using the Update Item button or the Update All button.
Note: It is recommended that you do not update any source files whose code has been modified without first compiling the code to ensure it contains no errors. If you are aware that the code for a resource item has been modified, compile the page's code, correct any errors, and then perform the update. This will ensure that you do not propagate errors to all clients running your application.
Note: There may be situations where you have built and configured a remote application and need to transfer it to a network at a remote site. If you do so, you should be especially careful to update all the locks on all resource items, otherwise you may find yourself unable to update the application at the remote site because the originating workstation that had resource items locked is not available to the remote network.
Update Changes to One Resource Item
The steps below will help to guide you through the process of updating a selected resource item, thereby propagating your modifications to all workstations running the application.
1. Logon to a user account that has been granted all system 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 and displays all resource items for the application.
4. Select the resource item whose modifications you wish to update.
5. Click the Update Item button.
The modifications to the selected resource item are updated and are propagated to all workstations running the application, and the lock on the selected resource item is released.
Once you have updated a selected resource item, you cannot rollback the update.
When you have made multiple modifications to a series of resource items, you may wish to update all the currently locked resource items. You may do so using the "Update All" button.
Note: Updating the "AppMod.src" source file for a remote application will prevent workstations from configuring the shared application, and requires that all workstations restart the remote application. When locking and updating the application's main source file, please see Lock and Update the AppMod.SRC File.
Update Changes to All Resource Items
Updating changes to all locked resource items at once can be achieved using the Update All button. This saves you the effort involved in selecting each resource item and clicking the Update Item button.
The information that follows demonstrates the process involved in updating multiple resource items.
Note: When you have locked a large number of items and have performed an Update All action, VTS processes these items into a list prior to performing the update. While the list is being assembled, clicking the Cancel button will stop the update operation. However, once the list has been assembled and sent to the server, clicking the Cancel button has no effect.
1. [If security is enabled] Logon to a user account that has been granted all system 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 and displays all resource items for the application.
4. Click the "Update All" button.
A dialog opens and requests confirmation that you wish to proceed with the update.
5. Click the "OK" button.
The modifications to all locked resource items are updated and are propagated to all workstations running the application, and the locks on all resource items are released.
Once you have updated all resource items, you cannot rollback the update.
Note: If you are aware that the code for a resource item has been modified, be sure to compile the page's code and correct any errors prior to performing an update. This will ensure that you do not propagate errors to all clients running your application.
Note: Updating the "AppMod.src" source file for a remote application will prevent workstations from configuring the shared application, and requires that all workstations restart the remote application. When locking and updating the application's main source file, please see Lock and Update the AppMod.SRC File.