How Report Scheduling Works

Users create reports using SAS Web Report Studio. The report definitions (.srx files) are stored in the WebDAV repository or on a file system, and metadata about the reports (including permissions information) is stored in the metadata repository.

Users create schedules for particular reports using SAS Web Report Studio. Information about the scheduled report jobs is stored in the metadata repository. The job information is also passed to the in-process scheduling server or to the Process Manager Server. The command for the job is created using information from the SAS Java Batch server definition.

Jobs and flows are automatically created when the report is scheduled in SAS Web Report Studio. Users can use the Schedule Manager in SAS Management Console to reschedule the flow and change the report schedule.

Depending on the scheduling server used, either the Platform Process Manager server submits the job for execution or the in-process scheduling server submits the job to SAS Web Report Studio for execution at the designated time (or after the designated dependent event).

The Batch Generation Tool, running on the scheduling server, executes the report and places the output in the location designated by the repository (the WebDAV server or the file system). Metadata about the report output is stored in the metadata repository. If you are scheduling using Platform Suite for SAS, information about the job status is stored on the Process Manager Server. Administrators can use Platform Flow Manager to view the status of the job.

If report distribution has been set up, then the report output is also sent to the appropriate destinations when the user bursts the report. For information about report distribution, see “Scheduling and Distributing Pre-generated Reports” in the SAS® 9.2 Intelligence Platform: Web Application Administration Guide.

Users can view the static output by using SAS Web Report Studio (or another application, such as the SAS Information Delivery Portal).