Chapter 5. Installation 99
Draft Document for Review May 23, 2008 10:14 am 7645install.fm
example: log4j.logger.maximo.sql. Loggers form a hierarchy. A logger is
defined as an ancestor of another logger if its name followed by a dot is a
prefix of the descendant logger name. A logger becomes the parent of a child
logger if there are no ancestors between itself and the descendant logger. For
example, log4j.logger.maximo.sql is the parent of
log4j.logger.maximo.sql.WORKORDER. You can assign the following levels to
loggers:
–DEBUG
–INFO
–WARN
–ERROR
–FATAL
2. A level indicates a type of event that the system logs.
3. Appenders: You can send logging requests to multiple destinations. An output
destination is called an appender. Appenders can exist for consoles or files.
You can associate one or more loggers with a given appender. Alternatively,
you can associate a single logger with multiple appenders.
4. Layouts: A layout determines the output format of a log statement. A layout is
always associated with an appender. For example, a conversion pattern such
as %d{dd MMM yyyy HH:mm:ss:SSS} [%-2p] %m%n results in the following
log statement: 2007-05-07 14:07:41,508 [main] INFO MyApp - Entering
application.
The Logging application supports two types of loggers: Root and Child. One or
more child loggers always inherit from one root logger. In the Logging
application, a root logger is termed "root logger," while a child logger is termed
"logger."
This application can be used to:
Create loggers that are components in the product that prepare log
statements to be written to console or log file.
Associate the appropriate log level with each logger.
De-activate loggers except root loggers.
Configure appenders that represent a console or log files to which log
statements are written.
– Specify an appropriate file name for an appender.
– Specify a log file size for an appender.
– Associate a logger with multiple appenders.
– Associate an appender with multiple loggers.
To Next Page
Loading...