Transfer CFT 3.2.2 Release Notes

New features and enhancements

Major evolutions

  • Added support for TLS 1.1 and 1.2. The OpenSSL library replaces Transfer CFT's internal proprietary SSL library. Backward compatibility is available as of 3.1.3 SP6, and 3.0.1 SP11 (not yet released as of this publication date), you may incur issues when using a mix of version if you do not upgrade to these versions.

    CAUTION
    Due to a TLS 1.2 compatibility issue, you cannot use the cipher suites 59, 60, and 61 between Transfer CFT 3.2.2 and Transfer CFT 3.1.3 SP5 or lower.

  • Added support for new TLS cipher suites.
  • Added support for Perfect Forward Secrecy.
  • Added a new parameter FILENOTFOUND for the CFTSEND and CFTRECV objects and the SEND and RECV.
  • Dynamically add, remove, enable, or disable a logical folder to monitor in the Transfer CFT runtime.
  • Added a new parameter, SERIAL, for the SEND/RECV and CFTSEND/CFTRECV commands that enables file transfer serialization in a flow definition.
  • Replaced Copilot applet UI with Java Web Start technology.
  • Added a reusable deployment package feature (new JCLs) for installing or applying Service Packs/patches to Transfer CFT in a z/OS environment.

Minor evolutions and enhancements

  • Added log output for rotation (backup) files when using LISTLOG.
  • Added new SERIALIZED parameter to filter the displayed transfer records.
  • Documented symbolic variable used to reconstitute a filename on reception.
  • Added CFTUTIL autocomplete command feature for UNIX/Windows.
  • Delivered a spoolout sample.
  • For IBM i, now process outputs (QPRINTS) are redirected to the following files in the production library: the CFTOUT file for Transfer CFT, and the COPOUT file for COPILOT. Additionally, process joblogs (QPJOBLOG) are redirected to the following files in the production library: JLOG and JLOG2 files for Transfer CFT, and the COPJLOG and COPJLOG2 files for Copilot.
  • Added support for the pre, post, and ack processing states to the Transfer JPI.
  • Added new parameters SY and RY, and UCONF parameters cft.purge.sy and cft.purge.ry, to automatically purge transfers in the Y (post-processing phase) state.
  • Added the CFTSUPPORT command in IBM i environments.
  • Added new parameters WPHASESTEPS and WPHASE for the SEND/RECV commands.
  • Added the RENAME option to the FACTION parameter, which replaces the existing FNAME file after the transfer completes with the WFNAME.
  • PKI exits available on all platforms.

Platform features

This table lists supported product features according to platform.

Functionality   Operating System
Windows Unix z/OS IBM i OpenVMS
Central Governance X X X X  
SP and patch deployment via Central Governance X X      
Multi-node architecture X X X * X
Secure Relay X X X X  
FIPS X X      
IPv6 X X X X X
pTCP X X      
UDT X **      
SOCKS X X X X X
TrustedFile (PGP S-MIME CMS) *** X X    

Enabled for the following platforms:

* Only one host

** Only applies to Linux-x86-32, Linux-x86-64, Linux-ia64 (64 bit)

*** Only applies to Windows-x86-32

 

Supported file systems for multi-node architecture

The following non-exhaustive table lists shared file systems that have been tested with Transfer CFT.

Operating system Tested and supported Not supported
AIX GPFS (recommended), NFSv4 NFSv3, CXFS, VeritasSF
HP-UX NFSv4 NFSv3, CXFS, VeritasSF
Linux-x86 GPFS (recommended), NFSv4 NFSv3, CXFS, ACFS, OCFSv1, OCFSv2, QFS, VeritasSF
OpenVMS RMS  
Solaris NFSv4 NFSv3, CXFS, QFS, VeritasSF
Windows-x86 CIFS CXFS, NFS
z/OS Sharing DASD across Sysplex  

Limitations

  • TLS renegotiation is not supported.
  • Transfer CFT no longer supports the XHTTPS protocol for synchronous communication.

Prerequisites

Windows

When using a Windows x86 (32-bit) or (64-bit) system, you must install the Visual C++ Redistributable Package for Visual Studio 2013 to provide necessary library files (DLL) for the compiler:

  • For a win-x86-32 target use: vcredist_x86.exe
  • For a win-x86-64 target use: vcredist_x64.exe

To download the redistribution package, visit: Visual C++ Redistributable Packages for Visual Studio 2013

Note   If the redistribution package is already installed on your Windows system, there is no need to reinstall.

Java support

You require Java version 7 or higher as a client to use the Copilot UI.

Upgrade procedure

As of version 3.1.3 Transfer CFT benefits from a CUP (Composite Update Package), which includes both the installer and product upgrades, easing the process of upgrading your environment.

Additionally, as of 3.1.3 you can also use Central Governance to upgrade your Transfer CFTs.

Discontinued support

Changing technologies as well as evolution in our customers systems, drives the need for Axway to modify or discontinue support for some features. The following list summarizes discontinued functions that have been announced for Transfer CFT.

Discontinued platforms

The following platforms were previously supported in Transfer CFT 3.1.3; however, support is discontinued in Transfer CFT 3.2.2:

  • HP‐UX 11iV1 (11.11) parisc‐32, parisc‐64
  • HP‐UX 11iV2 (11.23) parisc‐32, parisc‐64, ia64‐64
  • SUSE Linux Enterprise Server 10 x86‐64 (64-operating system)
  • Windows Server 2003 x86‐32, x86‐64, ia64‐64
  • Windows XP x86‐32, x86‐64
  • Windows Vista x86‐32, x86‐64
  • Red Hat Enterprise Linux 4 x86‐32, x86‐64, ia64‐64
  • IBM i (OS/400) 6.1
  • Z/OS (MVS) 1.12

For a comprehensive list of supported platforms for Transfer CFT, please refer to the Axway Supported Platforms guide available on Axway Support at https://support.axway.com.

Discontinued in Transfer CFT 3.0.1

Functionality

  • VFM

Interoperability

  • Composer for Transfer CFT
  • Transfer CFT Navigator

Networks and protocols

  • Networks: LU62, SNA, DSA, X.25, and DNA
  • Protocol: ETEBAC

Discontinued in Transfer CFT 3.1.3 z/OS [MVS]

Functionality

  • API CICS
  • Transfer CFT z/OS no longer uses the SAS/C compiler. This results in the removal of interfaces specifically used by the SAS/C objects, such as the USERAPI module. Therefore, Transfer CFT API access is now done via a call to the DLL. Consequently, this constraint requires a slight modification to the source code; for example, you must use a Language Environment (LE) conforming Assembler.
    To assist users in understanding and implementing, EXIT and API samples in Assembler, C, and COBOL are delivered with Transfer CFT version 2.7.x and higher.

Documentation

This section describes documentation enhancements and related documentation.

Documentation enhancements

Reorganized the Concepts section and added a Manage transfers section.

Related documentation

For more information about Transfer CFT and how it is used in Axway, refer to:

  • Axway Supported Platforms
  • Axway Interoperability Matrix
  • Transfer CFT 3.2.2 User Guide
  • Transfer CFT 3.2.2 Local Administration Guide
  • Transfer CFT 3.2.2 UNIX Installation Guide
  • Transfer CFT 3.2.2 Windows Installation Guide
  • Transfer CFT 3.2.2 z/OS Installation and Operation Guide
  • Transfer CFT 3.2.2 IBM i Installation and Operation Guide
  • Transfer CFT 3.2.2 VMS Installation and Operation Guide

Support services

The Axway Global Support team provides worldwide 24 x 7 support for customers with active support agreements.
Email support@axway.com or visit Axway Support at https://support.axway.com.

Copyright © 2016 Axway. All rights reserved

Related Links