Beginning
with SAS 9.3, the SAS Web Infrastructure Platform has implemented
a framework for providing separate logging contexts for the individual
SAS Web applications. Web application servers have a property defined
on their command line (com.sas.log.config.url) that points to the
directory where the log4j configuration files are located.
For SAS BI Portlets,
the
SASBIPortlets-log4j file is located
in the
SAS-Configuration-Directory\Levn\Web\Common\LogConfig directory.
Message logging is accomplished
by adding an appender section in the appropriate log4j file. A logging
context is the fully qualified class name of the class where the logging
message originated, and it is specific to SAS BI portlets.
A log can be set at
five different levels of detail: DEBUG, INFO, WARN, ERROR, and FATAL.
The default for the logging contexts is set to WARN, which means that
only WARN, ERROR, and FATAL messages are recorded. In large-scale
deployments, the size of the log file can grow rapidly when INFO messages
are enabled. However, you might want to enable INFO messages during
development and testing phases.
Every logging context
can have outputs associated with it. As a result, different log messages
might go to different locations. By default, all portal log messages
go to both the application server console and the log file.
The logging output is
stored in the application’s log file that is located at the
SAS-configuration-directory\Lev1\Web\Logs directory.