Building Your Event-Driven Architecture : Integration Server Administrator’s Guide : Setting Up the Server Log : Specifying Amount and Type of Information to Include in the Server Log : Logging Levels
Logging Levels
The logging levels that you can specify are described below. Each logging level includes the indicated type of message plus all messages from the levels above it (for example, the Warn level includes Fatal, Error, and Warn messages).
Level
Integration Server records these entries...
Examples
Fatal
Failures that end operations in such a way that the operations cannot successfully continue without user intervention. Failure is very likely to affect other operations or products.
Product cannot read its configuration file and has no default settings
Error
Same as Fatal, except that existing error handling renders the failure unlikely to affect other operations or products.
Business process step failed due to a service error caused by bad input data
Warn
Problems that do not end operations, or unexpected or unusual conditions that might signal impending failure.
Multiple registered JMX servers were discovered when only one is needed
Info
Success of an event that you need to know about.
Package loaded, or connection pool initialized
Debug
Code-level statements recording unusual conditions or decisions that might lead to errors.
Expected an object to be initialized but it is not, or hash table is empty
Trace
Code-level statements recording program flow and state during normal execution.
Method entry/exit, or local and global object state
Off
No information for the product or facility is written to the server log.
Copyright © 2016 - 2016 Software AG, Darmstadt, Germany.

Product LogoContact Support   |   Community   |   Feedback