BusinessObjects Enterprise Administrator's Guide

Viewing Web Intelligence documents

This section describes the process for viewing a Web Intelligence document.

1. InfoView sends the request to the web application server.
2. The web application server sends the request to the application server, which creates a new session with the Web Intelligence Report Server.
3. The Web Intelligence Report Server checks if the user has rights to use the Web Intelligence application.
4. The web application server then sends the request to the Web Intelligence Report Server.
5. The Web Intelligence Report Server contacts the CMS to check whether the user has the right to view the document, and to check when the document was last updated.
6. If the user has the right to view the document, the Web Intelligence Report Server checks whether it has up-to-date cached content for the document.
7. If cached content is available, the Web Intelligence Report Server sends the cached document information to the SDK.

If cached content is not available, the following happens:

1. The Web Intelligence Report Server obtains the document information from the CMS and checks what rights the user has on the document.
2. The Web Intelligence Report Server obtains the Web Intelligence document from either the Input or Output File Repository Server and loads the document file.

Note:    Which FRS is used depends on whether the request was for a Web Intelligence document that was saved to BusinessObjects Enterprise or for an instance of the document. Documents are stored on the Input FRS. Instances are generated when an object is run according to a schedule, and they are stored on the Output FRS.

3. If the document is set to "refresh on open" and the user has the View On Demand rights, the Web Intelligence Report Server refreshes the data in the document with data from the database.

Note:    If the document is set to "refresh on open" but the user does not have View On Demand rights, an error message is displayed.

4. The Web Intelligence Report Server stores the document file and the new document information in cache.
5. The Web Intelligence Report Server sends the document information to the SDK.
8. The viewer script calls the SDK to get the requested page of the document. The request is passed to the Web Intelligence Report Server.
9. If the Web Intelligence Report Server has cached content for the page, it returns the cached XML to the SDK.

If the Web Intelligence Report Server does not have the cached content for the page, it renders the page to XML using the current data for the document. It then returns the XML to the SDK.

10. The SDK applies an XSLT style sheet to the XML to transform it to HTML.
11. The viewer script returns the HTML to the browser.