See the Javadocs in <EPM_ORACLE_HOME>/common/docs/ReportingAnalysis/SDK/javadoc.
This class provides methods to enable clients to log their messages using ODL logging architecture. The client acquires a LoggerHelper artifact instance in every source file in which it wants to log messages. The client uses the static getLogger() method that takes a class name (String or Class artifact) as a parameter. Usually, this class is the fully qualified source file name.
The installer creates two directories:
<MIDDLEWARE_HOME>/user_projects/epmsystem1/diagnostics/logs/ReportingAnalysis/SDK—Log files generated by the ODL model.
<MIDDLEWARE_HOME>/user_projects/epmsystem1/config/ReportingAnalysis/SDK—XML configuration file for the ODL model. The configuration file name is logging.xml. Set the configuration file and the LoggingConfiguration.class as JAVA properties:
Djava.util.logging.config.class=oracle.core.ojdl.logging.LoggingConfiguration
Doracle.core.ojdl.logging.config.file=<MIDDLEWARE_HOME>/user_projects/epmsystem1/config/ReportingAnalysis/SDK/logging.xml
The configuration file contains sdk_file_handler. in which the following properties can be changed:
path—Full path of the file where log messages are written. The default path is <MIDDLEWARE_HOME>/user_projects/epmsystem1/diagnostics/logs/ReportingAnalysis/SDK/sdk.log
maxFileSize—Maximum log file size. If the file exceeds this limit, it is renamed and a new log file is created.
The log level is configured by setting the level attribute of logger element. By default the log level is set to WARNING:1.
Table 1. Log Levels
| ODL Log Level | ODL Description |
|---|---|
| INTERNAL_ERROR:1 | The program has experienced an error for some internal or unexpected non-recoverable exception. |
| ERROR:1 | A problem requiring attention from the system administrator has occurred. |
| WARNING:1 | An action occurred or a condition was discovered that should be reviewed and may require action before an error occurs. |
| NOTIFICATION:1 | A report of a normal action or event. This could be a user operation, such as "login completed" or an automatic operation such as a log file rotation. |
| NOTIFICATION:16 | A configuration-related message or problem. |
| TRACE:1 | A trace or debug message used for debugging or performance monitoring. Typically contains detailed event data. |
| TRACE:16 | A fairly detailed trace or debug message. |
| TRACE:32 | A highly detailed trace or debug message. |
The following logging configuration file entities are used to write log files:
sdk_file_handler—Writes log messages in a file located in <MIDDLEWARE_HOME>/user_projects/epmsystem1/diagnostics/logs/ReportingAnalysis/SDK. You can change this location in the path property of the handler.
Declaration:
<log_handler name="sdk_file_handler" class="oracle.core.ojdl.logging.ODLHandlerFactory"> ... </log_handler>
oracle.EPMSDK.com.sqribe.rm—Writes log messages to the file specified in the path property of sdk_file_handler. Default log level is WARNING:1. You can change the default if desired.
Declaration:
<logger name="oracle.EPMSDK.com.sqribe.rm" level="WARNING:1" useParentHandlers="false"> ... </logger>