OpenEdge Management and OpenEdge Explorer: Configuration
OpenEdge Management and OpenEdge Explorer: Configuration
OpenEdge Management and OpenEdge Explorer: Configuration
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Configuring AppServers <strong>and</strong> AppServer Internet Adapters<br />
5–16<br />
Table 5–9: AppServer Agent Logging Setting properties (3 of 4)<br />
Property Description<br />
Server logging entry types<br />
(continued)<br />
• DynObjects.Other — Turns on logging for<br />
dynamic objects that do not match the other<br />
dynamic object categories (for example,<br />
procedure or server socket) as they are<br />
created <strong>and</strong> destroyed. Logs information at<br />
Basic or Verbose.<br />
• ProEvents.UI.Char — Turns on logging of<br />
keystroke events for printable characters.<br />
Logs information at Basic or higher.<br />
• ProEvents.UI.Comm<strong>and</strong> — Turns on<br />
logging of keystroke events for nonprintable<br />
characters at the following logging levels:<br />
– Basic — Logs nonprintable keystrokes<br />
<strong>and</strong> a subset of Windows GUI events<br />
– Verbose — Logs nonprintable<br />
keystrokes <strong>and</strong> all Windows GUI<br />
events<br />
• ProEvents.Other — Turns on logging of<br />
COM, asynchronous, <strong>and</strong> server socket<br />
events. Logs information at Basic or higher,<br />
beginning with the events for which you have<br />
written triggers.<br />
• QryInfo — Turns on database query<br />
information logging at the following logging<br />
levels, with the same amount of information<br />
logged for each level:<br />
– Basic — Logs static queries <strong>and</strong> initial<br />
dynamic queries.<br />
– Verbose — Logs static queries <strong>and</strong><br />
multiple instances of dynamic queries.<br />
• SAX — Turns on logging for various stages<br />
of execution using the ABL SAX parser.<br />
You can specify a separate logging level for each<br />
log entry type <strong>and</strong> use a wildcard (*) to specify<br />
multiple entry types. For example:<br />
4GLTrace:3, ASPlumbing:2,DynObjects.*<br />
For details, see the information about client<br />
logging in <strong>OpenEdge</strong> Deployment: Startup<br />
Comm<strong>and</strong> <strong>and</strong> Parameter Reference.<br />
Server log file threshold size A value of 0 or a value between 500,000 <strong>and</strong><br />
2,147,483,647, where 0 means there is no limit on<br />
the agent log file size other than what the operating<br />
system imposes.