Migrating from Transfer CFT 2.6.4 SP2 or 2.7

This topic describes how to migrate Transfer CFT 2.6.4 SP2, or higher, or 2.7 to version 3.6.

See also How to use programs without menus for help performing the migration commands.

Migrating the main configuration and UCONF parameters

You can migrate the PARM, PART, IDF, other static configuration objects and UCONF parameters as follows:

  1. Load the former Transfer CFT 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 new Transfer CFT 3.6 installation.
  5. Load the new Transfer CFT 3.6 environment.
  6. Import your static configuration objects using the cftinit command.
  7. cftinit CFTPROD/cft_ext

Migrating PKI certificates

  1. Load the former Transfer CFT (2.6.4 or 2.7) environment.
  2. Export your PKI certificates using the PKIUTIL PKIEXT command.
  3. PKIUTIL PKIEXT fout=CFTPROD/pki_ext

  4. Load the new Transfer CFT 3.6 environment.
  5. Create a new PKI internal datafile using the command PKIUTIL PKIFILE. Replace <pki_database_filename> with the value +CFTPKU.
  6. PKIUTIL PKIFILE fname=<pki_database_filename>, mode='CREATE’
  7. Import your PKI certificates into the new Transfer CFT 3.6 using the command PKIUTIL. Replace the <script_filename> with the new script file path:
  8. PKIUTIL <prefix_character><script_filename>

    Examples

    PKIUTIL @CFTPROD/pki_ext

Migrating the runtime environment

Migrating the catalog

  1. Load the former Transfer CFT (2.6.4 or 2.7) environment.
  2. Export the catalog using the command CFTMI240:
  3. CFTMI240 MIGR type=CAT, direct=FROMCAT, ifname=<catalog_2.7_filename>, ofname=catalog_output.xml

  4. Load the new Transfer CFT 3.6 environment.
  5. Import the catalog using the command CFTMI. Replace the <catalog_filename_new_installation> with the corresponding environment variable +CFTCAT.
  6. Example

    CFTMI MIGR type=CAT, direct=TOCAT, ifname=CFTPROD/cat_out, ofname=<catalog_filename_new_installation>

Migrating the communication media files

  1. Load the former Transfer CFT (2.6.4 or 2.7.0) environment.
  2. Export the communication media file using command CFTMI240:
  3. CFTMI240 MIGR type=COM, direct=FROMCOM, ifname=<com_2.7.0_filename>, ofname=CFTPROD/com_out
  4. Load the new Transfer CFT3.6 environment.
  5. Import the communication media file using command CFTMI. Replace the <com_filename_new_installation> with the corresponding environment variable:
  6. Example

    CFTMI MIGR type=COM, direct=TOCOM, ifname=com_ouput.xml, ofname=<com_filename_new_installation>

Related Links