Table of Contents
Advertisement
event. The appropriate login event message is logged into WebSphere Partner
Gateway database. The possible response codes for user authentication are:
v 501 Syntax errors in parameters or arguments
v 503 Login with USER first.
v 202 Already logged-in
v 21 Maximum number of anonymous login has been reached.
v 421 Maximum number of login has been reached.
v 230 User logged in, proceed
After the user login is successful, Partner FTP Sender attempts to put the
document to the FTP Server. Once the file is uploaded, FTP Server produces an
upload end notification event. The possible response codes for upload start event
are:
v 150 File status okay; about to open data connection.
v 226 Transfer complete.
v 550 Invalid paths.
v 550 Permission denied.
v 425 Can't open data connection.
v 426 Data connection error.
v 551 Error on output file.
Once the document is successfully uploaded to the FTP Location, the FTP
connection is disconnected. FTP server produces a disconnect notification event.
This event is logged into WebSphere Partner Gateway database.
Logging and exception information related to Integrated FTP Server
The FTP server code internally produces logging and exception information. This
information is available in the log files generated on the system where the FTP
Server is installed. These log files are checked and analyzed separately to obtain
details on any error or debug information. The log file format is similar to the
formats used by other components of WebSphere Partner Gateway.
147
Chapter 14. Using logging and tracing features
Advertisement
Table of Contents
