We found out that if a job has parameters defined in an external
XML file, changes to those parameters is not reflected until we "touch" or
"change" the job XML.
Here is our job:
<job idle_timeout="0" order="yes" process_class="/CE_MAINTENANCE" stop_on_error="no" tasks="1"
title="[CE] This job removes all records in the tables SCHEDULER_HISTORY, SCHEDULER_ORDER_HISTORY,
DAYS_SCHEDULE, SOS_FTP_FILES which are older than the value of the parameter
delete_history_interval" visible="yes">
<params>
<include file="/opt/gts/var/lib/JobScheduler/CleanupHistoryConfig.xml"/>
</params>
<script java_class="com.sos.jitl.housekeeping.cleanupdb.JobSchedulerCleanupSchedulerDbJSAdapterClass" language="java"/>
<monitor>
<script java_class="gts.prisma.service.batch.common.LogInfoMonitor" language="java"/>
</monitor>
</job>
The reason lies in where you are keeping your parameter file:
- The JobScheduler watches objects (i.e. files) in the live-folder.
- If a file such as an include file is changed, all other objects using this file will also be reloaded and updated.
- Changes made to an include file will not be recognized if the included file is not located in the live-folder because JobScheduler does not normaly watch folders outside the live folder.
If you create a link in the live-folder to the "external" file it should be work in the way you request.
See also: