In Developer, set up a Configure Configuration:
Select or create a Configuration to be used as the Configure Configuration.
Select the Segment Class of the application you want to transfer.
Right-click the Segment Class and select Properties from the pop-up menu. The Segment Configuration property pages dialog box appears.
Set the details for the target application using the following configuration properties:
Retain existing database: choose one of the options:
Select Retain Existing (True) to retain an existing database already on the target host. The database definition is altered to that on the Transfer medium.
Select No Retain Existing (False) to initialize a new database.
If you are configuring an optional standby application to support a secondary database you must select either Configure New Clone or Retain Existing Clone. In either case, the database itself is not configured (or reorganized), as this will have been performed by the Remote Database Backup clone procedure from the Database Operations Centre.
If you select Configure New Clone, all programs are installed.
Select Retain Existing Clone when you are transferring changed programs for an application that has been previously configured against your cloned database. However, if the level of your Agile Business Suite Software has changed, select Configure New Clone.
Target Host Name: enter the name of the target host.
Host Builder Usercode: enter the Host Builder usercode on the target host.
Configure Work Pack: enter a pack name on the target host.
Host Builder Dict Pack: enter the Host Builder dictionary pack. Do not enter any other details.
On the Host Login dialog box, ensure the usercode matches the usercode under which the target application resides.
Click OK.
To prepare the source configuration, perform the following:
Select or create a Configuration to be used as the Source Configuration.
Select the Segment Class of the application you want to transfer.
Right-click the Segment Class and select Properties from the pop-up menu. The Segment Configuration property pages dialog box appears.
On the Host Login dialog box, ensure the usercode matches the usercode under which the target application resides.
Click OK.
To build the RTU file, perform the following:
Select the Folder for the Source Configuration.
Set the following configuration properties to False, if you do not want to include a system or reports Rebuild at the same time:
Deploy Application Components
Deploy Database
Deploy Reports
Set the Generate Runtime Transfer Utility File configuration property to True.
Enter the values for the Folder configuration properties under the Runtime Transfer Utility category. The Source Configuration must be given, the RDB Configure is only required for a standby system.
RTU file: Local filename – Enter the name of RTU file to be created by the build on the client
Example: RTUFILE
RTU file: Host filename – Enter the name to be assigned to the RTU file when it has been transferred to the MCP HOST (use MCP naming convention)
Example: (MYUSER)RTUFILE ON MYPACK
Note: If a usercode is not included in the RTU file’s host filename, the RTU file is transferred to the usercode entered under Usercode on the host named in Deployment Host, not the FTP Usercode.
If a family name is not included in the RTU file’s host filename, the RTU file is saved to the default pack of the Usercode.
RTU Source set – From the drop-down list, select the Source configuration to be included in the RTU file.
RTU RDB Configure set – Leave blank if you are not using Remote Database Backup.
If you are creating or maintain a RDB system: from the drop-down list, select the RDB configuration to be included in the RTU file.
Additional Configurations – From the drop-down list, select one or more Target configurations to be included in the RTU file.
Click OK.
Build the Configure Folder.