The scheduler runs reports in the background according to a user-defined schedule (also called a job). You can configure the following aspects of the scheduler:
• | Configuring the Scheduler Misfire Policy |
• | Configuring Scheduler Failure Notifications |
• | Restricting File System Output |
• | Removing Report Scheduling Interval Options |
• | Adding a Holiday Exclusion Calendar |
Configuring the Scheduler Misfire Policy
A scheduler misfire occurs when the scheduler cannot run a report at the designated time, for example because JasperReports Server is offline, its database is offline, or the number of threads is limited. In this case, you can configure the behavior of the scheduler to retry the report or skip the scheduled run.
You can set a different misfire policy for each kind of job schedule: single job, repeating job, and calendar job. Misfire policies are defined in the Quartz Scheduler documentation and other online resources:
http://quartz-scheduler.org/documentation/quartz-2.x/tutorials/tutorial-lesson-05
http://quartz-scheduler.org/documentation/quartz-2.x/tutorials/tutorial-lesson-06
http://nurkiewicz.blogspot.com/2012/04/quartz-scheduler-misfire-instructions.html
Configuring Scheduler Misfire Policy | |||||||||||||||||||
Configuration File | |||||||||||||||||||
.../WEB-INF/js.quartz.properties | |||||||||||||||||||
Property | Description | ||||||||||||||||||
report.quartz.misfirepolicy. | Sets the misfire policy for single jobs to one of the following:
| ||||||||||||||||||
report.quartz.misfirepolicy. repeatingsimplejob | Sets the misfire policy for repeating jobs to one of the following values:
| ||||||||||||||||||
report.quartz.misfirepolicy. calendarjob | Sets the misfire policy for jobs with calendar recursion to one of the following values:
|
Configuring Scheduler Failure Notifications
By default, if a scheduled report runs but causes an error, the scheduler sends an email to the schedule owner and to all JasperReports Server administrators in the same organization. This is in addition to any failure notification addresses specified on the Notifications tab of the scheduler wizard. To receive these scheduler failure alerts, administrators must have valid email addresses defined in their user accounts.
You can also configure the scheduler to send failure notifications to different users based on roles, or turn off failure notifications.
Configuring Scheduler Failure Notifications | ||
Configuration File | ||
.../WEB-INF/applicationContext-report-scheduling.xml | ||
Entry Key | Bean | Description |
administrator | quartz | This setting determines the role to which the scheduler failure notifications will be sent. All users in the organization with this role and a valid email address defined in their user profile will receive the email notification. By default, this setting is ROLE_ADMINISTRATOR. |
disableSending | quartz | Disables or allows failure notifications to be sent to the role in the previous setting. By default, this setting is false, meaning that notifications are sent. Set this value to true to disable scheduler failure notifications being sent to administrators (or the role defined above). |
disableSending | quartz | Disables or allows failure notifications to be sent to the schedule owner. By default, this setting is false, meaning that notifications are sent. Set this value to true to disable scheduler failure notifications to the schedule owner. |
Restricting File System Output
The scheduler outputs reports through several channels. Most reports are emailed, but reports can also be written to FTP folders. You can also configure the scheduler to write reports to the server's local file system. This option is disabled by default for security reasons.
If you turn on scheduler file system output, make sure you have configured user and folder access rights to make sure that malicious files cannot be written to your file system. The process that writes the files is the same user that runs the application server hosting JasperReports Server. |
Scheduler File System Output | |
Configuration File | |
.../WEB-INF/applicationContext.xml | |
Property to Update | Description |
enableSaveToHostFS | Set the value from "false" (the default) to "true". When true, the user interface for the scheduler displays active fields that allow the schedule creator to specify a folder in the server's file system. The scheduler will write files to this location every time it runs the schedule for this report. This property also determines the scheduler's overall access to the file system. When true, any schedule configured with a file system folder will write to the file system. When false, no scheduled reports will write output to the file system (FTP and email output are not affected). However, any file system output specified in a schedule remains defined and will again trigger file system output when this property is true again. |
Removing Report Scheduling Interval Options
Users can schedule reports to run at regular intervals. For simple recurrence, the default interval can be expressed in days, hours, or minutes. To prevent users from scheduling frequent reports, you can limit the intervals to days or hours by editing the following configuration file:
Scheduling Interval Options | |
Configuration File | |
.../WEB-INF/flows/reportJobBeans.xml | |
Section to Update | Description |
recurrenceIntervalUnits | Comment out the intervals you want to disable. |
To remove a temporal interval, enclose the corresponding bean in comment characters. For example, to keep users from scheduling reports at minute intervals, comment out the bean containing the INTERVAL_MINUTE field:
Adding a Holiday Exclusion Calendar
The scheduler supports exclusion calendars to specify days or times when no report should be run, even if scheduled. For example, you might not want a report to run on a bank holiday when the financial data would be meaningless.
The scheduler maintains a list of named calendars, and the user interface allows the schedule creator to select a calendar whose dates will be excluded from the schedule.
Currently, the only method to define a holiday calendar is through the REST API. You can use any browser plug-in that acts as a REST client and can send PUT requests to JasperReports Server. Using such a plug-in, compose and send the following REST request (header and body) to your server:
For example, using the Poster plug-in for Firefox, you can submit this request as shown in the following figure. The figure also shows the successful reply from the server.
Creating a Holiday Calendar with REST Web Services |
Then you should see your new calendar in the list of calendars in the Schedule tab.
Selecting a Custom Holiday Calendar in the Scheduler |
The REST API supports other types of calendars, however, the user interface lists only calendars of type holiday. Using the REST API, you can create and manage any number of calendars and update any schedule to use them. For more information, see the JasperReports Server Web Services Guide.
Recommended Comments
There are no comments to display.