The communication between Dashboards/Dashboards/Xcelsius and BW is handled by BICS remote web service. At design time the web service provides query information and stores the dashboard on the BW server. At runtime, the BEx Web runtime provides a link to the SWF file representing the dashboard. The SWF file is loaded by the browser and it calls the web service that provides the BW query data (and master data) in an XML format. The web service accesses the query data via BICS (BI Consumer Services).

The overall architecture consists of three major building blocks:

  • The Dashboards/Xcelsius standalone tool
  • The BI Java Stack or Business Objects Enterprise (envisioned in a second step)
  • The SAP ABAP Stack

XcBicsWs_designTime_final.png

Dashboards/Xcelsius reuses the BEx Analyzer Open/Save Dialogs which communicate with the SAP BW via the RFC protocol. Over these dialogs it is possible to browse for queries and to store the dashboard.

The dashboard consists of three components. The XLF file which represents the dashboard source, the SWF which is the Runtime version and the TXT that externalizes all texts which later on need to be translated. In addition to this also references to bound DataProvider objects over various BI query connections need to be stored. The reason of this is to find all dependent objects when for example one object is moved to another system.

During the design of a dashboard that uses the BI query connection the user gets help about the contained characteristics in a query. This information is obtained via the BICS Web Service that is based on HTTP/SOAP. Logon data needs to be passed to the Web Service in order to connect the ABAP backend.

Within the BICS there is a part that controls and manages the data access and a part that provides the possibility to browse for BI objects like queries, key figures and so on – the BICS Object Services. The BICS Object Services part is not used at DesignTime due to project time constraints. Nonetheless that part is needed at Runtime to deliver the Launcher. BICS uses the JCO to communicate with ABAP.

XcBicsWs_runTime_final.png

In the ABAP backend the OLAP processor provides the data and the TLOGO framework provides transport facilities. The dashboard can either be saved in the ABAP stack or in the local file system. Texts that are marked for translation are always stored in the ABAP stack.

Advantages of this integration are as follows:

  • Makes it possible to consume SAP BW data within Dashboards/Xcelsius in an easy and comparable workflow as already existing for other data sources.
  • Model the Xcelsius dashboard as TLOGO object that it can be transported in the Abap system landscape.
  • Connect the existing backend translation workflow with the dashboard to provide locale specific presentations for text and data.

Design time analysis for these dashboards can be done in the BW backend. Without the dashboard designer client tool, basic information like connections and UI components used in the dashboard can be obtained directly from the backend.

1. Run ST13 transaction and run ‘BW-TOOLS’

X1.png

2. Select Dashboard analysis radio button and hit run

X2.png

3. Enter technical name for dashboard or choose local XLF file:

X3.png

Export the report in HTML or other available formats. This file will contain the design time properties of the dashboard:

X4.png



To report this post you need to login first.

1 Comment

You must be Logged on to comment or reply to a post.

Leave a Reply