Logging for SAS Information Delivery Portal

Configuring Logging for SAS Information Delivery Portal

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. The logging service that was previously available in SAS Management Console has been deprecated.
For SAS Information Delivery Portal 4.31, the SASPortal-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 SASPortal-log4j file, and specifying a logging context. A logging context is the fully qualified class name of the class where the logging message originated. The following logging contexts are specific to the SAS Information Delivery Portal:
  • com.sas.portal
  • com.sas.webapp
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 a log file. The logging output for the portal is stored in the SASPortal4.3.log file located at the SAS-configuration-directory\Lev1\Web\Logs directory.
For more information about logging as it applies to SAS applications, see the SAS Intelligence Platform: Middle-Tier Administration Guide. For information about the log4j configuration file, see http://logging.apache.org/log4j/index.html.