Controlling Server Logging
As My webMethods Server runs, it collects logging information for a variety of categories, for web applications, and for portlet applications. Logging information is collected in two stages, Logger and Output.
Logger stage allows you to define the level of messages you want to collect for each category, web application, and portlet application.
Output stage determines the level of messages that you want
My webMethods Server to write to the console and the log files.
You can control each stage independently. The logger threshold takes precedence over an output threshold. If My webMethods Server discards a logging message because it does not meet a logger threshold, and is therefore not collected for a category or application, that message cannot be written to the output, that is, it cannot be written to the console or a log file.
Use the Logging Configuration page to control logging for the server. For more information, see
About Logging Thresholds and
Setting Logger and Output
Thresholds.
As
My webMethods Server writes log messages to the output log files, the files will grow in size. Periodically, the
My webMethods Server rolls over to a new set of files, making it easier to locate a specific date and to discard old log files as needed. For more information about the output log files, how often
My webMethods Server rolls over files, and how you can control the rollover, see
About the Log-File Rollover
Period and
Modifying the Log-File Rollover
Period.
