Investigating the logging and tracing output for the application
server is an excellent way to observe performance, diagnose problems,
and gain a general understanding of how the application server is
working within your environment. The expected output locations for
logging and trace information can be different depending on the operating
system on which the application server is running.
Note: 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.
Table 1. Log and trace
output for distributed and IBM i. This table lists the expected output for logging and tracing
output streams for distributed and IBM i
operating systemsLog or trace stream |
Expected output - basic log and trace mode |
Expected output - HPEL log and trace mode |
Java trace |
Trace.log. You must have tracing enabled. |
- HPEL trace repository.
- HPEL TextLog*.log, when you enable this log.
|
Java logs |
- Trace.log, when you enable tracing.
- Activity.log. The Activity.log file is also directed to the Showlog
output.
- SystemOut.log
|
- HPEL log repository
- HPEL TextLog*.log, when you enable this log.
|
System.out stream |
|
- HPEL log repository
- HPEL TextLog*.log, when you enable this log.
|
System.err stream |
SystemErr.log |
- HPEL log repository
- HPEL TextLog*.log, when you enable this log
|
cout (the C or C++ output stream) |
Native stdout |
Native stdout |
cerr (the C or C++ error stream) |
Native stderr |
Native stderr |
Figure 1. Distributed and IBM i
- Basic log and trace mode.
Distributed and IBM i - Basic log and trace mode
Figure 2. Distributed and IBM i - HPEL log and trace mode.
Distributed and IBM i - HPEL log and trace mode
Figure 3. z/OS - Traditional
log and trace mode.
z/OS -
Traditional log and trace mode
Figure 4. z/OS - HPEL log
and trace mode.
z/OS -
HPEL log and trace mode