Specifying log level entries
On the Logging and Tracing panel of the WebSphere® Application Server administrative console, you can manually specify the logging level of any number of classes or packages. However, you must use the correct syntax when you specify the logging level manually.
Each entry must have the form package_name.*=logging_level or class_name=logging_level. Entries are separated with a colon (:).
The minimum recommended log level for a production environment is info, which includes errors and important informational messages. However, you might need to configure the finest log level, which includes entry/exit logging, for temporary troubleshooting. The fine log level is used for debug-level logging. Log levels fine and below are not recommended for anything other than temporary troubleshooting in a production environment because they are verbose and affect performance.
The IBM CMIS for Content Manager application can be divided into the following categories for IBM CMIS for Content Manager component logging:
| Logging type | Package Name |
|---|---|
| IBM ECM CMIS application logging | com.ibm.ecm |
| IBM ECM CMIS component logging | com.ibm.ecm.cmis |
| Common component logging | com.ibm.ecm.integration |
| Performance logging | com.ibm.ecm.cmis.perf |
- To specify info-level logging for the application, which includes errors, warning, and important informational messages, enter: com.ibm.ecm.*=info
- To specify fine-level logging for the components, which includes information that can be used to debug general problems, enter: com.ibm.ecm.cmis.*=fine
- To specify finest-level logging for the components, which logs detailed trace information and method entry and exit information, enter: com.ibm.ecm.cmis.*=finest
- To specify finest-level logging for performance, which logs detailed trace information and all the detail that is required to debug performance problems, enter: com.ibm.ecm.cmis.perf=finest