-
Notifications
You must be signed in to change notification settings - Fork 41
System Jobs
This page provides information on the Herd system jobs. The system jobs are typically scheduled to run periodically. Also, System Job Execution Post endpoint can be used to invoke the job on demand.
The following system jobs are currently setup to be executed by Herd.
Job Name | Scheduled | Description |
---|---|---|
fileUploadCleanup | Y | This is a scheduled background process that cleans up any dangling business object data records left by file upload operations. |
jmsPublishing | Y | This is a scheduled background process that publishes JMS messages queued in the Herd database. |
storagePolicySelector | Y | This is a scheduled background process that selects Business Object Data instances that are due to be archived as per user-created Storage Policies. |
This system job is a scheduled background process that cleans up dangling business object data left registered with the S3_MANAGED_LOADING_DOCK storage that have a status other than DELETED. In addition, this process also finds and deletes all orphaned multi-part upload parts in all Herd managed S3 buckets. Please note that is important for the S3_MANAGED_LOADING_DOCK storage, since it is a security risk to leave the multi-part upload parts around.
Job Parameters
Parameter Name | Herd Web Applicaiton Configuration Option | Overridable by System Job Execution Post Endpoint | Accepted Values | Default Value | Description |
---|---|---|---|---|---|
file.upload.cleanup.job.cron.expression | Y | N | Cron expression | 0 0 1 * * ? | The cron expression to schedule "fileUploadCleanup" system job. Default is to run the system job every night at 1 AM. |
file.upload.cleanup.job.threshold.minutes | Y | Y | Integer | 4320 | The threshold in minutes to be used to select dangling Business Object Data S3_MANAGED_LOADING _DOCK records and orphaned multi-part upload parts for deletion. Only the dangling business object data records and all orphaned multi-part upload parts that are older than this amount of time will be deleted by the job. The default is 4320 minutes (3 days). |
This system job is a scheduled background process that publishes JMS messages queued in the Herd database.
Job Parameters
Parameter Name | DM Web Applicaiton Configuration Option | Overridable by System Job Execution Post Endpoint | Accepted Values | Default Value | Description |
---|---|---|---|---|---|
jms.publishing.job.cron.expression | Y | N | Cron expression | 0 0/5 * * * ? | The cron expression to schedule "jmsPublishing" system job. Default is to run the system job every 5 minutes. |
This system job is a scheduled background process that selects Business Object Data (Storage Units) that are due to be archived as per Storage Policies configured in the system. For each selected Storage Unit, the jobs sends a message to the SQS queue.
Job Parameters
Parameter Name | DM Web Applicaiton Configuration Option | Overridable by System Job Execution Post Endpoint | Accepted Values | Default Value | Description |
---|---|---|---|---|---|
storage.policy.selector.job.cron.expression | Y | N | Cron expression | 0 0 2 * * ? | The cron expression to schedule "storagePolicySelector" system job. Default is to run the system job every night at 2 AM. |
storage.policy.selector.job.sqs.queue.name | Y | N | A name for an already existing AWS SQS queue that Herd AWS account has permission to write to | The AWS SQS queue name where storage policy selector job sends storage policy selection messages. | |
storage.policy.selector.job.max.business.object.data.instances | Y | Y | Integer | 1000 | The maximum number of Business Object Data instances to be selected for archival in a single run of this system job. The default is 1000 Business Object Data instances. |
- Getting Started with herd
- herd Usage Pages
- herd API documentation
- herd Workflow Tasks
- herd Tools