Upgrade a Transfer CFT multi-node installation

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

Before you start

Before beginning the upgrade procedure:

  • You require the product and Installer version number and SP level in order to choose the appropriate procedure. See Upgrade Transfer CFT .
  • Download the Transfer CFT Upgrade Pack, available at support.axway.com.
  • 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 from Transfer CFT 3.0.1 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.

Upgrade all hosts

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

  3. Connect to each machine and perform the following tasks:
  • Launch the Transfer CFT profile from the Transfer CFT runtime directory on the shared disk. For example:
  • cd /<shared_disk>/<CFTdir>/Transfer_CFT/runtime

    profile.bat

  • Begin the upgrade procedure as described in Upgrade from Transfer CFT 3.0.1.

Restart the upgraded Transfer CFT multi-node multihost 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.bat
  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 Copilot should be started
    • All of the Transfer CFT nodes must be started

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 from Transfer CFT 3.1.2 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.

Upgrade all hosts

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

  3. Connect to each machine and perform the following tasks:
  • Launch the Transfer CFT profile from the Transfer CFT runtime directory on the shared disk. For example:
  • cd /<shared_disk>/<CFTdir>/Transfer_CFT/runtime

    profile.bat

  • Begin the upgrade procedure as described in Upgrade from Transfer CFT 3.1.2.

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.bat
  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 Copilot should be started
    • All of the Transfer CFT nodes must be started

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.

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.

Display product information

The display command lists information about all installed products.

  • Run the command from the root installation directory.
  • When you run this command without parameters, the command lists all installed products and versions, and all applied service packs.

Use the name parameter to display the installation history of a single product.

Windows

display.bat

UNIX

./display.sh

Related Links