Upgrade a Transfer CFT multi-node installation

This section describes how to upgrade a multi-node, multihost Transfer CFT from version 3.0.1, 3.1.2, 3.1.3 or 3.2.x to Transfer CFT 3.3.2.

Before you start

Before beginning the upgrade procedure:

  • Stop the Transfer CFT server and the Transfer CFT UI server, by entering:
    • cft stop
    • copstop -f
Note Transfer CFT clusters must be fully stopped while performing an upgrade.

Upgrade Transfer CFT 3.0.1 multi-node to 3.3.2

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

Upgrade all hosts

  1. Connect to each machine. Launch the Transfer CFT profile from the Transfer CFT runtime directory on the shared disk. For example:
  2. cd /<shared_disk>/<CFTdir>/Transfer_CFT/runtime

    . ./profile

  3. On each host, stop Copilot. This command stops Copilot as well all Transfer CFT nodes running on that machine.
  4. copstop -f

  5. Check the status of each Transfer CFT node:
  6. CFTUTIL listnode

  7. If Copilot and all nodes are stopped, begin the upgrade procedure as described in Upgrade Transfer CFT 3.0.1 to 3.3.2.

Upgrade the additional hosts

Repeat the above upgrade procedure on each 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.3.2 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.

Upgrade Transfer CFT  3.1.3 or 3.2.4 multi-node to 3.3.2

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

Upgrade all hosts

  1. Connect to each machine. Launch the Transfer CFT profile from the Transfer CFT runtime directory on the shared disk. For example:
  2. cd /<shared_disk>/<CFTdir>/Transfer_CFT/runtime

    . ./profile

  3. On each host, stop Copilot. This command stops Copilot as well all Transfer CFT nodes running on that machine.
  4. copstop -f

    • Check the status of each Transfer CFT node:
  5. CFTUTIL listnode

Upgrade the additional hosts

Repeat the above upgrade procedure on each 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.
  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.3.2 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.3.2 User Guide > Manage multi-node architecture.

Post upgrade

After completing the upgrade procedure, your Transfer CFT 3.3.2, 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