Migrating Transfer CFT 2.6.4 SP2 or 2.7 to 3.6

This topic describes how to migrate Transfer CFT 2.6.4 SP2, or higher, or 2.7 to version 3.6. Before starting this migration procedure, review the prerequisites and information on loading the environment. Additionally, you must have installed your new Transfer CFT 3.6 and applied the most recent service pack.

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 Migration prerequisites for details.
  1. Export your static configuration objects using the command CFTUTIL CFTEXT.
    Enter:
  2. CFTUTIL CFTEXT type=all, fout=cft-extract.conf
  1. Open the extract configuration files, cft-extract.conf, and update the file paths with those of the new Transfer CFT 3.6 installation.
  1. Load the new Transfer CFT 3.6 environment.
  1. Stop Transfer CFT if you have not already done so.
  2. Import your static configuration objects using the cftinit command. Enter:
  3. cftinit cft-extract.conf

Migrating PKI certificates

  1. Load the former Transfer CFT (2.6.4 or 2.7) environment.
  1. Export your PKI certificates using the command PKIUTIL PKIEXT. Enter:
  2. PKIUTIL PKIEXT fout=pki-extract.conf
  1. Load the new Transfer CFT 3.6 environment.
  1. Create a new PKI internal datafile using the command PKIUTIL PKIFILE. Replace <pki_database_filename> with the OS appropriate value:
  • UNIX: $CFTPKU
  • Windows: The absolute path value for the CFTPKU environment variable:
    PKIUTIL PKIFILE fname=<pki_database_filename>, mode='CREATE’
  1. 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:
  2. PKIUTIL <prefix_character><script_filename>

Examples

UNIX: PKIUTIL @pki-extract.conf

Windows: PKIUTIL #pki-extract.conf

Migrating the runtime environment

Migrating the catalog

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

  1. Load the new Transfer CFT 3.6 environment.
  1. Import the catalog using the command CFTMI. Replace the <catalog_filename_new_installation> with the corresponding environment variable:
  • UNIX: _CFTCATA
  • Windows: $CFTCATA

Example

CFTMI MIGR type=CAT, direct=TOCAT, ifname=catalog_output.xml, ofname=<catalog_filename_new_installation>

Migrating the communication media files

  1. Load the former Transfer CFT (2.6.4 or 2.7.0) environment.
  1. Export the communication media file using command CFTMI240:
  2. CFTMI240 MIGR type=COM, direct=FROMCOM, ifname=<com_2.7.0_filename>, ofname=com_output.xml
  1. Load the new Transfer CFT3.6 environment.
  1. Import the communication media file using command CFTMI. Replace the <com_filename_new_installation> with the corresponding environment variable:
  • UNIX: _CFTCOM
  • Windows: $CFTCOM

Example

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

Related Links