Setup of SAP Fiori System Landscape for SAP Business Suite

Use

This section contains the specific information and tasks that you need to set up the SAP Fiori system landscape for SAP Business Suite.

There are mandatory additional tasks that you have to perform, such as installing the components, setting up the communication channels, or setting up user authentication and single sign-on (SSO). For more information, see Setup of SAP Fiori System Landscape at http://help.sap.com/fiori_implementation.

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

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 software components and have to be installed in a system landscape that is enabled for SAP Fiori.

The following figure shows the detailed system landscape for SAP Fiori apps.

Figure 1: System Landscape for SAP Fiori Apps

Components of the System Landscape

Depending on the system landscape, the following components are used:

Client

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

SAP Web Dispatcher (Fact Sheets)

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 or the SAP Gateway server.

Note

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.

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.

ABAP Back-End Server

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

Database

SAP HANA is an in-memory database platform that you can use to analyze large volumes of data in real-time. An SAP HANA Database is required for all fact sheets.

anyDB stands for any database that stores the data for the back-end server. For most transactional apps, any database can be deployed instead of SAP HANA.