Scheduler Engine Configuration
Description of Issue
This article reviews the standard process for configuring the Scheduler Engine
Context
- Scheduler Configuration
- Scheduler Engine
Cause
These are the default Scheduler Engine configurations. They can be customized as needed.
Resolution
- Log into the Munis environment with an account that has Scheduler Engine Administrator Permissions
- Open Tyler Menu and navigate to System Administration > Scheduler Administration > Scheduler Queue
- Select Scheduler > Properties
- Review and populate the following variablesÂ
- Engine Default Properties
- Initial engine startup mode: Online
- Max concurrent jobs: 10
- Queue scan delay: 30
- Resume after inactivity of: Leave blank
- Run command delay: 5
- Idle loop delay: 5
- For daily maintenance: Remain running, Warn but allow, and 60
- Connection loss timeout: 0
- Timeout notification address: Leave blank
- Jobs Default Properties
- Jobs expire if not run after: Leave blank
- Retain job history: 365
- Hold next occurrence if a recurring job expires: Leave unchecked
- Hold next occurrence if a recurring job fails: Check
- Logging Default Properties
- Activity logging level: Critical only
- Auto-increment log name (add 000-999): Check
- Scheduling Dialog Default Properties
- Enable scheduling dialog: Check
- Default start time: 21:00:00
- Default job-started notification: Check
- Default job-ended notification: Check
- Default job-expired notification: Check
- 'Background' delay: 00:02:00
- Engine Default Properties
- Once complete click Accept
Additional Information