Personnalisation avancée > Adaptateur Windchill > Configuring the Windchill Adapter > Configuring Windchill Adapter Logging
  
Configuring Windchill Adapter Logging
Windchill uses the Apache log4j package to produce log messages. This package is bundled with Windchill.
To manage logging, you should be familiar with the following:
• General information about the log4j package.
The following URL takes you to an introduction to log4j:
http://logging.apache.org/log4j/docs/manual.html
• General information about setting log levels, working with log files, and viewing and emailing the log files for all Windchill products.
For more information, see Managing Windchill Logging.
• The loggers that are used for the Windchill adapter logging.
For descriptions of the out-of-the-box Windchill loggers, view the following file:
<Windchill>/codebase/loggers.html
As mentioned in loggers.html, the following loggers that are used by the Windchill adapter replace the use of setting properties for logging:
Logger
Description
wt.adapter.attribute
Logs messages about the processing of attributes on objects, including statistics associated with the retrieval and translation of attribute values.
wt.adapter.exception
Logs the stack traces associated with exceptions that are caught by the Windchill adapter.
wt.adapter.session
Logs messages related to Windchill session interactions surrounding task and webject invocation by the Windchill adapter.
wt.adapter.verbose
Logs information about adapter operations that do not pertain to any specific webject. This includes general information about execution of tasks, information about time to execute webjects and tasks, information about user authentication, so on.
wt.adapter.webject
Logs detailed information about individual webject parameters and internal webject operations.
wt.adapter.trace.timing
Logs statistical information pertaining to how long specific actions during webject invocation take to perform. Most messages issued to this logger require a log level of TRACE.
These logger names mimic the previous adapter properties that had been used for logging. Log messages issued based on property settings are now issued to the corresponding log4j logger. Because these loggers replace the legacy logging, each logger is either essentially on or off.
Out of the box, only error logging is enabled.