EAServer 5.0 includes a more configurable logging mechanism that allows integration with the JDK 1.4 Java Logging package or the Apache Log4j logging system. A server’s logging properties are defined in a Log Profile, which defines the logging subsystem used as well as other properties, such as output destinations, formats, and the level of severity required before a message is recorded. You can also configure different log profiles for the debug and production server versions.
You can use the following logging subsystems:
The built-in EAS subsystem, which offers the same functionality available in EAServer 4.x versions, plus several enhancements:
The ability to configure log levels. so that messages below a specified level of severity are discarded.
Support for different logging configurations in the debug and production servers.
Optional archiving and compression of previous log file versions.
More control over message formatting.
Apache Log4j, which is commonly used on large projects. For more information, see the Apache Log4j Documentation.
The Java Logging package, included in JDK 1.4. This API is Sun’s proposed standard for logging in Java applications. For more information, see the Java Logging documentation. To use this package, your server must be running JDK 1.4 or a later JDK version.
If you use the Log4j or Java Logging packages, you can extend default behavior by plugging in your own code that implements the required interfaces. For example, you can install Log4j log handler classes that write messages to the Windows NT event log or to a database. Also, if you use one of these packages to log messages from your own component or application code, you can configure the server’s log profile so that server log messages go to the same destinations.
