Configuring Which Log Events Are Stored

By default, most loggers are set up so that Windchill stores only ERROR and FATAL log events (except where the configuration has already been extended to output other log events) in Windchill log files. Therefore, you must usually change the configuration to see other log events, such as TRACE, DEBUG, INFO, or WARN.

To turn on a given logging level for a given area, determine if the area has a corresponding logger by viewing the loggers from the Operations tab (for details, see Using MBeans to Work with Log Files) or by using the Log Levels page (available from Site

> Utilities > Server Status. On the Server Status page, click Monitoring Tools):

• If a log4j logger has not been implemented, locate the property that sets the log level in wt.properties and set the level in that property using the xconfmanager utility.

• If a log4j logger has been implemented, you can turn on a given logging level for all loggers or adjust the logging level at a more specific level.

To turn on a given logging level for all loggers, find the log4j.rootLogger property in the appropriate properties file and change the value before the first comma ("error" by default) to the desired level. For example, change:

Turning on logging for all loggers usually results in too much data in the log output; therefore, a better practice is to adjust the logging level at a more specific logger level. To do this, you can append a line of following form to the properties file:

where <targetLoggerName> is the name of the logger and <desiredLogLevel> is the log level.

For example, to set the log level for wt.servlet.ServletRequestMonitor.stats to INFO, add the following property to the log4jWebApp.properties file:

Adding this property also causes the default log level of all wt.servlet.ServletRequestMonitor.stats.* loggers to be set to INFO. For example, the level of the wt.servlet.ServletRequestMonitor.stats.summary logger is also set to INFO unless the level of this logger is otherwise specified.

Changes to log4j configuration files may go unnoticed for as long as a few minutes as the checks for modifications to these files take place on a periodic basis. To force an immediate reload of the log4j configuration file, use the reconfigure operation on the Logging MBean, or make temporary changes to the log4j configuration without changing the configuration files.

Manual changes made to property files may not be preserved when you apply maintenance releases; ensure that any files you manually change are backed up.