For System Administrators > System Administration Guide > Managing Job Execution History
Was this helpful?
Managing Job Execution History
You can control the amount of job history that Integration Manager maintains by date, volume, or both depending on your needs.
Example: Job Execution History
Job history cutoff of 90 days
repository.storage-type=local job.history.max-job-age=90
For example, you could set the job history cutoff at 90 days and a maximum of 150,000 records. In this scenario, Integration Manager will remove the greater number of records exceeding either threshold.
These settings are controlled in your application.properties file by adding these optional properties:
repository.storage-type=local
job.history.max-job-age=90
job.history.max-job-count=150000
Additionally, you may control how often your job history is evaluated. The default is once per day. We highly recommend evaluating no more often than once per day in production systems. For test and non-production systems, you may specify an interval of no less than 5 minutes (300000ms). To modify this interval, you may add the optional property:
job.history.clean-interval=86400000 (evaluated in milliseconds)
After adding or changing the application.properties file, restart the Integration Manager service.
Managing Job History for Other Repository Types
Automatic job history management works only if you are storing history in a “local” repository, meaning a local file system. For other repository types, you can manage job history using their native lifecycle management policies.
 
 
 
 
 
 
 
 
 
Last modified date: 03/14/2022