CA TCPaccess FTP Server Modernization Guide

CA TCPaccess FTP Server provided file transfer capabilities within the CA TCPaccess Communication Server environment. It enabled users and applications to transfer files to and from z/OS systems using the FTP protocol. The product was an application that addressed the need for reliable file transfer in mainframe environments.

This was an application, tightly integrated with the CA TCPaccess Communication Server. It provided FTP server functionality for z/OS systems. It was not a standalone system, tool set, framework, or middleware; it was a specific application designed for file transfer.

Organizations that relied on CA TCPaccess for their communication server needs and required FTP capabilities on z/OS used this product. These were typically larger enterprises, often in industries like banking, insurance, and government, that had significant mainframe infrastructure. Companies needing secure and reliable file transfer within their z/OS environment found it useful.

Companies should have considered CA TCPaccess FTP Server when they needed FTP functionality tightly integrated with their existing CA TCPaccess Communication Server on z/OS. It was a fit when organizations wanted to leverage their existing mainframe infrastructure for file transfer. However, with the product no longer supported, organizations should migrate to alternative solutions.

Alternatives include other FTP servers for z/OS, such as IBM FTP, or managed file transfer solutions like Axway Transfer CFT or Globalscape EFT. Open-source FTP servers running on Linux on Z may also be an option. These alternatives provide similar file transfer capabilities and may offer enhanced features or security.

CA TCPaccess FTP Server ran on the z/OS platform and required the CA TCPaccess Communication Server to be present. It operated within an LPAR on the mainframe. It was dependent on z/OS and utilized specific subsystems provided by the operating system. It extended the functionality of CA TCPaccess.

The product relied on standard FTP commands for file transfer operations. Common commands included `USER`, `PASS`, `GET`, `PUT`, `LS`, `CD`, and `QUIT`. Configuration was typically managed through configuration files specific to CA TCPaccess. The product integrated with z/OS security systems for user authentication and authorization.

The server likely used standard FTP ports (21 for control, 20 for data). It integrated with z/OS security systems such as RACF, ACF2, or Top Secret for authentication and authorization. It may have supported encryption protocols like SSL/TLS for secure file transfer.

The primary business value was providing a reliable and integrated FTP server within the existing CA TCPaccess environment. It allowed organizations to leverage their mainframe infrastructure for file transfer needs. However, given the product's end-of-life status, the current business value is minimal, and migration is necessary.

Without CA TCPaccess FTP Server, organizations would need to find alternative solutions for file transfer on z/OS. This could involve implementing a different FTP server, using managed file transfer solutions, or developing custom file transfer mechanisms. The impact would depend on the criticality of FTP-based file transfer to their business processes.

CA TCPaccess FTP Server integrated with z/OS security systems for authentication and authorization. It likely supported authentication methods provided by RACF, ACF2, or Top Secret. Access control was managed through these security systems, controlling which users could access specific files and directories. Encryption, if supported, used SSL/TLS.

The product leveraged z/OS security systems for auditing and logging. Security events, such as login attempts and file access, were logged by z/OS. These logs could be integrated with security information and event management (SIEM) systems for centralized monitoring and analysis.

Deployment involved configuring the CA TCPaccess Communication Server and the FTP server component on z/OS. Implementation required expertise in z/OS systems administration and security. Ongoing operational requirements included monitoring the FTP server for availability and performance, managing user accounts, and reviewing security logs.

Administrative interfaces were likely command-line based, using z/OS system commands and CA TCPaccess-specific utilities. User management was handled through z/OS security systems. Configuration parameters included settings for network ports, security options, and logging levels. Monitoring was performed using z/OS system monitoring tools.