...
- To crate the the
scheduler_engine.log
do following changes in the- ${SCHEDULER_DATA}/config/factory.ini :
- options = -DSCHEDULER_DATA="${SCHEDULER_DATA}" -Dlog4j.configuration="file:///${SCHEDULER_HOME}
- ${SCHEDULER_HOME}/lib/log4j.properties
log4j.logger.com.sos.scheduler.engine=debug, engine
log4j.appender.engine=org.apache.log4j.RollingFileAppender
log4j.appender.engine.File=${SCHEDULER_DATA}/logs/scheduler_engine.log
log4j.appender.engine.MaxFileSize=5000KB
log4j.appender.engine.MaxBackupIndex=30
log4j.appender.engine.layout=org.apache.log4j.PatternLayout
log4j.appender.engine.layout.ConversionPattern=%5p %-12d{HH:mm:ss,SSS} (%F:%L) - %m%n
- ${SCHEDULER_DATA}/config/factory.ini :
IMP: After updating both the files
${SCHEDULER_DATA}/config/factory.ini
and${SCHEDULER_HOME}/lib/log4j.propertiesproperties
restart the JobScheduler.
The Engine Log
- contains important information about JobScheduler Engine actions.
- is stored in the file system
- is not subjected to
sos/housekeeping/scheduler_rotate_log
...