It is not recommended that you copy a remote application from one workstation to another simply by copying it. 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 possible 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.
Caution: 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 local 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 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. Remove any "Name = X" references from the Sync.wif file's [Configuration-Servers] section (i.e. the [Configuration-Servers] section of the application's Sync.wif file should appear like the example displayed below. (This will convert the remote application to a local application by removing its references to its primary configuration server and backup servers.)
[Configuration-Servers]
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. Remove any "Name = X" references from the Config.ini file's [RPCManager-Servers] section (i.e. the [RPCManager-Servers] section of the application's Config.ini file should appear like the example displayed below. (This will convert the remote application to a local application by removing its references to the primary service server and backup servers for the RPC Manager service.)
[RPCManager-Servers]
7. Check the Config.ini file for any other sections that specify servers for different VTS services and remove these sections and their "Name = X" references (e.g. [AlarmManager-Servers], [LogManager-Servers], etc.) (This will convert the remote application to a local application by removing its references to the primary service server and backup servers for the specified services.)
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 local application.
Note: If you wish to copy a remote application to a different workstation and modify it to run with a different set of servers, you may do so by following the steps outlined in the section that follows.