Universal Event Monitor for SOA Troubleshooting
Logging Operations
This information pertains to logging operations that may assist you in troubleshooting, should that be necessary. It includes different types of log files, their locations, methods of directing output, and examples.
The following table identifies the Universal Event Monitor for SOA for AIX / Linux product directories and files located under the /var/opt/universal parent directory.
Directory / File | Description |
|---|---|
log/uac | Directory containing log and work artifacts for the UAC component. |
work | Sub-directory used by the web services framework for temporary operations. It requires no user interaction. |
catalina.out | Container engine log file. |
container.log | Web services framework log file. |
derby.log | Database log file. |
uac.log | uac log file. |
Logging Configuration
At some point, you may want to check the logs for information regarding the operation of Universal Event Monitor for SOA.
Configuration of the logging operations is done via the log4jConfiguration.xml file for the server component.
AIX | This file is located in the uac product directory at |
|---|---|
UNIX | This file is located in the uac product directory at |
Windows | This file is located under |
Logging Levels
The logging levels supported by the logging implementation are:
DEBUG
INFO
WARN
ERROR (default)
The logging level should be changed only at the request of Stonebranch, Inc. Customer Support, as it can have a huge impact on performance.
Server Component Logging Configuration
By default, the logs are configured to write to a file on Linux and to write to the Event Viewer on Windows with the logging level set to error.
Appenders (Sinks) Availability
The following appenders, or sinks, are available to the server component.