Migrating from Transfer CFT 2.3.2

This section describes how to migrate Transfer CFT 2.3.2 to 3.6. See also How to use programs without menus for help performing the migration commands.

Migrating the configuration

Migrate the main configuration

Migrate PARM, PART, IDF and other static configuration objects.

  1. Load the Transfer CFT 2.3.2 environment. See the Prerequisites for details.
  2. Export your static configuration objects using the CFTUTIL CFTEXT command.
  3. CFTUTIL CFTEXT type=all, fout=CFTPROD/cft_ext
  4. Open the extract configuration files, cft-extract.conf, and update the file paths with those of the Transfer CFT 3.6 installation.
  5. Load the Transfer CFT 3.6 environment.
  6. Import your static configuration objects using the cftinit command.
  7. cftinit CFTPROD/cft_ext

Migrating TRKCNF file parameters

  1. In the TRKCNF file, select the parameters you want to import into 3.6.
  2. Create a script file, for example: TRKAPI_IMP
  3. For each parameter you select, add a UCONF command line to your new script file using the format:
  4. UCONFSET id=<parameter_id>, value=<value>
  5. Use the parameter mapping between trkapi and UCONF, as listed in the following table, to specify the correct parameter id.
  6. Parameter mapping between the CFTPROD/UTIN(TRKCNF) file and UCONF

    Parameter in trkapi.cfg

    Parameter names in UCONF

    TRACE

    sentinel.trktrace

    TRKGMTDIFF

    sentinel.trkgmtdiff

    TRKIPADDR_BKUP

    sentinel.trkipaddr_bkup

    TRKIPPORT

    sentinel.trkipport

    TRKIPPORT_BKUP

    sentinel.trkipport_bkup

    TRKLOCALADDR

    sentinel.trklocaladdr

    TRKPRODUCTNAME

    sentinel.trkproductname

    XFB.BufferSize

    sentinel.xfb.buffer_size

    XFB.Log (UNIX)

    sentinel.xfb.log

    XFBLOG (Windows)

    sentinel.xfb.log

    XFB.Sentinel

    sentinel.xfb.enable

    XFB.Trace

    sentinel.xfb.trace

    XFB.Transfer

    sentinel.xfb.transfer

  7. Load the Transfer CFT 3.6 environment.
  8. Import the selected UCONF parameters using the command CFTUTIL. Replace <script_filename> with the new script file path: CFTUTIL <prefix_character><script_filename>
  9. Example

    CFTUTIL @TRKAPI_IMP

Migrating PKI certificates

Exporting PKI certificates from Transfer CFT 2.3.2 is not supported. For this reason, you must create a new PKI database in the Transfer CFT 3.6 runtime using the PKIUTIL PKIFILE command. Next import each certificate using the PKIUTIL PKICER command.

For more information, refer to the Transfer CFT 3.6 User's Guide, sections Using the PKIFILE command and Using the PKICER command.

Migrating the runtime environment

Migrate the catalog

  1. Load the Transfer CFT 3.6 environment.
  1. Export the catalog using the command CFTMI230:
  2. CFTMI230 MIGR type=CAT, direct=FROMCAT, ifname=<catalog_2.3.2_filename>, ofname=CFTPROD/cat_out
  3. Import the catalog using the command CFTMI. Replace the <catalog_filename_new_installation> with the corresponding environmental variable: +CFTCAT
  4. CFTMI MIGR type=CAT, direct=TOCAT, ifname=CFTPROD/cat_out, ofname=<catalog_filename_new_installation>

Migrating the communication media files

  1. Load the Transfer CFT 3.6 environment.
  2. Export the communication media file using command CFTMI230:
  3. CFTMI230 MIGR type=COM, direct=FROMCOM, ifname=<com_2.3.2_filename>, ofname=CFTPROD/com_out
  4. Import the communication media file using command CFTMI. Replace the <com_filename_new_installation> with the system-specific environment variable: +CFTCOM
  5. CFTMI MIGR type=COM, direct=TOCOM, ifname=com_ouput.xml, ofname=<com_filename_new_installation>

Related Links