Siebel Reports Administration Guide > Reporting in the Siebel Web Clients > About Reports in the Siebel Web Client >

About the System Architecture for Reporting in the Siebel Web Client

The Siebel Reports Server encyclopedia consists of report executables and the user folders. These report executables correspond to the set of available reports among all the views. These executables run in the Siebel Reports Server factory process (a multi-threaded report execution process) at report execution time and generate the report output file (ROI) by obtaining data from the Siebel Object Manager. The report output (ROI) file will be stored in the user folder in the reports encyclopedia and can be accessed from the Siebel Reports Server views in Siebel Business Applications. The report is executed by passing the parameter (ROV) file, which is generated by Siebel Object Manager when the user runs a report from a Siebel Business Applications view.

Figure 4 illustrates the report execution process from the Web Client.

Figure 4. Server-Based Reporting for the Siebel Web Client

The following is the sequence of report generation steps, corresponding to Figure 4:

  1. The report request is submitted by the browser through Siebel Web Services Extension (SWSE) to the Siebel Server.
  2. The Siebel Object Manager (OM) creates and passes a URL for Active Portal with the Siebel Report Server login parameters, and the parameters to generate the report, to the browser.
  3. The browser submits the request to Active Portal.
  4. Active Portal authenticates the user on the Siebel Reports Server and requests the Siebel Reports Server to generate the report.
  5. The Siebel Reports Server runs the report and requests data from the OM through the Siebel Adapter for Actuate.
  6. Data is retrieved by the Siebel OM from the Siebel database and provided to the Siebel Reports Server.
  7. The report initiates using progressive report generation and retrieval. As soon as the first page is ready, the Siebel Reports Server creates the DHTML and starts delivering the report to the browser through Active Portal.
  8. The report in DHTML appears in the Web Client.

The report request submitted from the Web Client includes parameters for the current view, active query, sort specifications, and visibility rules. For reports run in the batch mode (using the Schedule Report option), the status of submitted report requests can be obtained from the Siebel Reports Server views.

Siebel Reports Administration Guide Copyright © 2009, Oracle and/or its affiliates. All rights reserved. Legal Notices.