This section describes the viewing mechanisms that are implemented in InfoView. The processing flow for custom applications may differ.
When you view a report through BusinessObjects Enterprise, the processing flow varies depending upon your default report viewer, the type of report, and the rights you have to the report. In all cases, however, the request that begins at the web server must be forwarded to the application server.
The actual request is constructed as a URL that includes the report's unique ID. This ID is passed as a parameter to a server
Different report viewers require different viewing mechanisms:
report_view_dhtml.aspx.
When evaluated by the application server, this script communicates with the framework (through the published SDK interfaces) in order to create a viewer object and retrieve a report source from the Cache Server and Page Server.
report_view_advanced.aspx.
When evaluated by the application server, this script communicates with the framework (through the published SDK interfaces) in order to create a viewer object and retrieve a report source from the Report Application Server.
viewrpt.aspx, hosted by the WCA.
The Crystal Web Request is executed internally through viewer code on the application server. The viewer code communicates with the framework in order to retrieve a report page (in .epf format) from the Cache Server and Page Server.
If they haven't already done so, users are prompted to download and install the appropriate viewer software.
Click the appropriate link to jump to that section:
| Business Objects http://www.businessobjects.com/ Support services http://www.businessobjects.com/services/support/ Product Documentation on the Web http://support.businessobjects.com/documentation/ |