This document covers the following topics:
All Event Replicator Target Adapter log files are stored in the \logs subdirectory of your Event Replicator Target Adapter installation. The Event Replicator Target Adapter log file name is sqlrep.log, which contains all current log messages. If you have a problem, please keep this log file.
In addition, the following additional log files may be found at this location. If you have a problem, please keep these log files as well:
Statistics about the Event Replicator Target Adapter session are stored in log files with
names in the format:
ArtResource_yyyymmdd_hhmmss.log,
where the date and time are used to make unique log files for each session.
Metrics up to the last transaction processed during the session
are stored in log files with names in the format:
ArtMetrics_yyyymmdd_hhmmss.log,
where the date and time are used to make unique log files for each session.
If you requested that webMethods EntireX or WebSphere MQ tracing occur when you configured the source definitions for Event Replicator Target Adapter, the etb_trace.log file (for webMethods EntireX) or the mqs_trace.log file (for WebSphere MQ) will be created at this location.
If you requested that all incoming Event Replicator messages be captured for debugging purposes when you configured the source definitions for Event Replicator Target Adapter, an etb_capture.log file (for webMethods EntireX) or an mqs_capture.log file (for WebSphere MQ) will be created at this location.
On Windows systems, the sqlrep.log file can be reviewed using a text editor. On UNIX systems, it can be reviewed by running the sqlreplog.sh script. You can control the level of log messages written to the sqlrep.log file; read Setting Log Levels for more information.
Each time you start up the Event Replicator Target Adapter, a new sqlrep.log file is created. The previously-existing log file will be renamed sqlrep.log.1. All previous log files are also retained and renamed, so that the lowest numbered file is the most recent historical log file (the sqlrep.log file with no number is always the current log file). In other words, if an sqlrep.log and an sqlrep.log.1 file already exist when the Event Replicator Target Adapter is started, the following sequence of events occurs:
File sqlrep.log.1 is renamed to sqlrep.log.2.
File sqlrep.log is renamed to sqlrep.log.1.
A new sqlrep.log file is created for the new Event Replicator Target Adapter session.
When an sqlrep.log file reaches 10MB in size, it is renamed sqlrep.log.1, and all previous log files are retained and renamed as well, as described above.
A maximum of 99,999 log files can be retained. When this maximum is reached and a new sqlrep.log file is created, the sqlrep.log.99999 file is overwritten with data from the sqlrep.log.99998 log file.
When the Event Replicator Target Adapter is installed, all messages that display to the console are automatically written to the Windows or UNIX system event logs (as appropriate). You can control the level of log messages written to the Windows and UNIX event logs; read Setting Log Levels for more information.
You can set the log level of messages written to the sqlrep.log log file, the Windows and UNIX event logs, and to the console. Three log levels are available (listed in order of settings that result in the most logging to those resulting in the least logging):
| Log Level | Description |
|---|---|
| DEBUG | Only debugging, informational, warning,
error, and fatal messages are logged or displayed.
Note: |
| INFO | Only informational, warning, error, and fatal messages are logged or displayed. |
| ERROR | Only error and fatal messages are logged or displayed. |
To change the log level of messages sent to the console:
Edit the log4j.properties file. This file is located in the \webapps\sqlrep\WEB-INF\classes directory wherever you installed Event Replicator Target Adapter.
Locate the lines in the log4j.properties that read:
log4j.category.com.softwareag.ada=loglevel,appender-name1,appender-namen . . . log4j.appender.CONSOLEAppender.Threshold=loglevel
Note:
These lines will not be next to each other in the
file.
These lines in the file control the level of Event Replicator Target Adapter log messages sent to the console. By default, the log level is set to ERROR.
Change the log level as needed. Valid log level values are ERROR, INFO, and DEBUG, as described earlier in this section. For example, the following settings would display informational and error messages on the console.
log4j.category.com.softwareag.ada=DEBUG, CONSOLEAppender . . . log4j.appender.CONSOLEAppender.Threshold=INFO
Note:
Setting the log level to DEBUG can impact
performance.
To change the log level of messages written to the
sqlrep.log file:
Edit the log4j.properties file. This file is located in the \webapps\sqlrep\WEB-INF\classes directory wherever you installed Event Replicator Target Adapter.
Locate the lines in the log4j.properties that read:
log4j.category.com.softwareag.ada=loglevel,appender-name1,appender-namen . . . log4j.appender.FILEAppender.Threshold=loglevel
Note:
These lines will not be next to each other in the
file.
These lines in the file control the level of Event Replicator Target Adapter log messages written to the sqlrep.log file. By default, the log level is set to ERROR.
Change the log level as needed. Valid log level values are ERROR, INFO, and DEBUG, as described earlier in this section. For example, the following settings would write all error, informational, and debugging Event Replicator Target Adapter messages to the sqlrep.log file.
log4j.category.com.softwareag.ada=DEBUG, FILEAppender . . . log4j.appender.FILEAppender.Threshold=DEBUG
Note:
Setting the log level to DEBUG can impact
performance.
To change the log level of messages written to the Windows or
UNIX system event logs:
Edit the log4j.properties file. This file is located in the \webapps\sqlrep\WEB-INF\classes directory wherever you installed Event Replicator Target Adapter.
In Windows environments, locate the lines in the log4j.properties that read:
log4j.category.com.softwareag.ada=loglevel, appender-name1,appender-namen . . . log4j.appender.NTAppender.Threshold=loglevel
Note:
These lines will not be next to each other in the
file.
These lines in the file control the level of Event Replicator Target Adapter log messages written to the Windows event log. By default, the log level is set to ERROR.
In UNIX environments, locate the line in the log4j.properties that reads:
log4j.appender.UNIXAppender.Threshold=loglevel
This line in the file controls the level of Event Replicator Target Adapter log messages written to the UNIX system event log. By default, the log level is set to ERROR.
Change the log level as needed. Valid log level values are ERROR, INFO, and DEBUG, as described earlier in this section. For example, the following setting would write all error, informational, and debugging Event Replicator Target Adapter messages to the Windows event log.
log4j.category.com.softwareag.ada=DEBUG, NTAppender . . . log4j.appender.NTAppender.Threshold=DEBUG
Note:
Setting the log level to DEBUG can impact
performance.
This step pertains to UNIX systems only. If you are working on a Windows system, you can ignore this step.
In UNIX environments, an additional step must be taken that has system-wide implications. The UNIX syslog.conf file controls the level of logging for the entire UNIX system, so any log level settings set by the Event Replicator Target Adapter for the UNIX system event log (in the previous step) may be overridden by the syslog.conf settings. To fully change the log level settings, you must have your UNIX system administrator update the syslog.conf file as follows and restart the daemon:
| To set the log level to: | Update syslog.conf to include an entry for: |
|---|---|
| DEBUG | user.debug |
| INFO | user.info |
| ERROR | user.err |
The syslog.conf entries should direct these message levels to appropriate UNIX system directories. For complete information on updating the syslog.conf file, refer to your UNIX documentation.