Client Documentation
2.1. Operating System and Requirements¶
2.1.1. Supported Operating Systems¶
The SFTPPlus Client is distributed as a ZIP file for Windows systems and a TAR GZ archive for Unix and GNU/Linux system.
A different archive is available for each supported operating system and CPU architecture type.
Below is the list with supported operating system and CPU types:
- Windows 2003 Server, Windows 7, Windows 2008 Server, Windows 2008 Server R2 full support on X86 and X86_64
- Ubuntu Linux 10.04 and 12.04 LTS on X86
- SuSe Enterprise Linux on X86
- Solaris 10 on X86
- Solaris 10 on Sparc64
- Red Hat Enterprise Linux 4 on PowerPC64
- Red Hat Enterprise Linux 4, 5, 6 on Intel X86
- HP-UX 11i3 and above running on Itanium and Itanium2
- AIX version 5.3, 6.1, 7.1 and newer running on both 32bit and 64bit versions
Virtual environments and virtual machines are supported for all platforms, including: VMWare ESX, Virtualbox, OpenVZ, Docker, WPAR, vWPAR, zones, etc
SFTPPlus Client does not include cluster aware logic, but it provides generic functionalities for implementing clustering.
We have customers deploying SFTPPlus Client resilience configuration on MSCS, RedHat Linux or IBM AIX clusters.
On MSCS the SFTPPlus Client can be deployed as a Generic Service Resource or a Generic Script Resource.
2.1.2. Software Requirements¶
On Microsoft Windows, the OpenSSL and cURL libraries are distributed together with the installation package and there are no 3rd party dependencies.
A recent version of OpenSSL and cURL libraries are required on Unix and Linux system.
On Unix and GNU/Linux system, the system OpenSSL and cURL libraries are used, and SFTPPlus Client depend on these 3rd party libraries being installed on the system
2.1.3. Hardware Requirements¶
| CPU: | The client will run on any CPU released in the last 10 years. Since many of the encryption / decryption operations are CPU-intensive operations, it is recommended to use a modern CPU. |
|---|---|
| Memory: | Between 10 - 30 MB of RAM, depending of CPU architecture. Client operates in a single thread model and memory and CPU usage will remain constant regarding the number of active transfers. |
| Disk usage: | Installation size 10 - 50 MB. |
| Network usage: | The server will try to use all available network bandwidth. This is normal for Ethernet/IP networks. Many of the cryptographic algorithms require a low network latency, and network delay should not be larger than 60 seconds. |