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

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

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

Table 39 identifies the logging levels and entry types <strong>for</strong> client and server contexts.<br />

Table 39: Setting logging levels and log entry types<br />

Operation<br />

Mode Logging Option OE Client<br />

Startup /<br />

connection<br />

Runtime<br />

setting<br />

Logging level -logginglevel,<br />

parameter<br />

Log entry types -logentrytypes,<br />

parameter<br />

ubroker.properties<br />

1,2<br />

-logginglevel,<br />

parameter<br />

-logentrytypes,<br />

parameter<br />

Logging level LOG-MANAGER:<br />

LOGGING-LEVEL<br />

attribute<br />

Logging level LOG-MANAGER:<br />

LOG-ENTRY-TYPES<br />

attribute<br />

MSS <strong>Data</strong><strong>Server</strong><br />

<strong>Server</strong><br />

-Dsrv logginglevel,<br />

parameter<br />

-Dsrv<br />

logentrytypes,<br />

parameter<br />

1. logginglevel and logentrytypes specified in the ubroker properties file are <strong>for</strong> App<strong>Server</strong><br />

agents in the client context only.<br />

2. To specify logginglevel and logentrytypes at startup <strong>for</strong> the <strong>Data</strong><strong>Server</strong>'s server context, continue to<br />

use the -Dsrv Startup/connection options. logginglevel and logentrytypes specified in the<br />

ubroker properties file <strong>for</strong> a <strong>Data</strong><strong>Server</strong> broker instance are ignored. Specifying the -Dsrv options<br />

within the srvrStartupParam of a <strong>Data</strong><strong>Server</strong> broker instance is also ignored.<br />

The following code example shows how logging levels and log entry types are set using<br />

the client startup switch:<br />

-logentrytypes DS.Cursor:3<br />

-logentrytypes DS.Cursor –logginglevel 3<br />

-Dsrv logginglevel<br />

-Dsrv logentrytype<br />

In the following example, logging levels and the log entry type are set using the<br />

LOG-MANAGER system handle:<br />

LOG-MANAGER:LOG-ENTRY-TYPES = "DS.Cursor:3"<br />

DSLOG-MANAGER:<br />

LOGGING-LEVEL<br />

attribute<br />

DSLOG-MANAGER:<br />

LOG-ENTRY-TYPES<br />

attribute<br />

In the next example, the logging level and log entry types are defined using the -Dsrv<br />

switch.<br />

-Dsrv logentrytypes,<strong>SQL</strong>:3<br />

-Dsrv logentrytypes,<strong>SQL</strong>,logginglevel,3<br />

The following example demonstrates the use of a DSLOG-MANAGER system handle with<br />

a <strong>Data</strong><strong>Server</strong> DB-CONTEXT attribute.<br />

DSLOG-MANAGER:LOG-ENTRY-TYPES = "<strong>SQL</strong>:3"<br />

236 <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!