30.11.2012 Views

OpenEdge Management and OpenEdge Explorer: Configuration

OpenEdge Management and OpenEdge Explorer: Configuration

OpenEdge Management and OpenEdge Explorer: Configuration

SHOW MORE
SHOW LESS

Create successful ePaper yourself

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

Configuring WebSpeed Messengers <strong>and</strong> WebSpeed Transaction Servers<br />

7–22<br />

Table 7–13: WebSpeed Agent Logging Setting properties (2 of 4)<br />

Property Description<br />

Server logging entry types<br />

(dynamic property)<br />

A comma-separated list of valid entry types for<br />

agent logging:<br />

• 4GLTrace — Turns on the logging for the<br />

execution of the following ABL statements:<br />

RUN, FUNCTION (user-defined functions),<br />

PUBLISH <strong>and</strong> SUBSCRIBE. Logs<br />

information at Basic or higher.<br />

• ASDefault — Combines the ASPlumbing<br />

<strong>and</strong> DB.Connects log entry types. This is the<br />

default value for AppServer agents.<br />

• ASPlumbing — Turns on logging for<br />

different actions depending on the logging<br />

level specified:<br />

– Basic — Logs messages when an<br />

AppServer agent starts <strong>and</strong> stops, <strong>and</strong><br />

when client processes connect <strong>and</strong><br />

disconnect from the AppServer agent.<br />

– Verbose — Same as Basic, plus<br />

logging of the execution of the top level<br />

procedure (that is, the procedure that<br />

the client process asks the AppServer<br />

agent to execute on its behalf, but not<br />

any procedure that the top level<br />

procedure executes).<br />

– Extended — Same as Verbose, plus<br />

messages about agent state, <strong>and</strong> status<br />

messages about read <strong>and</strong> write socket<br />

operations. Do not turn this on unless<br />

instructed to do so by Progress<br />

Software Technical Support.<br />

• DB.Connects — Turns on logging of<br />

database connections <strong>and</strong> disconnections.<br />

The messages include database name <strong>and</strong><br />

user ID number. Logs information at Basic<br />

or higher.<br />

• DynObjects.DB — Turns on logging for<br />

dynamic database-related objects (for<br />

example, TEMP-TABLE or DATASET) as<br />

they are created <strong>and</strong> destroyed. Logs<br />

information at Basic or Verbose.<br />

• DynObjects.XML — Turns on logging for<br />

dynamic XML-related objects (for example,<br />

x-document or x-noderef) as they are created<br />

<strong>and</strong> destroyed. Logs information at Basic or<br />

Verbose.

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

Saved successfully!

Ooh no, something went wrong!