Issues that you encounter while generating documents from
the templates and document specifications are listed in the core log
files. You can customize the location of the rpe.log file,
for example.
Before you begin
You can enable debug mode to include messages in the core
log files that describe how each element is processed during document
generation. By default, debug mode is not enabled. See
Setting the engine preferences for information about enabling debug
mode.
About this task
The location of the file that contains logging customizations
is
%RPE_HOME%\config\log4j.properties. Properties
that include the text
txtOutput apply to the
core log files.
Table 1. Log propertiesLog property |
Default value |
Description |
log4j.appender.txtOutput.File |
${java.io.tmpdir}/RPE/rpe.log |
The default location of the rpe.log file
is the user home directory in the application data. You can edit this
value to another directory location. See the Example: Changing the output location below. |
log4j.appender.txtOutput.MaxFileSize |
1000KB |
The size at which a new log file is created.
When the size of the rpe.log file is equal or
greater than 1MB, then the file is renamed rpe.log.1, rpe.log.2,
etc and the rpe.log is generated new. rpe.log is
always the newest log file. |
log4j.appender.txtOutput.Threshold |
DEBUG |
The minimal degree of severity of the messages
in the log file. You can enter any of the following thresholds, listed
from least to greatest severity:- DEBUG
- INFO
- WARNING
- ERROR
You can also set the threshold value to OFF to
disable logging. |
log4j.appender.txtOutput.layout.ConversionPattern |
%d{dd-MM-yyyy}T%d{HH:mm:ss:SS} %m %n |
- %d{dd-MM-yyyy}T%d{HH:mm:ss:SS}: The date and
the time of the log event
- %m: Log message
- %n: Enters a carriage return
|