Migrating Transfer CFT 3.2.x, 3.3.2 or 3.4 to 3.6

This topic describes how to migrate Transfer CFT 3.2.x, 3.3.2, or 3.4 to version 3.6. It is divided in 2 sections, the first section describes migration for a single node architecture, and the second section multi-node architecture. Lastly there are instructions explaining what would be needed to migrate from single node architecture to multi node architecture.

Single node architecture

Stop Transfer CFT and the Copilot server before starting the migration.

Migrating the configuration

Migrating the main configuration and UCONF parameters

Migrate PARM, PART, IDF, other static configuration objects and UCONF parameters as follows:

  1. Load the former Transfer CFT 3.x environment. See the Migration prerequisites for details.
  2. Export your static configuration objects using the command CFTUTIL CFTEXT. Enter:
  3. CFTUTIL CFTEXT type=all, fout=cft-extract.conf
  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 Transfer CFT 3.6 environment.
  6. Stop Transfer CFT if you have not already done so.
  7. Import your static configuration objects using the cftinit command. Enter:
  8. cftinit cft-extract.conf

Migrating PKI certificates

Stop Transfer CFT and the Copilot server before starting.

  1. Load the former Transfer CFT 3.x environment.
  2. Export your PKI certificates using the command PKIUTIL PKIEXT. Enter:
  3. PKIUTIL PKIEXT fout=pki-extract.conf
  4. Copy all files that are referenced in the pki-extractconf file (INAME OR IKNAME) to the folder where you are going to execute the PKI command on the new version. In the following example, copy ROOT0001 to the new folder in Transfer CFT 3.6.
  5. PKICER ID = 'LOCALROOT',

    ROOTCID = 'LOCALROOT',

     ITYPE = 'ROOT', /*

    PKIFNAME = '',*/ /*

    COMMENT = '',*/

     INAME = 'ROOT0001',

     IFORM = 'DER', /*

     IKNAME = '',*/ /*

     IKFORM = '',*/ /*

     FOUT = '',*/

     MODE = 'REPLACE'

  6. Load the Transfer CFT 3.6 environment.
  7. Create a new PKI internal datafile using the command PKIUTIL PKIFILE. Replace <pki_database_filename> with the appropriate value: $CFTPKU for UNIX, the absolute path value for the CFTPKU for Windows. Enter:
  8. PKIUTIL PKIFILE fname=<pki_database_filename>, mode='CREATE’
  9. Import your PKI certificates into Transfer CFT 3.6 using the command PKIUTIL. Replace the <prefix_character> based on your system, @ for UNIX and # for Windows.
    Enter:
  10. PKIUTIL <prefix_character>pki-extract.conf

Migrating the runtime environment

Stop Transfer CFT and the Copilot server before starting.

Migrating the catalog

  1. Load the former Transfer CFT 3.x environment.
  2. Export the catalog using the command CFTMI. Replace the <catalog_filename > with the corresponding environment variable, _CFTCATA for UNIX or $CFTCATA for Windows. Enter:
  3. CFTMI MIGR type=CAT, direct=FROMCAT, ifname=<catalog_filename_former_cft>, ofname=catalog_output.xml
  4. Load Transfer CFT 3.6 environment.
  5. Import the catalog using the command CFTMI. Replace the <catalog_filename > with the corresponding environment variable, _CFTCATA for UNIX or $CFTCATA for Windows. Enter:
  6. CFTMI MIGR type=CAT, direct=TOCAT, ifname=catalog_output.xml, ofname=<catalog_filename_new_cft >

Migrating the communication media files

  1. Load the former Transfer CFT 3.x environment.
  2. Export the communication media file using command CFTMI. Replace the <com_filename > with the corresponding environment variable, _CFTCOM for UNIX, or $CFTCOM for Windows. Enter:
  3. CFTMI MIGR type=COM, direct=FROMCOM, ifname=<com_filename_former_cft>, ofname=com_output.xml
  4. Load Transfer CFT 3.6 environment.
  5. Import the communication media file using command CFTMI. Replace the <com_filename > with the corresponding environment variable, _CFTCOM for UNIX or $CFTCOM for Windows. Enter:
  6. CFTMI MIGR type=COM, direct=TOCOM, ifname=com_ouput.xml, ofname=<com_filename_new_cft >

Executables and binaries

Remember that you can copy your post-processing scripts directly from the runtime/exec to the new version (3.6). When you copy files from the exec folder, be certain to modify any paths that point to the former version (3.x in this case). However, you must rebuild APIs and EXITS (binaries).

Migrate a multi-node to multi-node architecture

Migrating the configuration

Stop Transfer CFT and the Copilot server before starting the migration.

Migrating the main configuration and UCONF parameters

Migrate PARM, PART, IDF, other static configuration objects and UCONF parameters as follows:

  1. Load the former Transfer CFT 3.x environment.
  2. Export your static configuration objects using the command CFTUTIL CFTEXT. Enter:
  3. CFTUTIL CFTEXT type=all, fout=cft-extract.conf
  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 Transfer CFT 3.6 environment.
  6. Import your static configuration objects using the cftinit command. Enter:
  7. cftinit cft-extract.conf

Migrating PKI certificates

Stop Transfer CFT and the Copilot server before starting.

  1. Load the former Transfer CFT 3.x environment.
  2. Export your PKI certificates using the command PKIUTIL PKIEXT. Enter:
  3. PKIUTIL PKIEXT fout=pki-extract.conf
  4. Load the Transfer CFT 3.6 environment.
  5. Create a new PKI internal datafile using the command PKIUTIL PKIFILE. Replace <pki_database_filename> with the appropriate value, $CFTPKU for UNIX or the absolute path value for the CFTPKU for Windows. Enter:
  6. PKIUTIL PKIFILE fname=<pki_database_filename>, mode='CREATE’
  7. Import your PKI certificates into Transfer CFT 3.6 using the command PKIUTIL. Replace the <prefix_character> based on your system, @ for UNIX and # for Windows. Enter:
  8. PKIUTIL <prefix_character>pki-extract.conf

Migrating the runtime environment

Stop Transfer CFT and the Copilot server before starting.

Migrating the catalog

  1. Load the former Transfer CFT 3.x environment.
  2. Export all catalogs (one per node, named as cftcataXX, where XX is the node number with range from 00 to <number of nodes - 1>) using the command CFTMI. For each catalog. Enter:
  3. CFTMI MIGR type=CAT, direct=FROMCAT, ifname=<catalog_filename_former_cft_node_<node>>, ofname=catalog_output_<node>.xml

  4. Load Transfer CFT 3.6 environment.
  5. Import all catalogs using the command CFTMI for each of them. Use the same node number on both <node> on command. Enter:
  6. CFTMI MIGR type=CAT, direct=TOCAT, ifname=catalog_output_<node>.xml, ofname=<catalog_filename_new_cft_node_<node>>

Migrating the communication media files

  1. Load the former Transfer CFT 3.x environment.
  2. Export all communication media files (cftcom and cftcomXX, where XX is the node number with range from 00 to <number of nodes - 1>) using the command CFTMI.
  3. For each communication media file, enter:
  4. CFTMI MIGR type=COM, direct=FROMCOM, ifname=<com_filename_for_node_manager_on_former_cft>, ofname=com_output.xml

  5. For each node, enter:
  6. CFTMI MIGR type=COM, direct=FROMCOM, ifname=<com_filename_for_node_<node>_on_former_cft>, ofname=com_output_<node>.xml

  7. Load Transfer CFT 3.6 environment.
  8. Import all communication media files using the CFTMI command.
  9. For the manager, enter:
  10. CFTMI MIGR type=COM, direct=TOCOM, ifname=com_ouput.xml, ofname=<com_filename_for_node_manager_on_new_cft>

  11. For each node, enter:
  12. CFTMI MIGR type=COM, direct=TOCOM, ifname=com_ouput_<node>.xml, ofname=<com_filename_for_node_<node>_on_new_cft>

Single-node to multi-node architecture migration

The only difference between migrating from single node to multi-node architecture and migrating from single-node to single-node architecture is the catalog migration step. Since there is no catalog named cftcata in multi-node, import the catalog exported from single-node architecture to the catalog of any of the nodes in the multi-node architecture.

Be certain to stop Transfer CFT and the Copilot server before performing the procedure.

Related Links