Bookshelf v10.1.3.2: Oracle BI Presentation Services Configuration File Structure

The structure of the configuration XML file is shown in Figure 3. The cardinality of each node is shown in brackets.

An example of a logconfig.xml file that has four writers is shown in Figure 4.

An example of a logconfig.xml file that has one writer set up to record charting events is shown in Figure 5.

Table 18. Oracle BI Presentation Services Log Configuration File Elements
Element	Attribute	Description
Writers	Contains writers configuration. This configuration is loaded on startup.
Writer	Configures a writer.
	implementation	Name of the C++ class that implements the writer. The following implementations are defined: FileLogWriter. Writes to a disk file. CoutWriter. Writes to standard output. EventLogWriter. Writes to Windows event log or UNIX syslog. CrashWriter. Writes to a crash dump file when the Oracle BI Presentation Services attempts to log from a specific source file and line number. Used in a production environment for information of some loggable but non-fatal error (for example, failed NQTEST). On Windows, CrashWriter requires appropriate version of `dbghelp.dll` (at least 6.0.17.0). The correct `dbghelp.dll` is found in `support/windows/system32`. Put this DLL in the `WINNT/system32` or in the `main/bin` directory. No registration is required.
	name	Unique name for the writer.
	writerClassId	Integer number in the range 1-10. This number is used by filters to allow or prohibit logging. Each distinct writer must have a unique value, which is used later for filter configuration. Different writers may have the same class ID, but if they do, those writers cannot be distinguished by filters.


Writer (continued)	fmtName	(optional) Specifies the format of logged messages. Valid values are: default. Formats messages with identifying headings. short. Formats messages in a shortened form without identifying headings. xml. Formats messages in XML. If you do not set this attribute, then logged messages appear in the default format. For examples of these formats, see Examples of the Formats of Logged Messages.
	FileLogWriter specific attributes:
	dir	Directory where log files are to be created.
	maxFileSizeKb	Maximum size of the logging file in kilobytes. When the file size limit is reached, the file is closed and a new logging file is created.
	filePrefix	Log files prefix.
	filesN	Maximum number of logging files. When this number is exceeded, the logger starts to write to the beginning of the first file.
	EventLogWriter specific attributes:
	winSource	Event log source for logged events.
	CrashWriter specific attributes:
	file	Dump file path. On Windows, a dump file is created in `bin/coredumps` and Oracle BI Presentation Services continues to run.
	line	Dump file line number.
WriterClassGroups	Contains definition for writer classes. Writer class is a group of Writer class IDs.
WriterClassGroup	Contains (as child text) a comma-separated list of class IDs.
WriterClassGroup	name	Name of the WriterClassGroup.
Filters	Contain filter configuration.
FilterRecord	writerClassGroup	Specifies the group of writers to which this record is applied. WriterClassGroup should be defined previously in the WriterClassGroups section.
	path	Log source path. To enable the logging of SOAP information, enter the following value: saw.httpserver.request.soaprequest Current filter record is applied to the software component identified by that path and all its subcomponents.
	information	An integer that specifies the severity of the corresponding message type. Only messages with a severity index less than the provided number are logged.
	warning
	error
	security