Designer 10.5 | webMethods BPM Process Development Help | Process Engine Processing | Process Logging Behavior | About Process Engine Logging
 
About Process Engine Logging
 
Changing the Process Engine Logging Levels
During run time, the Process Engine transmits log messages to the Integration Server server.log file (sometimes referred to as the journal log), located by default in the folder Software AG_directory /IntegrationServer/serverName/instances/instance_name/logs. A new file is created for each date of operation, with the date appended to the file name, for example, server.log.20120815.
You may find the contents of the server.log file useful for troubleshooting or debugging purposes. The log levels listed in the following table are available:
Level
Highest message type written to server.log, plus all lower messages
Fatal
Failure that likely affects other operations or products.
Error
Failure that does not likely affect other operations or products.
Warn
Problems that do not end operations, or unexpected or unusual conditions.
Info
Success of an event (this is the default setting).
Debug
Code-level statements recording unusual conditions or decisions.
Trace
Code-level statements recording program flow and state.
Off
No information is written to the server log.
*To change the Process Engine server log level, see Changing the Process Engine Logging Levels.
*For detailed information about Integration Server logging, see Chapter 8, Setting Up the Server Log, in the PDF publication webMethods Integration Server Administrator’s Guide.
In addition to Process Engine-related messages, the server.log file also contains messages generated by individual process instances. However, you can enable process instance logging for each process model so that messages from instances of that model are sent to a separate log file. For more information, see About Process Instance Diagnostic Logging.
Related Topics