Network Deployment (Distributed operating systems), v8.0 > Reference > Log and trace file descriptions
Log and trace settings
Use this page to view and 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 admin console page, click:
- Troubleshoot > Logs and trace > server_name
With WAS v8 you can configure the server to use the HPEL log and trace infrastructure instead of using SystemOut.log , SystemErr.log, trace.log, and activity.log files or native z/OS logging facilities. If you are using HPEL, you can access all of your log and trace information using $PROFILE/bin/LogViewer.sh.
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
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. We 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 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 Java virtual machines (JVM), might write data to these process streams. In addition, JVM provided 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 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 WAS 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 and Trace Analyzer, provides additional diagnostic capabilities. In addition, the binary format provides capabilities that are utilized by IBM support organizations.
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 your HTTP server.
Diagnosing problems with message logs
Use HPEL to troubleshoot applications