Logging Configurations
In log4j, a logger associates a runtime object with an appender, specifies the types of events to be logged, and whether to pass messages to a parent logger. In the Administrator web interface, a logger is referred to as a logging configuration.
A logger is an ancestor of another logger if its name followed by a dot is a prefix of the descendant logger name. A logger is a parent of a child logger if there are no ancestors between itself and the descendant logger. For example, com.tibco is a parent of com.tibco.silver. Each host, node, and application can have a logging configuration and each logging configuration has a root logger. The logging level is specified for each appender that belongs to a logger. This lets a logger to send logs to different destination with a different level. You can use the Administrator graphical and command-line interfaces to create loggers and appenders and to add appenders to existing loggers.
Default Logging Configurations
TIBCO ActiveMatrix nodes log at the WARN level by default. Node level configuration and application level configuration are independent. However, the node and application levels share a configuration when a root logger has not been configured for an application. It such a case, the application logging configuration shares the root logger configuration of the node where part or all the application components run.
To modify the default log configurations for a node, edit theCONFIG_HOME/admin/amxadmin/private/instanceName/DefaultLogConfiguration.properties file.
Basic and Advanced Mode
Logging configuration setting is available in two modes for hosts and nodes, basic and advanced. The advanced mode is available for an application when it is not selected to share the node level configuration.
In the basic mode for hosts and nodes, default log level settings for FileAppender and JmsAppender are available.