Release 10.1A: OpenEdge Application Server:
Developing AppServer Applications

> ## Examining the AppServer agent log file

> When you investigate errors and troubleshoot code, examine the contents of the AppServer agent log (specified using the `srvrLogFile` property in `ubroker.properties`). It can contain OpenEdge system messages (informational, error, and warning) and output from Progress 4GL `MESSAGE` statements that are not assigned an output destination by the `OUTPUT` `TO` `KEEP-MESSAGES` statement. For more information, see the `OUTPUT` `TO` statement entry in OpenEdge Development: Progress 4GL Reference .

> You can choose to track and record procedure information using the following properties in the `ubroker.properties` file:

> - `srvrLoggingLevel`

> - `srvrLogEntryTypes`

> These properties tell an AppServer agent to put procedure call trace messages into the AppServer agent log file with different levels of detail and for different types of information. Specifically, they issue a start message when a remote procedure begins and an end message when a remote procedure returns. Then, when you see a system message in the AppServer agent log file, you can determine what procedure generated a specific message.

> You can also troubleshoot functions of the AppServer broker in your application using the corresponding properties in the `ubroker.properties` file:

> - `brkrLoggingLevel`

> - `brkrLogEntryTypes`

> For more information on using log files generated with these and other properties, see OpenEdge Development: Debugging and Troubleshooting .

Copyright © 2005 Progress Software Corporation www.progress.com Voice: (781) 280-4000 Fax: (781) 280-4095