13.01.2013 Views

OpenEdge Data Management: DataServer for Microsoft SQL Server

OpenEdge Data Management: DataServer for Microsoft SQL Server

OpenEdge Data Management: DataServer for Microsoft SQL Server

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Chapter 6: Connecting the <strong>Data</strong><strong>Server</strong><br />

Analyzing application execution with Enhanced Logger<br />

The Enhanced Logger provides a means <strong>for</strong> either standard reporting of runtime<br />

activity or logging diagnostic data <strong>for</strong> troubleshooting problems based on a set of<br />

logging characteristics. The <strong>Data</strong><strong>Server</strong> can be configured to write in<strong>for</strong>mation to a log<br />

file. You control the type and the degree of detail logged using a combination of log<br />

entry types and logging levels. Log entry types are categories of in<strong>for</strong>mation written to<br />

the log file. Logging levels control the degree of logging detail <strong>for</strong> any given log entry<br />

type.<br />

The legacy qt_debug logging infrastructure only logged server in<strong>for</strong>mation but the<br />

Enhanced Logger framework <strong>for</strong> <strong>Data</strong><strong>Server</strong>s offers two logging contexts:<br />

• <strong>Server</strong> context <strong>for</strong> <strong>Server</strong>-specific log entries<br />

• Client context, which shares logging in<strong>for</strong>mation with <strong>OpenEdge</strong> clients and<br />

App<strong>Server</strong> agents.<br />

Note: Both the server and the client contexts <strong>for</strong> <strong>Data</strong><strong>Server</strong>s include some log entry<br />

types that work in concert with one another. You can yield a detailed<br />

understanding of the <strong>Data</strong><strong>Server</strong> operations by merging the contexts into one<br />

view of <strong>Data</strong><strong>Server</strong> log activity.<br />

LOG-MANAGER system handle attributes and methods<br />

The LOG-MANAGER system handle controls logging settings <strong>for</strong> the <strong>OpenEdge</strong> client and<br />

<strong>Data</strong><strong>Server</strong> client contexts. The LOG-MANAGER attributes and methods allow you to<br />

programmatically control the logging levels and log entry types during the execution of<br />

your program.<br />

Table 33 lists the function of each LOG-MANAGER system handle attribute.<br />

Table 33: LOG-MANAGER system handle attributes (1 of 2)<br />

Attribute Access Function<br />

ENTRY-TYPES-LIST Readable Returns a list of all valid entry types.<br />

LOG-ENTRY-TYPES Readable/Writable Returns/Writes a list of one or more<br />

types of log entries.<br />

LOGFILE-NAME Readable/Writable Returns/Writes the name of the log<br />

file.<br />

LOGGING-LEVEL Readable/Writable Returns/Writes the level at which log<br />

entries are written.<br />

LOG-THRESHOLD Readable Returns the file size threshold of log<br />

files. When the current log file<br />

becomes equal to or greater than the<br />

specified size, <strong>OpenEdge</strong> renames<br />

and saves the log file and creates a<br />

new log file.<br />

230 <strong>OpenEdge</strong> <strong>Data</strong> <strong>Management</strong>: <strong>Data</strong><strong>Server</strong> <strong>for</strong> <strong>Microsoft</strong> <strong>SQL</strong> <strong>Server</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!