ILOG JRules User Guide > Managing Rule Execution Server > Tasks > Monitoring Rule Execution Server Events > Setting the Granularity of Log Messages

The Rule Execution Server management console uses log4j. Log4j enables developers to log messages according to message type and level, and to control at runtime how these messages are formatted and where they are reported.

To modify the log statements in the management EAR:

For example, jrules-bres-management-WL81.ear/jrules-bres-management.war/WEB-INF/classes/log4j.lcf. You can configure: file size, path, encoding, and pattern. The default values are as follows:

Note
When you use a relative path for the log file, it is relative to the JVM launching directory. In some cases, you must use an absolute path (for example if you run Tomcat as a Windows service).

For further reference, see http://logging.apache.org/log4j/.

Related Concepts

Rule Execution Server Management Model

Related Tasks

Setting the Granularity of Log Messages
Finding the Cause of an Improper Rule Execution Server Configuration
Execution Events Monitoring
Management Events Monitoring
Receiving Notification of Rule Engine Events Using the API

Related Samples and Tutorials

How to Automate Ruleset Management