Logging
SuperWEB2 logs information during the lifetime of the application to the log files located in <tomcat_home>\logs
There are a number of logging levels available for SuperWEB2:
| Level | Logs... |
|---|---|
| ERROR | Runtime errors and unexpected conditions. This is the default level and should be used when SuperWEB2 is running in production. It provides a balance between the amount of log output and the application performance. |
| INFO | More detail than ERROR level logging. You should only use the level if you are trying to identify and resolve a configuration problem. This level is not appropriate for long term use in a production environment as it impacts the application performance and disk space requirements of the application. |
| DEBUG | More detail than INFO. This logging level can be useful when investigating Rules Engine actions, as it provides full details of configured rule parameters. You should only use this level when advised to do so by support. |
There are separate log settings for the Job Queue Manager and the User Data Repository. For more information, see:
Change the Logging Level
The logging level of SuperWEB2 is controlled by the file <tomcat_home>\webapps\webapi\WEB-INF\classes\log4j.xml. This file contains the settings for the default logging level (ERROR).
There are two other files in this directory:
- <tomcat_home>\webapps\webapi\WEB-INF\classes\log4j_debug.xml
- <tomcat_home>\webapps\webapi\WEB-INF\classes\log4j_info.xml
These contain the settings for the other logging levels. To change to one of those levels you need to:
- Stop Tomcat or the SuperWEB2 service.
- Rename log4j.xml to log4j_error.xml.
- Rename either log4j_debug.xml or log4j_info.xml to log4j.xml.
For example, to switch to the INFO level you would rename log4j_info.xml to log4j.xml. - Restart Tomcat or the SuperWEB2 service.
You can switch to a different level by renaming the files accordingly: whichever file is currently named log4j.xml will be the one whose settings are applied to SuperWEB2.