Job Configuration

Configure the settings of the job including start and end times, notifications, auditing and retention

Job Configuration Fields

Standard Options

Note: START AND END TIME
These values are only set by users for Simple Migrations. For Incremental Migrations, they are calculated based on when the job was last run. Event and Polling jobs don't use them at all

Notifications

Notifications will only function is email is enabled. This allows the user to set conditions in which the listed email addresses will receive confirm status reports when a job completes.

Advanced Options

Field	Description
Repository Connection Thread Count	The number of individual workers which will process and queue documents. Implementation may vary in certain systems.
Output Connection Thread Count	The number of individual workers which will process and post documents. Implementation may vary in certain systems.
Batch Size	If greater than 0, Documents will be assigned a batch ID. Batch Ids are a combination of the job id and the job run id (the timestamp of when the job was started), plus the batch number. The batch Id will also be set as the highest parent folder for the document. (Ex. /home/simflofy will become {batchId}/home/simflofy). Some connectors have their own batch configuration, which is compatible with this field.
Max Queue Size	Limits the number of documents that can be queued at once, making repository workers wait. This can slow down output speeds, which may be useful if your output repository can be throttled.
Max Errors Allowed	Maximum errors before the job stops. Leave 0 for unlimited errors.
Process Relationships	Check this to tell Target Connector to process Document Relationships. This feature only works for the CMIS Connector.
Include Hash	Check to tell Repository Connector to create hash of content if possible.
Repository and Output Time Zone	These values will be used to adjust date fields (Created, Modified, and Mapped) to the appropriate timezone for their destination.
Chain Job	Select a job to run after this one completes.
Chain Job Wait Interval	Amount of time to wait after job completes before starting next job in format: 5s 5m 5h 5d
History Retention	How long to keep the Job Run History for this job before the Job History Clean up Service clears the content.

Auditing

Audit: Where to write audit data too. Note that Job Restart and Document Search will only work if Mongo is selected.
- Mongo: Audit to the Mongo Database or SQL Database if running in SQL mode.
- Log4j: Audit to the 3sixty-admin.log
- None: Auditing is turned off.
Record Audit When: The audit level or what to audit.
- All (Read, Written, Skipped, Deleted and Failed): Full Auditing
- Failures Only: Audit only those records that fail during a job run.
- Failed and Deleted: Audit a record that failed during the job run or was deleted from a Sync Job.
- Failed and Skipped: Audit a record that failed during the job run or was skipped.
- Written, Failed and Deleted: Audit a record that failed during the Job run or was deleted from a Sync Job or written by the Output Connection.
- Written, Failed, Skipped and Deleted: Audit a record that failed during the Job run or was skipped or deleted from a sync job or written by the Output Connection.

More detail on Auditing in 3Sixty