Use this page to view and configure logging and trace settings for the server. To view this administrative console page, click the following paths:
Troubleshooting > Logs and Trace > server_name
The diagnostic trace configuration settings for a server process determine the initial trace state for a server process. The configuration settings are read at server startup and used to configure the trace service. You can also change many of the trace service properties or settings while the server process is running.
The JVM logs are created by redirecting the System.out and System.err streams of the JVM to independent log files. WebSphere Application Server 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.
WebSphere Application Server 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 Java virtual machines (JVM), 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.
The IBM service log contains both the WebSphere Application Server messages that are written to the System.out stream and some special messages that contain extended service information that is normally not of interest, but can be important when analyzing problems. There is one service log for all WebSphere Application Server JVMs on a node, including all application servers. The IBM Service log is maintained in a binary format and requires a special tool to view. This viewer, the Log Analyzer, provides additional diagnostic capabilities. In addition, the binary format provides capabilities that are utilized by IBM support organizations.
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. You can enter the log detail level string directly, or generate it using the graphical trace interface.
Searchable topic ID: utrb_logtrace