Table 1. WebSpeed Agent Logging Setting properties
Property Description
Server log filename The server log file name.
Server logging level (dynamic property) A value that specifies the amount of information to be written to the agent log. You can select from the following values in the drop-down list:
  • None — Log no entries. This is equivalent to turning logging off.
  • Error Only — Log OpenEdge error messages. This includes all error messages and is unrelated to the entry types specified. Errors continue to be logged at all higher levels.
  • Basic — Server logging entry types determine the logged information. Each entry type generates at least some output. This is the default.
  • Verbose — Logging entry types determine the logged information, but it is typically more information than Basic.
  • Extended — Server logging entry types determine the logged information, but it is typically more information than Verbose.

You can update this property dynamically. Any changes will affect all current and new brokers and/or agents.
Append to server log file Indicates whether a new agent log file should be created when the WebSpeed Transaction Server is started.
Server logging entry types (dynamic property) A comma-separated list of valid entry types for agent logging:
  • 4GLTrace — Turns on the logging for the execution of the following ABL statements: RUN, FUNCTION (user-defined functions), PUBLISH and SUBSCRIBE. Logs information at Basic or higher.
  • ASDefault — Combines the ASPlumbing and DB.Connects log entry types. This is the default value for AppServer agents.
  • ASPlumbing — Turns on logging for different actions depending on the logging level specified:
    • Basic — Logs messages when an AppServer agent starts and stops, and when client processes connect and disconnect from the AppServer agent.
    • Verbose — Same as Basic, plus logging of the execution of the top level procedure (that is, the procedure that the client process asks the AppServer agent to execute on its behalf, but not any procedure that the top level procedure executes).
    • Extended — Same as Verbose, plus messages about agent state, and status messages about read and write socket operations. Do not turn this on unless instructed to do so by Progress Software Technical Support.
  • DB.Connects — Turns on logging of database connections and disconnections. The messages include database name and user ID number. Logs information at Basic or higher.
  • DynObjects.DB — Turns on logging for dynamic database-related objects (for example, TEMP-TABLE or DATASET) as they are created and destroyed. Logs information at Basic or Verbose.
  • DynObjects.XML — Turns on logging for dynamic XML-related objects (for example, x-document or x-noderef) as they are created and destroyed. Logs information at Basic or Verbose.
  • DynObjects.Other — Turns on logging for dynamic objects that do not match the other dynamic object categories (for example, procedure or server socket) as they are created and destroyed. Logs information at Basic or Verbose.
  • ProEvents.UI.Char — Turns on logging of keystroke events for printable characters. Logs information at Basic or higher.
  • ProEvents.UI.Command — Turns on logging of keystroke events for nonprintable characters at the following logging levels:
    • Basic — Logs nonprintable keystrokes and a subset of Windows GUI events
    • Verbose — Logs nonprintable keystrokes and all Windows GUI events
  • ProEvents.Other — Turns on logging of COM, asynchronous, and server socket events. Logs information at Basic or higher, beginning with events for which you have written triggers.
  • QryInfo — Turns on database query information logging at the following logging levels, with the same amount of information logged for each level:
    • Basic — Logs static queries and initial dynamic queries
    • Verbose — Logs static queries and multiple instances of dynamic queries
  • SAX — Turns on logging for various stages of execution using the ABL SAX parser.
You can update this property dynamically. Any changes will affect all current and new brokers and/or agents.You can specify a separate logging level for each log entry type, and you can use a wildcard (*) to specify multiple entry types. For example:
4GLTrace:3,ASPlubing:2,DynObjects.*
Server log file threshold size A value of 0 or a value between 500,000 and 2,147,483,647, where 0 means there is no limit on the agent log file size other than what the operating system imposes.
Maximum number of server log files The number of rolled-over log files to keep. The value can be 0 or a value between 2 and 999999, where 0 means there is no limit on the number of agent log files to keep. The specified number represents the maximum total number of log files to keep on disk at any time, including the current log file being written to.
When the file becomes equal to or greater than the Server log file threshold size, the client process renames it and creates a new log file. The file is renamed as follows, where ###### is a number starting at 000001 and increasing to 999999, after which it rolls back over to 000001:
filename.######.extension
Server watch dog interval The interval (in seconds) for the server log file watchdog thread. If the Server log file threshold size property is specified, the broker will roll over the server log file when its size is larger than the logThreshold value.