Sometimes, the default logging level for WebSphere is not detailed enough to debug a LiveCycle issue. Also, in Production deployment, there is a need to minimize the amount of information logged because of its significant negative impact on performance as well as the increased storage requirements imposed by large log files.
WebSphere supports the following levels of logging.
- fatal
- severe (recommended for production deployment)
- warning (recommended for test environments)
- audit
- info (default)
- config
- detail (recommended for development environments)
- fine
- finer
- finest
The level can be applied globally, or separately to various packages deployed. All LiveCycle packages will begin with com.adobe.* and org.quartz.* (the open-source Quartz Job Scheduler) However, Content Services ES packages will begin with org.alfresco.* as well as org.hibernate.* (it uses the open-source Hibernate relational persistence framework) and org.springframework.* (it uses the open-source Spring application framework).
If you are not interested in being that specific, you can set the logging level for all packages by typing in this (for the 'detail' logging level):
*=detail
Change Log Level
----------------------
- In WebSphere Admin Console, click on the appserver instance that hosts LiveCycle
- Under the 'Troubleshooting' section, click on 'Change Log Level Details'
- Wait a few minutes for WebSphere to load all of the deployed packages.
- Click on the packes you are interested in. If you would like to include all packages, click on * [All Components], then 'Message and Trace Levels', and then choose your desired logging level.
- Click 'Apply', then 'Save'.
An appserver instance re-start is required for this to take effect.
Leave a comment