Configuring API-specific Loggers
You can enable persistence layer logging for all Windchill modules using the wt.pom.SQL logger. However, it leads to a large number of log entries. Alternatively, for granular troubleshooting, you can use the API-specific loggers to restrict the persistence-layer logging to specific classes only.
To enable API-specific logging, configure the following properties in the wt.properties file located at <WT_HOME>/codebase.
• wt.pom.logger.apilevel.enabled
The default value of this property is false. When set to true, the property searches for the class names configured in the wt.pom.logger.apilevel.classes property. You will need to restart method server if you change the property value.
• wt.pom.logger.apilevel.classes
Specifies the classes for which you want to generate persistence layer log messages. To take effect, the wt.pom.logger.apilevel.enabled property must be set to true.
The property takes a comma-separated list of fully qualified class names, for example wt.dataops.purge.StandardPurgeService,wt.change2.listeners.ResultingChangeEventHandler.
The configuration example shown above enables persistence layer logging specifically for the StandardPurgeService and ResultingChangeEventHandler classes. If any methods in these classes call APIs from other classes and so on, persistence layer logging is generated for the entire call hierarchy.
The persistence layer loggers affected by these property settings are given below:
• wt.pom.sql
• wt.pom.mapping
• wt.pom.joinMapping
• wt.pom.blob
• wt.pom.statementCache
• wt.pom.statementCache.summary
• wt.pom.refreshCache
• wt.pom.properties
• wt.pom.accessControl
• wt.pds.bind
• wt.pds.concurrent
• wt.pds.concurrent.statistics
• wt.pds.exception
• wt.pds.general
• wt.pds.queryCancel
• wt.pds.queryContext
• wt.pds.meta
• wt.pds.statementParameter
• wt.query
• wt.pom.paging
• com.ptc.core.query.server
• com.ptc.core.query.common
• wt.pom.rowCount