Architecture
1.
The Central Management Server (CMS) checks the CMS system database to determine if a Web
Intelligence document is scheduled to run.
2.
When the scheduled time arrives, the CMS locates an available Web Intelligence Scheduling Service running on an Adaptive Job Server. The CMS sends the schedule request and all information about the request to the Web Intelligence Scheduling Service.
3.
The Web Intelligence Scheduling Service locates an available Web Intelligence Processing Server based on the Maximum Connections value configured on each Web Intelligence Processing Server.
4.
The Web Intelligence Processing Server determines the location of the Input File Repository Server
(FRS) that houses the document and the universe metalayer file on which the document is based.
The Web Intelligence Processing Server then requests the document from the Input FRS. The Input
FRS locates the Web Intelligence document as well as the universe file on which the document is based and then streams them to the Web Intelligence Processing Server.
Note:
This step also requires communication with the CMS to locate the required server and objects.
5.
The Web Intelligence document is placed in a temporary directory on the Web Intelligence Processing
Server. The Web Intelligence Processing Server opens the document in memory. QT.dll generates the SQL from the universe on which the document is based. The Connection Server libraries included in the Web Intelligence Processing Server connect to the data source. The query data passes through
QT.dll
back to the Report Engine in the Web Intelligence Processing Server, where the document is processed. A new successful instance is created.
6.
The Web Intelligence Processing Server uploads the document instance to the Output FRS.
Note:
This step also requires communication with the CMS to locate the required server and objects.
7.
The Web Intelligence Processing Server notifies the Web Intelligence Scheduling Service (on the
Adaptive Job Server) that document creation is completed. If the document is scheduled to go to a destination (file system, FTP, SMTP, or Inbox), the Adaptive Job Server retrieves the processed document from the Output FRS and delivers it to the specified destination(s). Assume that this is not the case in this example.
8.
The Web Intelligence Scheduling Service updates the CMS with the job status.
9.
The CMS updates the job status in its memory, and then writes the instance information to the CMS system database.
3.4.5 Analysis
3.4.5.1 Viewing an SAP Analysis, OLAP edition workspace
85 2012-12-12
Architecture
This workflow describes the process of a user requesting to view an SAP Analysis, OLAP edition workspace from BI launch pad.
1.
The web client sends a request via the web server to the web application server to view a new workspace. The web client communicates with the web application server using DHTML AJAX technology (Asynchronous JavaScript and XML). The AJAX technology allows for partial page updates, so a new page does not have to be rendered for each new request.
2.
The web application server translates the request and sends it to the Central Management Server
(CMS) to determine whether a user is entitled to view or create a new workspace.
3.
The CMS retrieves the user's credentials from the CMS system database.
4.
If the user is allowed to view or create a workspace, the CMS confirms this to the web application server. At the same time, it also sends a list of one or more available Multi-Dimensional Analysis
Service (MDAS).
5.
The web application server picks an MDAS from the list of available choices and sends a CORBA request to the service to find the appropriate OLAP server(s) to create a new, or refresh an existing, workspace.
6.
The MDAS needs to communicate with the Input File Repository Server (FRS) to retrieve the appropriate workspace document that has information about the underlying OLAP database and an initial OLAP query saved with it. The Input FRS retrieves the appropriate Advanced Analyzer workspace from the underlying directory and streams that workspace back to the MDAS.
7.
The MDAS opens the workspace, formulates a query, and sends it to the OLAP database server.
The MDAS has to have an appropriate OLAP database client configured for the OLAP data source.
The translation of the web client query into the appropriate OLAP query needs to occur. The OLAP database server sends the query result back to the MDAS.
8.
The MDAS, based on the request to either create, view, print, or export, pre-renders the result to enable the Java WAS to finish the rendering more quickly. The MDAS sends XML packages of the rendered result back to the web application server.
9.
The web application server renders the workspace and sends the formatted page or portion of the page to the web client via the web server. The web client displays the updated or newly requested page. This is a zero-client solution that does not need to download any Java or ActiveX components.
86 2012-12-12
