An optional SAS Micro
Analytic Service start-up parameter specifies the location of an XML
logging configuration file, which controls the logging levels and
the location of the log file or files. SAS Micro Analytic Service
uses the SAS 9.4 Logging Facility. For more information, see SAS
9.4 Logging: Configuration and Programming Reference.
Your SAS solution might provide
a default logging configuration file, and that file might include
loggers or appenders in addition to those described in this chapter.
For example, on UNIX the file might be /data1/SAS/config/Lev1/Web/Common/LogConfig/SASMicroAnalyticService-log4sas.xml.
For more information, see your solution’s documentation.
SAS Micro Analytic Service
uses two loggers named App.tk.MAS and App.tk.MAS.CodeGen. Code that
is hosted by SAS Micro Analytic Service, or the functions that it
calls, can use additional loggers.
The logger App.tk.MAS
is used for logging all aspects of SAS Micro Analytic Service operation
besides code compilation and code generation, which use App.tk.MAS.CodeGen.
Normal operations, such as start-up and shutdown, are logged at the
INFO level. Detailed
information about such operations as compilation start and finish,
and others, are logged at the DEBUG level. Warning and error conditions
are logged at the WARN or ERROR levels, as appropriate. By default,
App.tk.MAS is set to the INFO level.
App.tk.MAS.CodeGen is
used for logging compiler-generated messages, such as compilation
warnings and errors. Compiler messages can also be retrieved programmatically
through the Java and REST interfaces. (See getCompilationMessages
in
Method Descriptions.) Your SAS solution might report
compilation messages automatically. Because these messages are available
programmatically, and to prevent compiler messages from cluttering
the log, App.tk.MAS.CodeGen is set to the FATAL logging level by default.