Log formatters format log messages so they can be used
by various log handlers.
Handlers can be configured with a log formatter that knows how
to format log records. The event, which is represented by the log
record object, is passed to the appropriate formatter by the handler.
The formatter returns formatted output to the handler, which writes
the output to the output device.
The formatter is responsible for rendering the event for output.
This formatter uses the resource bundle that is specified in the
event to look up the message in the appropriate language.
Formatters are attached to handlers using the setFormatter method.
With WebSphere
® Application Server,
you can configure the formatter to work with trace, the
SystemOut.log, and the
SystemErr.log log files:
- Basic (Compatible): Preserves only basic trace information.
With this option, you can minimize the amount of space taken by the
trace output.
- Advanced: Preserves more specific trace information. You
can see detailed trace information for troubleshooting and problem
determination.
- Log analyzer trace format: Preserves trace information
in the same format as produced by Showlog tool.
You can select a formatter for a handler
using the administrative console panels. See Diagnostic trace service
settings for details.
You can find the java.util.logging documentation at http://java.sun.com/javase/.
New feature: This topic
references one or more of the application server log files. Beginning
in WebSphere Application Server Version 8.0 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 or 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.
newfeat