When I turned the logging level to “Yes”, and ran the same process, 1572 lines were added to my ftpclient.log! With the ftpclient.log set to “Logging Level” of “No”, or error-only mode, nothing was added to the log, because there weren’t any errors. It does an FTP Client List Service, then it disconnects. It has an FTP Client Begin Session Service which logs in to “oxnard” using port “4299”, userid “admin” and password “password”.

I ran a very simple FTP business process. The logging for it is kept in the ftpclient.log. In Sterling B2B Integrator, if you are initiating a connection with FTP, you are using the FTP Client Adapter. This blog has two sections “Successful FTP Client Connection:” and “Unsuccessful FTP Client Connection:” There are a lot of options and parameters in an FTP transfer. (There are others, too…) It also has passive and binary options for how SSL/TLS security is handled. For example, the type option itself has two common parameters, ASCII or type A, BINARY or type B. It has dozens of command options, and several places where different types of data are specified. This protocol is one of the oldest ways in the computer industry for transferring data between two systems.

Let’s talk about the logs that are used for FTP. This blog is part of a series in which I am conducting swimming lessons to help Sterling B2B Integrator users to make use of the sea of information that is stored in some of our logs.

Filezilla log file analyzer