Owner's manual

1. This is a properties file with name value pairs with = as the separator.
2. A key with the name loggers defines all loggers that are configured.
For example, loggers = com.hp.nonstop.sample, org.jboss.as.ejb3. Where,
these two are two different loggers with log categories as com.hp.nonstop.sample and
org.jboss.as.ejb3.
3. A key with the name handlers defines all handlers.
a. It is not mandatory to define all the handlers with a handlers key.
b. A handler when associated with a logger gets automatically defined.
It is not mandatory to define all the handlers with a handlers key.
A handler gets automatically defined when it is associated with a logger.
4. A key with name filters defines all the filters present in the configuration file.
It is not mandatory.
A filter gets automatically defined when it is associated with either a logger or a handler.
5. A key with name formatters.
It is not mandatory.
A formatter gets automatically defined when associated with a handler.
6. A key with name errorManagers.
It is not mandatory.
7. The logger configuration is of the format logger.<log
category>.<attribute>=<value>. The following are the attributes:
level attribute defines the log level. This is a string value which indicates the log level.
For example, logger.org.jboss.as.ejb3.level=INFO.
filter attribute defines the filter expression that needs to be applied to this logger. See
filter expressions for more details. If the value is not a filter expression, then it can be a
named filter too.
8. handlers attribute defines a comma separated list of handlers for this logger. For example,
logger.org.jboss.as.ejb3.handlers=CONSOLE, FILE.
9. The handler configuration is always of the format handler.<handler
name>.<attribute>=value. The following are the attributes:
null attribute, where the value is a fully qualified name of the class that extends the
java.util.logging.Handler class. For example,
handler.CONSOLE=org.jboss.logmanager.handlers.ConsoleHandler.
module attribute, where the handler is in a module other than the JBoss log manager’s
module and hence, the name of the module needs to be mentioned. For example,
handler.CUSTOM.module=com.hp.nsk.utils.
constructorProperties attribute is a comma separated list of property names that
are to be used to construct the handler.
filter attribute is the filter expression that needs to be applied to this handler. If the
value is not a filter expression, then the value can be a named filter too.
level attribute defines the logging level for the handler.
formatter attribute defines the formatter to use for the handler.
78 Configuring NSASJ