A.5.4 Configurable Logging Properties

The following table identifies the configurable properties for logging in an Oracle client’s environment.

Table A-3 Configurable Parameters for Common Logging

Property	SampleValue	Description
log.format	%d[%t] %p %m%n	Identifies the log formatting string. See ApacheSoftware’s ShortIntroduction to log4j guide(http://logging.apache.org/log4j/docs/ manual.html) for more details about the log message format.
log.message.library	Tobe specified at installation.	Identifiesthe full path and filename of the message library.
log.max.size	2000000000	Determines the maximum size (in bytes)of a log file before the system creates a new log file. For more information (See LogFile Sizes for more information).
log.category.<catgory_name>.locati on		Contains routing information for messagelibraries for this category. For more information (See Logging Location Property Values for more information).
log.categories.file.path	Tobe specified at installation.	Identifies the full path to the categories.cfg file.
log.<category_name>.<severity>.lo cation		Contains routing information for message libraries with the given severity for the given category. For more information (See Logging Location Property Values for more information).
log4j.config.file	Tobe specified at installation.	Specifies the full path to the external log4j configuration file.
log.default.location		Contains routing information for message libraries for this category for which there is no location previously specified.
log.mantaslog.location		Contains routing information for message libraries for this category for which there is no location previously specified.
log.syslog.location		Contains routing information for message libraries for this category for which there is no location previously specified.
log.smtp.hostname		Identifies the hostname of the SMTP server if e-mail address is specified as log output.
log.fatal	true	Indicates that fatal logging is enabled; falseindicates that fatal logging is not enabled.
log.fatal.synchronous	false	Indicates that fatal logging is enabled; falseindicates that fatal logging is not enabled.
log.warning	true	Indicates enabling of warning logging; falseindicates that warning logging is not enabled.
log.warning.synchronous	false	Indicates enabling of warning logging; falseindicates that warning logging is not enabled.
log.notice	true	Indicates enabling of notice logging; falseindicates that notice logging is not enabled.
log.notice.synchronous	false	Indicates enabling of notice logging; falseindicates that notice logging is not enabled.
log.diagnostic	false	Indicates that diagnostic logging is not enabled; true indicates enabling of diagnostic logging.
log.diagnostic.synchronous	false	Indicates that diagnostic logging is not enabled; true indicates that diagnostic logging is enabled.
log.trace	false	Indicates that trace logging is not enabled;trueindicates enabling of trace logging.
log.trace.synchronous	true	Indicates that trace logging is not enabled;trueindicates enabling of trace logging.
log.syslog.hostname	hostname	Indicates the host name of syslog for messages sent to syslog.
log.smtp.hostname	hostname	Indicates the host name of the SMTP server for messages that processing sends to an e-mail address.
log.time.zone	EST	Indicates the time zone that is used when logging messages.

Data Management uses common logging by assigning every component (for example, FDT or MDT) a category. You can configure the destination of log messages for each component which Table 69 describes. The default logging behavior is to send log messages to the component’s designated log file in the date subdirectory representing the current processing date under the logs directory. This behavior can be turned off by setting the Log@UseDefaultLog attribute in DataIngest.xml to false. If this attribute is true, the system continues to send messages to the designated log files in addition to any behavior that the common logging configuration file specifies.