The Runtime Transfer Utility (RTU) enables you to transfer applications built and deployed from Developer to Runtime using Builder to other locations on the same host or different hosts.
Transfer Options
Standard Transfer
A standard transfer copies all the application objects and files, and Report objects associated with the application.
Selective Transfer
With a selective transfer, you can choose to transfer:
application files
Reports
Any Reports built since the last application generate
Transferable Reports
Transferable Reports built since the last application generate
Your selection of Reports
Compile-free Configure
With a compile-free configure, you do not require a compiler on the target host. The objects for the following files are compiled during the transfer phase instead of the configure phase:
DASDL
DMSUPPORT
RMSUPPORT
REORGANIZATION
DBILIBRARY
WDP
ROCSUPPORT
SQLSUPPORT
DBINTERFACE
Conditions for Using Runtime Transfer
Runtime Transfer is only available for Developer applications deployed to MCP target hosts using Builder.
If you select the Transferring All updated reports and All updated transferable reports options (Refer to Selected Transfer Screen), only Reports that have been built since the last application build is selected for transfer.
When you create a set of configuration properties for your model to use with the Runtime Transfer Utility:
The name you enter in the Name attribute for the set of configuration properties for your model must match the host where you intend to initiate the transfer.
You must specify a user code in the Usercode property under the Configure/BNA category for the deployment folder. The Runtime Transfer Utility does not recognize the default usercode.
If you are transferring from one host to another, both hosts must be running the same IC level of Runtime for ClearPath MCP. They must also be running the same mark level of Enterprise Database Server for ClearPath MCP software.
Restrictions on Using Runtime Transfer
Refer to Restrictions on Transfer and Configure.