Show TOC

Setup of SAP Fiori System Landscape with SAP HANA XSLocate this document in the navigation structure


In the SAP Fiori system landscape with SAP HANA Extended Application Services (SAP HANA XS), you can use transactional and analytical apps.

This system landscape applies to the intranet deployment scenario. When accessing SAP Fiori apps over the Internet, that is, from outside the corporate network, make sure the access is secure. For more information, see Deployment Options.

Set up the system landscape to enable SAP Fiori before you start to implement an app.

The apps require front-end components (providing the user interface and the connection to the back end) and back-end components (providing the data). The front-end components and the back-end components are delivered in separate products and have to be installed in a system landscape that is enabled for SAP Fiori.

The following figures show the detailed system landscape for SAP Fiori analytical apps.

You have the following options:

  • Integrated Scenario

    In this scenario, the ABAP back-end server and the SAP HANA XS server share the same SAP HANA database. No data replication is necessary.

    Figure 1: System Landscape for SAP Fiori Analytical Apps in an Integrated Scenario
  • Side-by-Side Scenario

    In this scenario, the ABAP back-end server with an underlying anyDB is connected with SAP HANA XS on an SAP HANA database via data replication.

    Figure 2: System Landscape for SAP Fiori Analytical Apps in a Side-by-Side Scenario

Components of the System Landscape

Depending on the app type, the following components are used:


To be able to run SAP Fiori apps, the runtime environment (such as the browser) of the client must support HTML5.

SAP Web Dispatcher

The SAP Fiori apps send requests to several systems, depending on the application type and the connected system landscape.

SAP Fiori apps are processed as follows: First, the client loads the UIs for the SAP Fiori apps. Second, while running, the app consumes data from the SAP Business Suite back-end systems.

Standard browsers have a “same origin” policy, that is, HTTPS requests for the UI data and the back-end data must communicate with just one web address.

To meet this requirement, a reverse proxy server between the client and the SAP system must be installed. The reverse proxy server acts as the only point of entry for all HTTPS requests. Depending on the requests that the app sends, the reverse proxy server selects the appropriate application server, the ABAP front-end server, SAP HANA XS, or SAP Gateway server.


We recommend using SAP Web Dispatcher as reverse proxy server.

ABAP Front-End Server

The ABAP front-end server contains all the infrastructure components to generate an SAP Fiori app-specific UI for the client and to communicate with the SAP Business Suite back-end systems. The UI components and the gateway are based on SAP NetWeaver. Typically, both are deployed on the same server.

The central UI component is a framework that provides the common infrastructure for all SAP Fiori apps: SAP Fiori launchpad is the basis of all SAP Fiori UIs, and provides fundamental functions for SAP Fiori apps such as logon, surface sizing, navigation between apps, and role- based app catalogs. End-users access the SAP Fiori apps from the SAP Fiori launchpad. The specific UIs for the apps are delivered as SAP Business Suite product-specific UI add-on products, which must be additionally installed on the front-end server.

The KPI modeling framework enhances the central UI component with parts that the SAP HANA XS server requires for the analytical apps. The KPI modeling framework comprises reusable components with which you can view KPI tiles, a generic drill-down app that provides a standard infrastructure for viewing KPI data and navigating to detail views, and further apps that you can use to create and model KPIs and make them available in the analytical apps.

SAP Gateway handles the communication between the client and the SAP Business Suite back end. SAP Gateway uses OData services to provide back-end data and functions, and processes HTTPS requests for OData services. The transactional apps, which are updating data in the SAP Business Suite systems, use this communication channel when called in an insight-to-action scenario.

ABAP Back-End Server

In the ABAP back-end server, the SAP Business Suite products are installed, which provide the business logic and the back-end data, including users, roles, and authorizations. The add-ons for the SAP Fiori apps are continuously released in Support Packages. The back-end server is based on SAP NetWeaver.


SAP HANA Extended Application Services (SAP HANA XS) is a lightweight application server in SAP HANA providing business content (that is, virtual data models (VDMs)) for analytics.

The VDM acts as a data provider and is a generic interface to the SAP HANA database. This interface consists of query views that are used to analyze KPIs. The VDM is a structured representation of SAP HANA database views used in the SAP HANA analytics framework for SAP Business Suite. VDM is deployed with SAP HANA Live for SAP Business Suite.

SAP HANA XS also acts as a metadata provider, enabling you to view a list of all available KPIs consolidated in the KPI catalog.


SAP HANA is an in-memory database platform that you can use to analyze large volumes of data in real-time.

anyDB stands for any database that stores the data for the back-end server.