Log and trace settings

Use this page to view and configure logging and trace settings for the server.

Supported configurations: You can only access this page when the server is configured to use basic log and trace mode.

To view this administrative console page, click Troubleshooting > Logs and trace > server_name .

Note: You can configure tracing from the MVS™ console using the modify command.

Tip: This topic references one or more of the application server log files. As a recommended alternative, you can configure the server to use the High Performance Extensible Logging (HPEL) log and trace infrastructure instead of using SystemOut.log , SystemErr.log, trace.log, and activity.log files on distributed and IBM® i systems. You can also use HPEL in conjunction with your native z/OS® logging facilities. If you are using HPEL, you can access all of your log and trace information using the LogViewer command-line tool from your server profile bin directory. See the information about using HPEL to troubleshoot applications for more information on using HPEL.

Switch to HPEL Mode

Use the Switch to HPEL Mode button to change the log and trace mode for the server to HPEL.

Note: Switching the server to HPEL log and trace mode requires a server restart.

Diagnostic Trace

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.

Java virtual machine (JVM) Logs

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.

Process Logs

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.

IBM Service Logs

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.

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. You 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 your HTTP server.

Change log and trace mode

Specifies to switch between HPEL mode or Basic mode logging.

Note: Switching the server to HPEL log and trace mode requires a server restart.