Setting up the Job Conductor parameters

Type in the path to the folder that has been created to store the Job execution archives, grouped by execution tasks. This folder can not be removed. Otherwise, the tasks can not be executed.

Type in the path to the folder that has been created to store the Job execution logs, grouped by execution tasks. The logs in this folder are used to be downloaded as execution log on UI and/or for manual check of the Job execution. It is recommended not to remove this folder either.

This parameter is optional, as you can enter a value in the Storage period for log files field instead.

Enter how many execution log files you want to store in each folder created for the Jobs. Note that this limitation applies only to execution log files. The folders also contain resuming log files as well, therefore the file count in the folders is twice the value of the limit set in the Number of execution logs parameter. If this value is set to 0, there will be no limit on the number of execution logs.

This parameter is optional, as you can enter a value in the Number of execution logs parameter field instead.

Enter how long the log files of all Jobs will be kept, in seconds, before they are removed. If this value is set to 0, there will be no limit on the storage period for log files.

This parameter is optional, as you can enter a value in the Storage period for generated Jobs parameter field instead.

Enter how many generated Job archives you want to store in the dedicated folder. If this value is set to 0, there will be no limit on the number of generated Jobs.

This parameter is optional, as you can enter a value in the Maximum number of generated Jobs parameter field instead.

Enter how long the generated Job archives will be kept, in seconds, before they are removed. If this value is set to 0, there will be no limit on the storage period for generated Jobs.