Getting Started with WebSphere Application Server

Chapter 11 – Troubleshooting 201
The server-log4j.properties file can also be edited from the admin console by selecting the
Server Logs portlet. With the admin console, you can also filter the server.log entries.
In Linux, AIX, or Solaris users can use the tail -f server.log command to display
current entries to the server.log file while the server is running.
11.5.3 Client log
Messages from Java EE client applications are written to the file
/var/log/client.log. Similar to server.log, you can change the
file location, name and the log levels by editing the /var/log/clientlog4j.properties.
11.5.4 Deployer log
Messages are generated when an application is deployed to a server. These messages
are logged to the /var/log/deployer.log file. You can change the
file location, name and the log levels in /var/log/deployerlog4j.properties.
11.5.5 Web log
HTTP requests to the Web container are logged. The HTTP request information includes
the type of request (GET or POST), the time of access, and other related data. You can
see the access log files in the /var/catalina/logs folder. The file
name has the format:
_access_log..txt
For example, 0.0.0.0_access_log.2010-06-29.txt, records all the access
information on 2010.06.29 from every client.
From the admin console you can review and edit the Web server log file and edit its
properties by selecting Server Logs -> Web Access Log Viewer. With the admin console,
you can use a filter to narrow down log entries.
11.5.6 DB2 database log
DB2 database log files include information about the DB2 database server, such as
database startup and shutdown information. There are two main logs:
• DB2 Administration Notification log
• db2diag.log