In this section: Reference: |
The following image shows the ReportCaster components and the processing that takes place when ReportCaster accesses an SQL repository to create, execute, and distribute a scheduled job.
The Distribution Server is a Java application that governs the process of submitting and distributing a scheduled job. You can install the Distribution Server on the same platform as the Reporting Server and the components (which reside on the web or application server), or it can be installed on a different platform.
The Reporting Server processes a scheduled request, retrieves the data, and returns the report to the Distribution Server, which distributes the output. ReportCaster supports multiple Reporting Servers (specified in the ReportCaster Configuration tool), and one Repository (specified in the Client Configuration in the Administration Console).
When you create a ReportCaster schedule, one of the properties of the schedule set by ReportCaster is the next run time (NEXTRUNTIME) for that schedule. The Distribution Server checks for schedules in the Repository that have a next run time less than or equal to the current time. Once the scheduled job runs, the NEXTRUNTIME is updated to the next instance that the schedule is set to run.
The following steps describe what happens when the Distribution Server identifies a schedule to run.
The scheduled job includes distribution information, parameter values, and ReportCaster internal variables (such as schedule ID, schedule procedure name, pre-processing and post-processing procedures, and the user ID (owner ID) that scheduled the job).
Note: You can specify that certain commands are to be run prior to the execution of a scheduled job by using the Universal Profile setting in the WebFOCUS Administration Console. For more information, see the WebFOCUS Security and Administration manual.
WF Server Procedures and Managed Reporting support bursting, which enables you to send portions of a report to specific recipients. If you are distributing a burst tabular report, the burst value is determined by the first BY field. If you are distributing a burst graph report, the burst value is determined by the second BY field. The burst value is automatically determined by the internal matrix. The internal matrix is a memory area that stores each database field value and calculates values referenced by the TABLE or GRAPH request.
Note: The logging process has been modified so that messages are written to the WebFOCUS Repository as they are available, rather than all at once at the end of a schedule. ReportCaster log information is written to the log tables as the schedule progresses. As a result, you can run a log report while a schedule is running to determine how far a schedule has progressed.
Error conditions in log reports appear in red text and warnings appear in orange text.
Error conditions occur for log reports or notification when:
Tip: We recommend using different mail servers for notification and email distribution. Using separate mail servers ensures that you will still receive notifications if the default mail server falters.
In this example, the Distribution Server polls the BOTSCHED table every minute looking for scheduled jobs. However, note that ReportCaster enables authorized users to change the polling interval for the Distribution Server using the Reader interval setting in the Configuration tool. You can specify an interval from 1 to 999999 minutes.
Note: For information about recovering jobs that were placed in the Distribution Server queue but whose NEXTRUNTIME was not updated, see Recovery. For additional schedule considerations, see Time Zone Considerations and Daylight Saving Time Considerations.
Users who access ReportCaster remotely from a different time zone must schedule jobs using the time zone of the machine on which the Distribution Server is located. When viewing job schedules, the displayed date and time is from the time zone of the Distribution Server.
ReportCaster uses Java technology, which always adjusts for Daylight Saving Time, regardless of Windows® settings. If you are in an area that does not observe Daylight Saving Time, scheduled jobs will run at the correct time. However, some internal files will add an hour to time stamps during this period. These files include the following:
When considering the effect of Daylight Saving Time (DST) for jobs scheduled by ReportCaster, the main thing to remember is that 1:59:59 AM is when the time change occurs. As a result, the clock time is set to either 3 AM (when DST begins) or 1 AM (when DST ends).
A simple rule to remember is that regardless of the time change, the schedule interval stays the same. This is because the schedule run time is based on elapsed time rather than the actual clock time.
The following table lists and describes the expected behavior for jobs scheduled by ReportCaster when Daylight Saving Time is in effect.
Interval |
Description |
For example: |
---|---|---|
Schedule is set to run once at a specific time, or to run every day, week, month, or year. |
The schedule runs at that time, regardless of the time change. |
A 9:15 AM schedule will still run at 9:15 AM. |
Schedule is set to run every minute or hour when DST begins. |
The schedule is advanced by 1 hour. |
A schedule that runs every 2 hours: 12:00 PM, 2:00 AM, 4:00 AM, and so on. Will run at the following times: 12:00 PM, 3:00 AM, 5:00 AM, and so on. This occurs because at 1:59:59 AM, the clock is set ahead to 3:00 AM. |
Schedule is set to run every minute or hour when DST ends. |
The schedule is set back 1 hour. |
A schedule that runs every 2 hours: 12:00 PM, 2:00 AM, 4:00 AM, and so on. Will run at the following times: 12:00 PM, 1:00 AM, 3:00 AM, and so on. This occurs because at 1:59:59 AM, the clock is set back to 1:00 AM. |
WebFOCUS |