Migrating from Transfer CFT 2.4

This topic describes how to migrate from Transfer CFT 2.4 to version 3.6. Before starting this migration procedure, perform the steps described in Prerequisites.

See also How to use programs without menus for help performing the migration commands.

Migrating the configuration

Migrating the main configuration

Migrate PARM, PART, IDF and other static configuration objects.

  1. Load the Transfer CFT 2.4 environment. See the Prerequisites for details.
  1. Export your static configuration objects using the CFTUTIL CFTEXT command.
  2. CFTUTIL CFTEXT type=all, fout=CFTPROD/cft_ext
  3. Open the extract configuration files, CFTPROD/cft_ext, and update the file paths with those of the Transfer CFT 3.6 installation.
  4. Load the Transfer CFT 3.6 environment.
  5. Import your static configuration objects using the cftinit command.
  6. cftinit CFTPROD/cft_ext

Migrating the TRKCNF file parameters

Migrate the parameters from the Transfer CFT 2.4TRKCNF file.

  1. In the TRKCNF file, select the parameters you want to import to 3.6.
  1. Create a script file, for example: TRKAPI_IMP
  1. For each parameter you select, add a UCONF command line to your new script file using the format:
  2. UCONFSET id=<parameter_id>, value=<value>
  3. Use the parameter mapping between CFTPROD/UTIN(TRKCNF) and UCONF, as listed in the following table, to specify the correct parameter id.
  4. Parameter mapping between the TRKCNF file and UCONF

    Parameter in trkapi.cfg

    Parameter names in UCONF

    TRACE

    sentinel.trktrace

    TRKGMTDIFF

    sentinel.trkgmtdiff

    TRKIPADDR_BKUP

    sentinel.trkipaddr_bkup

    TRKIPPORT

    sentinel.trkipport

    TRKIPPORT_BKUP

    sentinel.trkipport_bkup

    TRKLOCALADDR

    sentinel.trklocaladdr

    TRKPRODUCTNAME

    sentinel.trkproductname

    XFB.BufferSize

    sentinel.xfb.buffer_size

    XFB.Log (UNIX)

    sentinel.xfb.log

    XFBLOG (Windows)

    sentinel.xfb.log

    XFB.Sentinel

    sentinel.xfb.enable

    XFB.Trace

    sentinel.xfb.trace

    XFB.Transfer

    sentinel.xfb.transfer

  5. Load the Transfer CFT 3.6 environment.
  6. Import the selected UCONF parameters using the command CFTUTIL. Replace <script_filename> with the new script file path.
  7. CFTUTIL <prefix_character><script_filename>

    Example

    CFTUTIL @TRKAPI_IMP

Migrating COPCONF parameters

Migrate parameters from the Transfer CFT 2.4 COPCONF file.

  1. From the COPCONF file, select the parameters you want to import into version 3.6.
  1. Create a script file, for example: COP_IMP
  1. For each selected parameter add a UCONF command line in your new script file using the format:
  2. UCONFSET id=<parameter_id>, value=<value>
  3. Use the parameters mapping between copconf and UCONF as listed in the following table to specify the correct parameter id.
  4. Parameter mapping between copconf file and UCONF

    Parameter in copconf

    Parameter name in UCONF

    BatchList

    copilot.batches

    CFTCOM

    copilot.cft.com

    CFTMEDIACOM

    copilot.cft.mediacom

    ChildProcessTimeout

    copilot.misc.childprocesstimeout

    HttpRootDir

    copilot.http.httprootdir

    MinNbProcessReady

    copilot.misc.minnbprocessready

    NbProcessToStart

    copilot.misc.nbprocesstostart

    NBWAITCFTCATA

    copilot.cft.nbwaitcftcata

    ServerHost

    copilot.general.serverhost

    ServerPort

    copilot.general.serverport

    SslCertFile

    copilot.ssl.sslcertfile

    SslCertPassword

    copilot.ssl.sslcertpassword

    SslKeyFile

    copilot.ssl.sslkeyfile

    SslKeyPassword

    copilot.ssl.sslkeypassword

    TcpTimeout

    copilot.misc.tcptimeout

    TIMERWAITCFTCATA

    copilot.cft.timerwaitcftcata

    TrcMaxLen

    copilot.trace.trcmaxlen

    TrcType

    copilot.trace.trctype

    wlogComment

    copilot.batches.wlog.comment

    wlogParams

    copilot.batches.wlog.params

    WsiComplience

    copilot.webservices.wsicomplience

  5. Load the Transfer CFT 3.6 environment.
  6. Import the selected UCONF parameters using the command CFTUTIL. Replace the <script_filename> with the new script file path.
  7. CFTUTIL <prefix_character><script_filename>

    Example

    CFTUTIL @CFTPROD/COP_IMP

Migrating PKI certificates

You must be at Transfer CFT 2.4.1 SP5 or higher before performing this procedure.

  1. Load the Transfer CFT 2.4 environment.
  1. Export your PKI certificates using the PKIUTIL PKIEXT command:
  2. PKIUTIL PKIEXT fout=cftprod/pki_ext
  3. Load the new Transfer CFT 3.6 environment.
  4. Create a new PKI internal datafile using the command PKIUTIL PKIFILE. Replace <pki_database_filename> with the appropriate variable +CFTPKU.
  5. PKIUTIL PKIFILE fname=<pki_database_filename>, mode='CREATE’

  6. Import your PKI certificates into Transfer CFT 3.6 using the command PKIUTIL. Replace the <script_filename> with the new script file path.
  7. PKIUTIL <prefix_character><script_filename>

    Example

    PKIUTIUL @CFTPROD/pki_ext

Migrating the runtime environment

Migrating the catalog

  1. Load the Transfer CFT 2.4 environment.
  1. Export the catalog using the command CFTMI240:
  2. CFTMI240 MIGR type=CAT, direct=FROMCAT, ifname=<catalog_2.4_filename>, ofname=CFTPROD/cat_out

  3. Load the Transfer CFT 3.6 environment.
  4. Import the catalog using the command CFTMI. Replace the <catalog_filename_new_installation> with the corresponding environment variable:
  5. CFTMI MIGR type=CAT, direct=TOCAT, ifname=catalog_output.xml, ofname=<catalog_filename_new_installation>

Migrating the communication media files

  1. Load the Transfer CFT V2.4 environment.
  2. Export the communication media file using command CFTMI240:
  3. CFTMI230 MIGR type=COM, direct=FROMCOM, ifname=<com_2.3.2_filename>, ofname=CFTPROD/com_out

  4. Load Transfer CFT 3.6 environment.
  5. Import the communication media file using command CFTMI. Replace <com_filename_new_installation> with the corresponding environment variable +CFTCOM.
  6. CFTMI MIGR type=COM, direct=TOCOM, ifname=CFTPROD/com_out, ofname=<com_filename_new_installation>

Related Links