<< Click to Display Table of Contents >> Current:  System Management  > System Attribute Configuration  Schedule Tasks Configuration

The user can configure some attributes for Schedule Tasks.

 

❖Startup status of task plan service

Configure the attribute: scheduler.init.start=xxx in bi.properties. xxx can be true or false, and the default value is true. When the value is true, the task plan service is started; when the value is false, the task plan service is closed. 

 

❖Execution of Multi-task

Configure the attribute: sched.job.parallel=xxx in bi.properties. xxx can be true or false, and the default value is true. When the value is true, multi-task is in parallel execution in job; while it is false, multi-task is in serial execution in job.

 

❖The preorder job fails, and the execution status of subsequent job

Configure the attribute:  sched.afterjob.execute=xxx in bi.properties. xxx can be true or false, and the default value is false. If the value is true, the subsequent job continues to run when the preorder job fails; while the value is false, the subsequent job does not run when the preorder job fails.

 

❖Date format of output file

Configure the attribute: export.append.ts.format=xxx in bi.properties. xxx can be yyyyMMdd or yyyyMMddHHmmss, and the default value is yyyyMMdd (year-month-day). 

Similarly, you can configure the date format: mail.append.ts.format=yyyyMMdd for sending the attachment of email.

 

❖Resend mechanism of sending email

Configure the attribute: mail.repeat=xxx in bi.properties. xxx can be true or false, and the default value is true. When the value is true, the task of sending email will be repeated for three times if the network is not stable; when it is false, the task of sending email will not be repeated. 

 

❖The create number and concurrent number of job by grouping

Configure the attribute in the bi.properties file: job.concurrency.limit=xxx, where xxx can be true or false, and the default value is false. When the value is true, the "Job Quantity Limit" attribute is added in the group information of group management of authorize users, as shown below:

After you set a job quantity limit for a group, the number of user-created jobs and the number of running jobs in the group cannot exceed this number.

➢Note:

1.The number of jobs that can be set is less than the number of CPU in the license of the current node;

2.admin and admin_role users do not have a limit on the number of jobs;

3.When a user is in multiple groups, the number of jobs for that user is limited to the minimum number of jobs set in all groups;

4.When a user is in a multi-level group, if the current group has set the job quantity limit, the number of jobs of the user is limited to the number of jobs set by the current group; if the current group does not set the number of jobs, the number of jobs of the user is limited to the number of jobs that inherit the adjacent parent group;

5.After the user moves the group, the job that the user has created is retained, but the number of jobs that are run is limited by the number of jobs currently grouped.