WebSphere Application Server log files

WebSphere® Application Server uses a separate JVM for each application server, each node agent, and the deployment manager in your cluster environment. In a non-cluster setup, there is a separate JVM for each application server in the profile. Each JVM produces independent log output. The FFDC (First Failure Data Capture) facility in each JVM also produces output. Additionally, the HTTP server plug-in generates a log on each HTTP server where it is installed.

WebSphere Application Server on z/OS® uses the system log. On other platforms, log output is written to a set of log files for each JVM. The paths and names of the log files are configurable. The default locations are:

was_install_root/profiles/profile_name/logs/server_name/
was_install_root/profiles/profile_name/logs/ffdc/

where:

was_install_root: Installation directory of WebSphere Application Server on the machine, for example /local/WebSphere/V9R0CF/cftm51/w90c1nd/AppServer.
profile_name: Name of the application server profile, for example AppSrv01.
server_name: Name of the application server, for example server1.

The files in the logs/server_name directory have default names, see Application server log files and trace files for details. Due to log rotation, additional filenames with timestamps may be generated. The file names in the ffdc directory are generated with a timestamp and prefixed with server_name.

The default location for log output from the HTTP server plug-in is:

plugin_install_root/logs/web_server_name/http_plugin.log

where:

plugin_install_root: Installationg directory of the HTTP Server plug-in on the machine.
web_server_name: Name of the web server.