It is recommended that you do not copy a remote application from one workstation to another simply by copying the application directory and pasting it into the VTS product or installation directory on the destination workstation. When copying a remote application, it is always preferable to use the "Get From Server" option and allow VTS to copy all required files and directories to the destination workstation (see Retrieving Remote Applications from a Server).
However, it is conceivable that you might build a remote application on a workstation that is not connected to the destination network, and then wish to copy the remote application to a workstation on the destination network.
Note: If you do so, you should be especially careful to update all locks on the application's resource items prior to copying it; 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.
Further, if the remote application you are copying to a remote network is also a layered application, you must be sure to include all application directories for each layer to the destination workstation.
The instructions below will assist you in copying the remote application from one workstation and run it as a remote application on another.
First, ensure that all configuration changes are up to date:
1. Run the application on the originating workstation.
2. Logon to the application using a user account that has been granted all security privileges.
3. Click the Configure button.
4. Click the Remote Configuration button.
5. Update any resource items that have been locked for modification. (If you need assistance in doing so, please refer to "13: Working with Remote Applications: Remote Configuration and the VTS Locking Scheme: Update Changes to Resource Items).
6. Close the Remote Configuration dialog.
7. Close the Configuration Toolbox.
Second, copy the application directory:
1. Stop the application on the originating workstation.
2. Navigate to the VTS installation directory on the originating workstation.
3. Copy the application directory and the application directories of any custom OEM layers upon which the application is based.
4. Paste the application directory and the application directories of any custom OEM layers upon which the application is based to the VTS installation directory on the destination workstation.
Third, edit the application’s configuration options.
1. Open the Sync.wif file in the application directory on the destination workstation using the text editor of your choice.
2. Modify any "Name = X" references from the Sync.wif file's [Configuration-Servers] section so that the local workstation's name appears first in the list. The first workstation referenced in the [Configuration-Servers] section will be the primary configuration server for the application, while any subsequent workstations specified in the list will be the backup servers for the application. Note: If you are unfamiliar with the term "primary configuration server" and "backup servers", it is strongly recommended that you review VTS Servers and Clients Defined.
3. Save the Sync.wif file.
4. Close the Sync.wif file.
5. Open the Config.ini file in the application directory on the destination workstation using the text editor of your choice.
6. Modify any "Name = X" references from the Config.ini file's [RPCManager-Servers] section so that the local workstation's name appears first in the list. The first workstation referenced in the [RPCManager-Servers] section will be the primary server for the RPC Manager service, while any subsequent workstations specified in the list will be the backup service servers for the application. Note: If you are unfamiliar with the term "primary service server" and "backup service servers", it is strongly recommended that you review VTS Servers and Clients Defined.
7. Check the Config.ini file for any other sections that specify servers for different VTS services and modify their "Name = X" references (e.g. [AlarmManager-Servers], [LogManager-Servers], etc.) (These sections may or may not exist, depending upon the configuration of the original application.)
8. Save the Config.ini file.
9. Close the Config.ini file.
10. Run the application on the destination workstation.
The application will now run on the destination workstation as a remote application. In this scenario, the destination workstation has become the primary configuration server. Client workstations on the same network as the primary configuration server may now perform a Get From Server action to obtain the latest copy of application data. Instructions on retrieving an application from a server are provided in Retrieving Remote Applications from a Server.