Upgrade a Transfer CFT multi-node installation

This section describes how to upgrade from a Transfer CFT 3.1.3, 3.2.x, 3.3.2, or 3.4 multi-node, multihost installation to Transfer CFT 3.6.

As of Transfer CFT 3.4 there is no separate upgrade package, you use the installation package to perform an upgrade procedure as described in the sections below.

Before you start

Before beginning the upgrade procedure, download the Transfer CFT installation kit available at support.axway.com.

Note Remember that Transfer CFT clusters must be fully stopped while performing an upgrade.

Limitation

During an upgrade, if the CFTCOM file path is greater than 64 characters the COM file is not migrated, and you must migrate it manually.

Procedure

For details on shared disks, node commands, and other multi-node considerations, refer to the Transfer CFT 3.6 User Guide > Manage multi-node architecture.

Upgrade all hosts

  1. Stop Copilot. This command stops Copilot as well all cftnodes running on that machine.
  2. copstop -f

  3. Connect to the first machine and execute the following command:
  4. ./Transfer_CFT_3.6_Install_<OS>_<BN>.run --architecture first_host --installdir <installdir>

     

  5. For each additional host, connect to the machine and execute the following command:
  6. ./Transfer_CFT_3.6_Install_<OS>_<BN>.run --architecture additional_host --runtimedir <runtimedir>

  • Use the two following parameters, depending on if this is the first host or an additional host:
    • architecture and installdir (first_host), or
    • architecture and runtimedir (additional_host)
  • Where:
    • --architecture <architecture>: Installation architecture (first_host or additional_host).
    • --installdir <installdir>: For a legacy upgrade, this is the directory where the Axway Installer was installed. When this parameter is assigned, it overwrites any reference in the configuration file (first_host).
    • --runtimedir <runtimedir>: For a legacy upgrade, you must specify the installation’s shared directory instead of the runtime. For example: /mnt/Axway_Shared or Z:\Axway_Shared
      When this parameter is assigned, it overwrites any reference in the configuration file (additional_host).

Restart the upgraded Transfer CFT multihost multi-node environment

  1. Launch the Transfer CFT profile from the Transfer CFT runtime directory on the shared disk of each machine.
  2. cd /<shared_disk>/<CFTdir>/Transfer_CFT/runtime
  3. . ./profile
  4. Check the new version using the following command:
  5. CFTUTIL ABOUT

  6. Start Copilot (start each of the Copilots in the multi-node environment).
  7. copstart

  8. After restarting the Copilots, restart the Transfer CFT server:
  9. cft restart

  10. Check the upgraded Transfer CFT multi-node multihost system.
  11. CFTUTIL listnode

    • All of the Copilots should be started
    • All of the Transfer CFT nodes must be started

Your Transfer CFT 3.6 exec scripts are now operational. However, you must rebuild your APIs and Exits. Once Transfer CFT has been upgraded on a host you can start that instance, there is no need to wait until Transfer CFT is upgraded on every host.

Managing multi-node

For details on shared disks, node commands, and other multi-node considerations, refer to the Transfer CFT 3.6 User Guide > Manage multi-node architecture.

Post upgrade

After completing the upgrade procedure, your Transfer CFT 3.6, exec scripts are operational. However, you must rebuild your programs that use APIs and exits.

After performing an upgrade, all passwords are cyphered using a hard-coded key. We recommend that you generate an encryption key as described in Generate an encryption.

Check the new version

To check the Transfer CFT version, as well as the license key and system information, enter the command:

CFTUTIL ABOUT

Uninstall an upgrade pack

The procedure is the same as when you uninstall a Service Pack. See Uninstall Transfer CFT.

Related Links