Configuring the job expire batch process

The Job Expire batch process triggers job expiration. The batch process, by default, runs every day at 6 A.M. as configured in the scheduler-config.xml file. The batch process expires all versions of a policy in a job that can be expired.

You can configure both the scheduling and the amount of time that must elapse before expiration. Configure the batch process by modifying the following parameters in the config.xml file:

• JobExpirationEffDateThreshold is the number of days past the effective date of the policy version before a job can be expired. PolicyCenter compares this value with the effective date of the policy version, the default value is 7 (a week).
• JobExpirationCreateDateThreshold is the number of days past the create date of the submission before a submission can be expired. The create date is the day the submission entered the system. PolicyCenter compares this value with Job.CreateTime.

See also

• Scheduling work queue writers and batch processes for more information on how to configure the Job Expire batch process.
• Job expiration parameters