Manually upgrade Transfer CFT

This section explains how to upgrade an existing Transfer CFT IBM i from 2.7.1, 3.0.1, 3.1.3, 3.3.2, 3.4, or 3.5 to Transfer CFT 3.6 for either a single installation or a multi-node installation.

Before you start

Before beginning the upgrade procedure, you should:

  • Check that you have the Transfer CFT Upgrade Pack available for download from Axway Sphere at support.axway.com.
  • Stop the Transfer CFT server and the Transfer CFT Copilot (UI) server. Enter:

CFTSTOP

COPSTOP

Display product details

You can use the display command to check the version or product details prior to upgrading.

CFTUTIL about

Manually upgrade a single installation

The manual upgrade procedure is similar to the migration procedure.

  1. Load the former Transfer CFT CFT 2.7.1, 3.0.1, or 3.1.3 environment.
  2. Stop Transfer CFT.
  3. Create a backup library to save your configuration:
  • CRTLIB LIB(CFTUPGLIB)

    1. Export your configuration.
      • Export your static configuration objects using the command CFTUTIL CFTEXT:
      CALL PGM(CFTUTIL) PARM(‘CFTEXT’ ‘type=all, fout=CFTUPGLIB/EXTCONF’)
      • Export your PKI certificates using the PKIUTIL PKIEXT command. Enter:
      CALL PGM(PKIUTIL) PARM(‘PKIEXT’ ‘fout=CFTUPGLIB/EXTPKI’)
      • Export the catalog using the CFTMI command. Enter:
      CALL PGM(CFTMI) PARM(‘MIGR’ ‘type=CAT, direct=FROMCAT, ifname=CFTPROD/CAT, ofname=CFTUPGLIB/EXTCAT’)
      • Export the communication media file using the CFTMI command:
      CALL PGM(CFTMI) PARM(‘MIGR’ ‘type=COM, direct=FROMCOM, ifname=CFTPROD/COM, ofname=CFTUPGLIB/EXTCOM’)
      • Additionally, you must export any procedures that are specific to your production, sample APIs, exits, and execs to your backup library.
    2. Rename the INSTALL directory, the RUNTIME directory, and the Transfer CFT libraries.

      STRQSH CMD('mv /home/cft/install /home/cft/install_save')

      STRQSH CMD('mv /home/cft/runtime /home/cft/runtime_save')

      RNMOBJ OBJ(QSYS/CFTPROD) OBJTYPE(*LIB) NEWOBJ(CFTPRODSAV)

      RNMOBJ OBJ(QSYS/CFTPGM) OBJTYPE(*LIB) NEWOBJ(CFTPGMSAV)

    3. You can now install the new Transfer CFT version. See About the INSTALL command.
    4. Import the configuration.
      • Import your static configuration objects using the command:
      CFTINIT FILES('CFTUPGLIB/EXTCONF')
      • Import your PKI certificates using the PKIUTIL command:

      CALL PGM(PKIUTIL) PARM('PKIFILE' 'fname=CFTPROD/PKIBASE, mode=CREATE')

      PKIUTIL LIBRARY(EXTLIB) FILE(EXTPKI) MEMBER(EXTPKI)

      • Import the catalog using the CFTMI command:
      CALL PGM(CFTMI) PARM(‘MIGR’ ‘type=CAT, direct=TOCAT, ifname=CFTUPGLIB/EXTCAT, ofname=CFTPROD/CAT’)
      • Import the communication media file using the CFTMI command:
      CALL PGM(CFTMI) PARM(‘MIGR’ ‘type=COM, direct=TOCOM, ifname=CFTUPGLIB/EXTCOM, ofname=CFTPROD/COM’)
      • Import specific procedures to your production, for example APIs, EXITs, and execs from the CFTUPGLIB backup library.
      Note  You must recompile these after upgrading.

    Check the new version

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

    CFTUTIL about

    Manually upgrade a Transfer CFT 2.7.1, 3.0.1, or 3.1.3 multi-node installation

    The multi-node procedure is similar to the single instance upgrade procedure. However, when exporting CAT and COM, you must export your configuration for each node.

    1. Load the former Transfer CFT 2.7.1, 3.0.1, or 3.1.3 environment.
    2. Stop Transfer CFT IBM i.
    3. Create a temporary library for your exported configuration:
  • CRTLIB LIB(CFTUPGLIB)

    1. Export your configuration.
      • Export your static configuration objects using the command:
      CALL PGM(CFTUTIL) PARM(‘CFTEXT’ ‘type=all, fout=CFTUPGLIB/EXTCONF’)
      • Export your PKI certificates using the PKIUTIL PKIEXT command:
      CALL PGM(PKIUTIL) PARM(‘PKIEXT’ ‘fout=CFTUPGLIB/EXTPKI’)
      • Export the catalog using the CFTMI command:
      CFTMI MIGR type=CAT, direct=FROMCAT, ifname=<catalog_filename_ former_cft_for_node_<node>>, ofname=catalog_output_<node>.xml
      • Export the communication media file using the command:
        • For each communication media file, enter:
        • CALL PGM(CFTMI) PARM(‘MIGR’ ‘type=CAT, direct=FROMCAT, ifname=CFTPROD/CAT, ofname=CFTUPGLIB/EXTCAT’)
        • For each node, enter:
        • CALL PGM(CFTMI) PARM(‘MIGR’ ‘type=COM, direct=FROMCOM, ifname=CFTPROD/COM<nodenumber>, ofname=CFTUPGLIB/EXTCOM<nodenumber>’)l
      • You must also export any procedures that are specific to your production, such as APIs, exits, execs, etc. (Copy your API, exit sources, exec, and specific scripts.)
    2. Change the hostname for each Transfer CFT. Rename the INSTALL and RUNTIME directories, and the Transfer CFT libraries:
    3. STRQSH CMD('mv /home/cft/install /home/cft/install_save')

      STRQSH CMD('mv /home/cft/runtime /home/cft/runtime_save')

      RNMOBJ OBJ(QSYS/CFTPROD) OBJTYPE(*LIB) NEWOBJ(CFTPRODSAV)

      RNMOBJ OBJ(QSYS/CFTPGM) OBJTYPE(*LIB) NEWOBJ(CFTPGMSAV)

    4. You can now install the new Transfer CFT version. See About the INSTALL command.
    5. Import the configuration that you saved previously in the temporary directory created in Step 3:

      CFTINIT FILES('CFTUPGLIB/EXTCONF')

      • Import the PKI certificates using the PKIUTIL command:

      CALL PGM(PKIUTIL) PARM('PKIFILE' 'fname=CFTPROD/PKIBASE, mode=CREATE')

      PKIUTIL LIBRARY(EXTLIB) FILE(EXTPKI) MEMBER(EXTPKI)

      • Import the catalog using the CFTMI command:

      CALL PGM(CFTMI) PARM(‘MIGR’ ‘type=CAT, direct=TOCAT, ifname=CFTUPGLIB/EXTCAT, ofname=CFTPROD/CAT’)

      • Import the communication media file using the CFTMI command:
        • For each communication media file, enter:
        • CALL PGM(CFTMI) PARM(‘MIGR’ ‘type=COM, direct=TOCOM, ifname=CFTUPGLIB/EXTCOM, ofname=CFTPROD/COM’)

        • For each node, enter:
        • CALL PGM(CFTMI) PARM(‘MIGR’ ‘type=COM, direct=TOCOM, ifname=CFTUPGLIB/EXTCOM<nodenumber>, ofname=CFTPROD/COM<nodenumber>’)

      • Import specific procedures to your production, for example APIs, EXITs, and execs from the CFTUPGLIB backup library.
        Note  You must recompile these after upgrading.

    Check the new version

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

    CFTUTIL about

    Related Links