This topic lists the locations and settings of the log files for the product.
File name | Default location |
---|---|
install.log |
|
File name | Default location |
---|---|
edge-alerts.x.log, where x is an integer |
|
edge-alerts-.x.log, where x is an integer |
Reader readerid is ON/OFF
File name | Default location |
---|---|
edge-heartbeats.x.log, where x is an integer |
|
edgeid=UP/DOWN readerid=UP/DOWN
The WebSphere Application Server log files also contain information for WebSphere Premises Server.
File name | Default location |
---|---|
SystemOut.log |
|
SystemErr.log | |
trace.log |
See Modifying the logging levels of WebSphere Premises Server using WebSphere Application Server for details on how to enable tracing on WebSphere Application Server for WebSphere Premises Server.
File name | Default location |
---|---|
db2diag.log |
|
jdbcerr.log |
File name | Default location |
---|---|
edge_controller_name_x.log,
where x is an integer For example, E1_1.log |
|
A Log File agent listens to messages and directs all OSGi log output to a configurable set of rotating files.
When one of these log file fills up, the system then creates a new file and writes to it. Each log file name is the Data Capture and Delivery controller name plus _number. For example, if the first log file is E1_0.txt, then the next file will be E1_1.txt. If the maximum number of files is reached, then the oldest log file will be deleted.
To configure the settings for these files, see the Log File agent properties.