WAS v8.5 > Reference > Log and trace file descriptionsLog and trace settings page
Use this page to configure logging and trace settings for the server.
We can only access this page when the server is configured to use basic log and trace mode.
To view this dmgr console page, click...
Troubleshooting | Logs and trace | server_name
IBM recommends using the HPEL log and trace infrastructure. With HPEL, one views logs using the LogViewer command-line tool in PROFILE/bin.
Switch to HPEL Mode
Use the Switch to HPEL Mode button to change the log and trace mode for the server to HPEL.
Switching the server to HPEL log and trace mode requires a server restart.
Diagnostic Trace
Set the the initial trace state for a server process. Settings are read at server startup. Some trace service properties can be changed while the server process is running.
JVM Logs
The JVM logs are created by redirecting the System.out and System.err streams of the JVM to independent log files. WAS writes formatted messages to the System.out stream. In addition, applications and other code can write to these streams using the print() and println() methods defined by the streams.
Process Logs
WAS processes contain two output streams that are accessible to native code running in the process. These streams are the stdout and stderr streams. Native code, including JVMs, might write data to these process streams. In addition, JVM provided System.out and System.err streams can be configured to write their data to these streams also.
IBM Service Logs
The IBM service log contains both the WAS messages that are written to the System.out stream and some special messages containing extended service information that is normally not of interest, but can be important when analyzing problems. There is one service log for all WAS JVMs on a node, including all application servers.
Change Log Level Details
Enter a log detail level that specifies the components, packages, or groups to trace. The log detail level string must conform to the specific grammar described in this topic. We can enter the log detail level string directly, or generate it using the graphical trace interface.
NCSA access and HTTP error logging
The NCSA access and HTTP error logging page enables you to configure the log settings for the HTTP server.
Related
Use basic or traditional message logs
Troubleshoot applications with HPEL