Relación entre la Morfología dental y la estructura dental

The structure of the configuration file is shown in Example 8–3. The cardinality of each node is shown in brackets.

Example 8–3 Structure of Log Section in instanceconfig.xml File

Logging [1..1] Writers [0..1] Writer [0..1] WriterClassGroups [0..1] Filters [0..1] FilterRecord [0..n]

An example of an instanceconfig.xml file that has four writers is shown in

Example 8–4.

Example 8–4 instanceconfig.xml File with Four Writers

<?xml version="1.0" ?> <Server>

. . . . <Logging> <Writers>

<Writer implementation="FileLogWriter" name="Global File Logger"

writerClassId="1" dir="{%ORACLE_BIPS_INSTANCE_LOGDIR%}" filePrefix="sawlog" maxFileSizeKb="10000" filesN="10" fmtName="ODL-Text" ODLLogFilePath="{%ORACLE_ BIPS_INSTANCE_LOGDIR%}/diagnostic.log"/>

<Writer implementation="CoutWriter" name="Global Output Logger" writerClassId="2" />

<Writer implementation="EventLogWriter" name="Event Logger" writerClassId="3" />

<Writer implementation="CrashWriter" name="CrashWriter"

Caution: Because logging affects performance, do not increase the logging on a production implementation, except to diagnose specific issues.

Logging in Oracle BI Presentation Services writerClassId="4" /> </Writers> <WriterClassGroups> <WriterClassGroup name="All">1,2,3,4</WriterClassGroup> <WriterClassGroup name="File">1</WriterClassGroup> <WriterClassGroup name="Console">2</WriterClassGroup> <WriterClassGroup name="EventLog">3</WriterClassGroup> <WriterClassGroup name="Crash">4</WriterClassGroup> </WriterClassGroups> <Filters>

<FilterRecord writerClassGroup="Console" path = "saw" information="1" warning="31" error="31" trace="0" incident_error="32" />

<FilterRecord writerClassGroup="File" path = "saw" information="1" warning="31" error="31" trace="0" incident_error="32" />

<FilterRecord writerClassGroup="File" path="saw.mktgsqlsubsystem.joblog" information="1" warning="2" error="31" trace="0" incident_error="32"/> <FilterRecord writerClassGroup="File" path="saw.httpserver.request" information="16" warning="32" error="32" trace="0" incident_error="32"/> <FilterRecord writerClassGroup="File" path="saw.httpserver.response" information="16" warning="32" error="32" trace="0" incident_error="32"/> </Filters>

</Logging> </Server>

Table 8–3 contains a description of each node in the configuration hierarchy.

Table 8–3 Oracle BI Presentation Services Log Configuration File Elements

Element Attribute Description

Writers None Contains writers configuration.

This configuration is loaded on startup.

Writer None Configures a writer.

Writer disableCentralContro

l

(Optional) Determines that this entry is not updated by Fusion Middleware Control. Default value is true.

Logging in Oracle BI Presentation Services

Diagnosing and Resolving Issues in Oracle Business Intelligence 8-17

Writer implementation The following implementations are defined:

■ FileLogWriter. Writes to a disk file. ■ CoutWriter. Writes to standard output. ■ EventLogWriter. Writes to a Windows

event log or UNIX syslog.

■ CrashWriter. A Windows only facility that

writes to a crash dump file when

Presentation Services attempts to log from a specific source file and line number. Used in a production environment for information of some loggable but irrecoverable error (for example, failed NQTEST).

Note: Use this implementation with care as it might leave the server in an unstable state. Use this implementation in very rare diagnostic-only scenarios on a test system. On Windows, CrashWriter requires the appropriate version of dbghelp.dll (at least 6.0.17.0).

The correct dbghelp.dll can be found in

support/windows/system32. Put this DLL in the WINNT/system32 or in the main/bin directory.

No registration is required.

Writer name Unique name for the writer.

Writer writerClassId Specifies an integer number in the range 1 through 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 might have the same class ID, but if they do, those writers cannot be

distinguished by filters.

Writer fmtName (Optional) Specifies the format of logged

messages. Valid values are:

■ default - 10g style. Formats messages with

identifying headings.

■ ODL-TEXT. Formats messages in Oracle

Diagnostic Text format.

■ ODL-XML. Formats messages in Oracle

Diagnostic XML format.

If you do not set this attribute, then logged messages are displayed in the default format which for file log writers is 10g style and for console is ODL-TEXT.

See Section 8.5.3, "Examples of the Formats of Logged Messages" for examples.

Writer (FileLogWriter specific attribute)

dir Specifies the directory where log files are created.

Table 8–3 (Cont.) Oracle BI Presentation Services Log Configuration File Elements

Logging in Oracle BI Presentation Services

Writer (FileLogWriter specific attribute)

ODLLogFilePath Specifies the file that Fusion Middleware Control displays in the Log Viewer. Writer (FileLogWriter

specific attribute)

maxFileSizeKb Specifies the 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. Writer (FileLogWriter

specific attribute)

filePrefix Specifies the prefix for log files. Writer (FileLogWriter

specific attribute)

filesN Specifies the maximum number of logging files.

When this number is exceeded, the first file is deleted and re-created again. Then the logger starts to write to the beginning of the first file. Writer

(EventLogWriter specific attribute)

winSource Specifies the event log source for logged events.

Writer (CrashWriter specific attribute)

file Specifies the dump file path.

On Windows, a dump file is created in

bin/coredumps and Presentation Services continues to run.

Writer (CrashWriter specific attribute)

line Dump file line number.

WriterClassGroups None Contains the definition for writer classes. A writer class is a group of writer class IDs. WriterClassGroup

(Contains [as child text] a

comma-delimited list of class IDs.)

name Specifies the name of the WriterClassGroup.

Filters None Contains filter configuration.

FilterRecord writerClassGroup Specifies the group of writers to which this record is applied. WriterClassGroup should be defined previously in the WriterClassGroups section.

FilterRecord disableCentralContro l

(Optional) Determines that this entry is not updated by Fusion Middleware Control. Default value is true.

FilterRecord path Specifies the log source path. To enable the logging of SOAP information, enter the following value:

saw.httpserver.request.soaprequest The current filter record is applied to the software component that is identified by that path and all its subcomponents.

FilterRecord information Contains an integer that specifies the severity of the corresponding message type.

Only messages with a severity index less than the provided number are logged.

Table 8–3 (Cont.) Oracle BI Presentation Services Log Configuration File Elements

Logging in Oracle BI Presentation Services

Diagnosing and Resolving Issues in Oracle Business Intelligence 8-19