Kbase P9893: How to turn on 4GL tracing within WebSpeed, AppServer and the 4GL Client?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
11/08/2009 |
|
Status: Verified
GOAL:
How to enable enhanced logging feature?
GOAL:
How to enable client logging?
GOAL:
How to enable 4GLTracing?
GOAL:
How to turn on 4GLTracing?
GOAL:
What can be used help troubleshooting issues related to WebSpeed?
GOAL:
What can be used help troubleshooting issues related to AppServer?
GOAL:
How to trace the 4GL?
GOAL:
How to use the -clientlog, -logginglevel and -logentrytypes startup parameters
GOAL:
What does the -clientlog parameter accomplish?
GOAL:
What are the advanced logging features available to the 4GL?
GOAL:
How to turn on logging for a 4GL client?
GOAL:
How to enable 4GL Tracing?
GOAL:
How to setup 4GLTrace?
GOAL:
How to configure 4GLTrace?
GOAL:
How to enable logging for AppServer agents?
GOAL:
How to turn on logging for AppServer processes?
GOAL:
How to turn on 4GL tracing within WebSpeed?
GOAL:
How to turn on 4GL tracing within AppServer?
FACT(s) (Environment):
Progress 9.1D
Progress 9.1E
OpenEdge 10.x
All Supported Operating Systems
FIX:
The 4GL Tracing Feature is a diagnostic feature that was added in Progress Version 9.1D01 and carried over in OpenEdge releases.
In Progress 9.1D01 or higher:
This feature records the execution of the following 4GL statements in a log file:
- RUN
- User-defined FUNCTIONS
- PUBLISH
- SUBSCRIBE
The destination of the messages depends on what the client type is:
For GUI/TTY clients, the log file is the file name specified by the -clientlog startup parameter.
For AppServer and WebSpeed, the messages go to the existing server log file.
Note: The -clientlog parameter can also be used without the -logginglevel and -logentrytypes parameters.
In this case all error messages and messages that would normally appear in an alert box will still be written to the specified logfile, as well as entries on database connections and disconnections.
This information can be used to relate client log messages with database log messages.
4GL Tracing is enabled when the logginglevel parameter is set to 4, and the logentrytypes parameter is set to 2.
Note: To use -logentrytypes 4 you must be at least at Progress 9.1D09.
To set these parameters:
For GUI/TTY clients, specify the startup parameters -logginglevel 4 -logentrytypes 2.
Example:
prowin32.exe -clientlog mylog.lg -logginglevel 4 -logentrytypes 2
For AppServer/WebSpeed, set srvrLoggingLevel to 4 and srvrLogEntries to 2 in the ubroker.properties file.
Example:
srvrLoggingLevel=4
srvrLogEntries=2
In OpenEdge 10.x:
The client logging uses a different syntax. For more information, refer to the OpenEdge Development: Debugging and Troubleshooting Guide
For WebSpeed & AppServer use:
srvrLoggingLevel=2
srvrLogEntryTypes=4GLTrace
You can also use Progress Explorer to set the logging level and the log entry types for the AppServer agent under the Logging Setting section:
The logginglevel of 2 equates to the Basic setting.
The current log entry types shows a comma delimited list of the AppServer default entry types.
Add a comma and 4GLTRACE as an added entry type:
Example: ASPlumbing,DB.Connects,4GLTRACE
You can also set the desired size of the AppServer log file (500,00 bytes to 2GB) and the maximum number of files to be keep on disk. The increased logging can cause the log file to use up space very fast, which could be a problem, if not monitored or controlled.
For Client:
prowin32.exe -clientlog mylog.lg -logginglevel 2 -logentrytypes 4GLTrace