|
Similarly to the AggreGate Server, AggreGate Client uses Apache Log4J logging library for log output of its own internal events. It is highly customizable and allows multiple levels and sources of logging information along with numerous log destinations. Logging output can be redirected to:
| • | Java Message Service (JMS) |
| • | And many other destinations.. |
Logging of AggreGate Client is configured and managed exactly in the same way as the logging of AggreGate Server. In effect, this means you're most likely to use the default configuration. If you want to change anything, you're going to have to directly edit AggreGate Client logging configuration file, which is logging-client.xml, in the installation directory. The structure of this file is briefly described in logging configuration file section.
More info on logging:
|
This may seem like a bit of a terse explanation, but it's just because logging is a complex topic, and is only used for troubleshooting. If we were to delve into logging in detail, we would effectively be writing another manual for Log4J. We opted for using a third-party logging tool because it is robust, flexible, and very well documented.
|
|