Agile Process : Administering My webMethods Server : Analysis, Reporting, and Troubleshooting : Controlling Server Logging : About the Log-File Rollover Period
About the Log-File Rollover Period
Periodically, the logging process rolls over to a new set of files based on either date or file size. When My webMethods Server rolls over a file based on date, it renames the old log file so that it includes the date so that if you need to refer to old log data, it is easier to find the data for a specific date. When My webMethods Server rolls over based on size, it maintains a specified number of backup files and discards older data.
My webMethods Server log files reside in the following directory:
Software AG_directory \MWS\server\serverName\logs
The following table describes the log files that My webMethods Server creates and the default for when My webMethods Server rolls over the log file. For information about how to customize the rollover periods, see Modifying the Log-File Rollover Period.
Log file
By default, this log contains...
By default, the log is rolled over...
_full_.log
Log messages from all categories and all enabled thresholds (for example, TRACE, DEBUG, INFO, WARN, ERROR, and FATAL).
Daily at midnight
When the log is rolled over, the past days log messages are rolled over into a file that is named to reflect the date of the log information it contains:
_full_.yyyy-MM-dd.log
You can customize how often My webMethods Server rolls over this log.
_problems_.log
WARN, ERROR, and FATAL log messages from all categories.
Daily at midnight
When the log is rolled over, the past days log messages are rolled over into a file that is named to reflect the date of the log information it contains:
_problems_.yyyy-MM-dd.log
You can customize how often My webMethods Server rolls over this log.
install.log
DEBUG level log messages from the install
When the log size reaches 100 MB
When the log is rolled over, the old log messages are rolled over into a backup file that uses the following naming convention, where N is a number.
install.N.log
For example, the first time the log is rolled over, the backup log is named install.1.log. By default, My webMethods Server maintains up to three backups.
You can customize the maximum size limit for this file before My webMethods Server rolls it over and how many backup files the server maintains.
caf.log
CAF application log messages
Daily at midnight
When the log is rolled over, the past days log messages are rolled over into a file that is named to reflect the date of the log information it contains:
caf.yyyy-MM-dd.log
You cannot customize how often My webMethods Server rolls over this log.
schema.log
Log messages from DDL statements execution for creating, modifying, or deleting x-type objects
When the log size reaches 5 MB
When the log is rolled over, the old log messages are rolled over into a backup file that uses the following naming convention, where N is a number.
schema.N.log
For example, the first time the log is rolled over, the backup log is named schema.1.log. By default, My webMethods Server maintains up to ten backups.
You can customize the maximum size limit for this file before My webMethods Server rolls it over and how many backup files the server maintains.
_errors_.xm_
An XML fragment of FATAL log messages from all categories
You can wrap the XML fragment that is contained in the errors log with a root XML element to produce well-formed XML.
This log is not rolled over
Copyright © 2017 Software AG, Darmstadt, Germany.
Product LogoContact Support   |   Community   |   Feedback