FTP is the protocol of choice to send data over the Internet. A wide range of command lines and GUI clients are available. Most operating systems install an FTP client by default. A plain FTP server is still available but will be discontinued for upload other than using the Java utility or the z/OS utility on 5 October 2020. We strongly recommend using the new server enforcing encryption. After disabling of plain FTP, only FTPS (FTP over TLS) and SFTP (FTP over SSH) will be supported for manual uploads. The two upload utilities (Java utility - SDDUU and z/OS utility - PDUU) will still be able to upload data to ftp.ecurep.ibm.com, testcase.boulder.ibm.com and ftp.ap.ecurep.ibm.com.
On 5 October 2020 we will disable cipher suites that use SHA-1 hashing algorithms. Make sure that your FTP client is supporting current encryption options.
All secure FTP servers enforce authentication. An IBM Support File Transfer ID is required to use these servers.
FTPS instructions (FTP over TLS)
FTP is the protocol of choice to send data over the Internet. A wide range of command lines and GUI clients are available. Most operating systems have an FTP client installed by default. ECuRep does only support FTPS (explicit) to meet legal requirements. Transfers should always use "binary" mode to make sure that file integrity is kept. You should consider the use of "passive" mode (port range 65024 - 65535) to avoid connection issues.
For a certain period, anonymous FTP uploads using tools that enforce encryption of the content, will be supported. In order to use this, your FTP client must support TLS and your firewall must be transparent for secure FTP.
Note: Please use the server closest to your physical location.
Please notice, that testcase.boulder.ibm.com leverages RFC4217 DRAFT level, ftps.ecurep.ibm.com and ftps.ap.ecurep.ibm.com leverages full RFC4217 level, which differs in sub commands AUTH and CCC) For z/OS FTPS implementation, please refer to information in our Help - FTP section.
Information about the encryption use can be found in the "Encryption" tab.
For additional information regarding certificates and IBM ID and Transfer ID usage, please refer to FAQs About GDPR-related Changes to ECuRep and Testcase FTP File Uploads.
If the upload to one of the servers is failing, please try uploading to another server.
Active versus passive transfer mode
The FTP protocol supports two transfer modes: active and passive. Both are supported by the ECuRep FTP server. The active mode is the default for many FTP clients. If you encounter problems after logging on to the ECuRep's FTP server, try to switch to the passive mode. This is needed because most corporate firewall policies only allow the use of the passive mode. If your client does not support the passive mode, please use another client. If you are in doubt, try a ls command right after login. If nothing is returned and a timeout occurs passive FTP is required. All three upload servers are using the port range 65024 - 65535 for data connections.
ASCII versus binary transfer mode
One of the least-understood aspects of FTP transfers is the difference between ASCII and binary mode data transfers. ASCII stands for American Standard Code for Information Interchange, and is a type of character encoding based on the English language used on devices that handle information stored in text. It includes 33 non-printed control characters and 94 printed characters such as letters and punctuation.
When files are transferred in ASCII mode, the transferred data is considered to contain only ASCII formatted text. The party that is receiving the transferred data is responsible for translating the format of the received text to one that is compatible with their operating system. The most common example of how this is applied pertains to the way Windows and UNIX handle newlines. On a Windows computer, pressing the "enter" key inserts two characters in an ASCII text document - a carriage return (which places the cursor at the beginning of the line) and a line feed (which places the cursor on the line below the current one). On UNIX systems, only a line feed is used. ASCII text formatted for use on UNIX systems does not display properly when viewed on a Windows system and vice versa.
Binary mode refers to transferring files as a binary stream of data. Where ASCII mode may use special control characters to format data, binary mode transmits the raw bytes of the file being transferred. In binary mode, the file is transferred in its exact original form.
For our FTP server transfer must be done in binary mode.
Upload (toibm) directories
On each server there are different upload directories organized in two levels. To upload data you need to change to "toibm", choose the sub directory matching your product best like "websphere" and change to that directory. Data uploads are only possible in these directories. Uploads to the first level "toibm" are not possible. The upload directories have 'write only' permissions which means that they cannot be listed. Some graphical clients do not allow changing to these directories but you can still drag & drop data to the directory.
To help you use our FTP server, we provide several operating system-specific descriptions. For more information, please go to the description of your operating system.
SFTP instructions (secure)
Secure FTP over SSH is based on the Secure Shell protocol. In contrast to standard FTP, only one port is used for session handling and data transfer. Therefore, the implementation is firewall-friendly.
In general, the directory structure of the SFTP server is the same as on the standard FTP server except that only the toibm directory is available.
Note: Please use the server closest to your physical location.
|Asia||sftp.ap.ecurep.ibm.com (220.127.116.11, 18.104.22.168)|
We have successfully tested different implementations of SFTP clients. The tests included command line and GUI clients. Some Windows FTP clients support FTP, FTPS and SFTP. Please have a look at the documentation of your client. If you have problems configuring secure FTP on your system, contact your local support or the provider of your FTP client. Secure Copy is not supported.
07 August 2020