Architecture
6.
ProcReport.dll
starts crpe32.dll, which processes the report according to the parameters passed.
7.
While crpe32.dll is still processing the report, records are retrieved from the data source as defined in the report.
8.
The Crystal Reports 2011 Scheduling Service updates the CMS periodically with the job status. The current status is Processing.
9.
Once the report is compiled into the memory of the Crystal Reports 2011 Scheduling Service, it may be exported to a different format, such as Portable Document Format (PDF). When exporting to
PDF, crxfpdf.dll is used.
10.
The report with saved data is submitted to the scheduled location (such as email), and then it is sent to the Output FRS.
Note:
This step also requires communication with the CMS to locate the required server and objects.
11.
The Crystal Reports 2011 Scheduling Service updates the CMS with the job status. The current status is Success.
12.
The CMS updates the job status in its memory and then writes the instance information to the CMS system database.
3.4.4 Web Intelligence
3.4.4.1 Viewing an SAP BusinessObjects Web Intelligence document on demand
This workflow describes the process of a user viewing an SAP BusinessObjects Web Intelligence document on demand to see the latest data. For example, from the Web Intelligence viewer in BI launch pad.
1.
A web browser sends the view request to the web application server via the web server.
2.
The web application server interprets the request and determines that it is a request to view a Web
Intelligence document. The web application server sends a request to the Central Management
Server (CMS) to ensure that the user has sufficient rights to view the document.
3.
The CMS checks the CMS system database to verify the user has sufficient rights to view the document.
4.
The CMS sends a response to the web application server to confirm the user has sufficient rights to view the document.
5.
The web application server sends a request to the Web Intelligence Processing Server, requesting the document.
83 2012-12-12
Architecture
6.
The Web Intelligence Processing Server requests the document from the Input File Repository
Server (FRS) as well as the universe file on which the requested document is built. The universe file contains metalayer information, including row-level and column-level security.
7.
The Input FRS streams a copy of the document to the Web Intelligence Processing Server, as well as the universe file on which the requested document is built.
Note:
This step also requires communication with the CMS to locate the required server and objects.
8.
The Web Intelligence Report Engine (on the Web Intelligence Processing Server) opens the document in memory and launches QT.dll and a Connection Server in process.
9.
QT.dll
generates, validates, and regenerates the SQL and connects to the database to run the query. The Connection Server uses the SQL to get the data from the database to the Report Engine where the document is processed.
10.
The Web Intelligence Processing Server sends the viewable document page that was requested to the web application server.
11.
The web application server sends the document page to the web client via the web server, where the page is rendered and displayed
3.4.4.2 Setting a schedule for an SAP BusinessObjects Web Intelligence document
This workflow describes the process of a user scheduling an SAP BusinessObjects Web Intelligence document to be run at a future time from a web application such as the Central Management Console
(CMC) or BI launch pad.
1.
The web client submits a schedule request in a URL via the web server to the web application server.
2.
The web application server interprets the URL request and determines that the request is a schedule request. The web application server sends the schedule time, database login values, parameter values, destination, and format to the specified Central Management Server (CMS).
3.
The CMS ensures that the user has rights to schedule the object. If the user has sufficient rights, the CMS adds a new record to the CMS system database. The CMS also adds the instance to its list of pending schedules.
4.
The CMS sends a response to the web application server to let it know that the schedule operation was successful.
5.
The web application server generates the next HTML page and sends it via the web server to the web client.
84
3.4.4.3 A scheduled SAP BusinessObjects Web Intelligence document runs
This workflow describes the process of a scheduled SAP BusinessObjects Web Intelligence document running at a scheduled time.
2012-12-12
