Table of Contents
Advertisement
Interpreting WebSphere Application Server log and trace messages
Messages and errors from the WebSphere Application Server console processes
display in the WebSphere Partner Gateway logs. Some of these messages might
appear to be errors, but they are informational and do not pose a problem for the
WebSphere Partner Gateway application. The level value is set from configuration
data when the logger is created and can be changed at run time from the
administrative console. Use the following information to interpret the WebSphere
Application Server messages you might encounter in your system output logs.
WebSphere Application Server event types
A one character field that indicates the type of the message or trace event. Message
types are in upper case. Possible values include:
F
E
W
A
I
C
D
O
R
Z
Integrated FTP Server logging
This section describes the integration of success and failure event messages for the
FTP Server actions. When WebSphere Partner Gateway Partner intends to send a
document to WebSphere Partner Gateway Integrated FTP server, Integrated FTP
server produces a client connect notification event. The appropriate connection
event message is logged into WebSphere Partner Gateway database after
examining the FTP server response codes.
Success and failure event messages for FTP Server actions
The event messages produced by the FTP Server for various actions such as
establishing connection, user login, file upload, file download and disconnect are
logged as events in WebSphere Partner Gateway database. These events can be
viewed from WebSphere Partner Gateway console using the existing event viewer.
The possible response codes for connect event are:
v 220 Service ready for new user.
v 530 No server access from the IP.
v 530 Maximum number of server connections has been reached.
After the connection is established, the user information is authenticated. After
user authentication is performed, FTP Server produces a client login notification
146
IBM WebSphere Partner Gateway Enterprise and Advanced Editions: Administration Guide
A fatal message
A error message
A warning message
A audit message
A informational message
A configuration message
A detail message
A message that was written directly to SystemOut.log by the user
application or internal components.
A message that was written directly to SystemErr.log by the user
application or internal components.
A placeholder to indicate that the type was not recognized.
Advertisement
Table of Contents
