Fiori

Provides the end user a single entry point to all Fiori applications that has been

assigned to his / her role.

It is a requirement to access all Fiori apps.

4

Typical high level landscape for Fiori apps: Reverse proxy server

The entry point for HTTP requests, rejects or accepts requests and decides which server

to send accepted requests to.

ABAP front end server Contains all the UI components and SAP NetWeaver Gateway

ABAP backend server Contains the backend business suite and the search model for factsheets

HANA XS Engine Used for all analytical apps

Notice, transactional apps are the only app type that dont have to run on HANA Factsheets, analytical and smart business apps all require HANA, no exceptions.

10

This slide details a landscape in which all the Fiori app types are installed. Notice the progression of the app types.

SAP Web dispatcher is the entry point for HTTP(s) requests. It can reject or accept connections. When it accepts a connection, it selects an appropriate application server and balances the load to ensure an even distribution across the servers.

The complete UI layer consisting of: the central UI add-on contains the SAP UI5 control library and the SAP Fiori launch pad the product-specific UI add-ons contain the UI developments for the respective Business

Suite product, such as ERP-FIN, ERP-SD, ERP-MM, CRM or SCM. the SAP NetWeaver Gateway a development framework, which offers development and

generation tools to create OData services to a variety of client development tools. Put simply, it establishes a connection between SAP Business Suite data and target clients, platforms, and programming framework.

SAP Fiori Support Packs contains new apps released as well as bugs/fixes for existing apps.

ABAP back-end server contains the business logic and the back-end data. The OData service and data model is packaged with the business suite enhancement pack by product.

HANA XS Engine The XS engine contains the Fiori app content and the VDM reuse content. This content is provided

through SAP HANA Live which is included with SAP HANA as a separate package to be installed. Day 4 will cover the analytical and smart business apps in detail

In the upcoming slides we will separate the architectures and look at each app type individually.

11

The SAP Web dispatcher (Reverse Proxy) is the entry point for HTTP(s)

requests. It can reject or accept connections.

The central UI add-on contains the SAP UI5 control library and the SAP Fiori

Launchpad. In addition, the product-specific UI add-ons contain the UI

developments for the respective Business Suite product, such as ERP-FIN,

ERP-SD, ERP-MM, CRM or SCM.

SAP NetWeaver Gateway is a development framework, which offers

development and generation tools to create OData services to a variety of

client development tools. Put simply, it establishes a connection between SAP

Business Suite data and target clients, platforms, and programming framework.

12

Same as the transactional architecture in terms of architecture and components

except the HANA DB is required in order for the search model part of

factsheets to work. The data requested from factsheets is pulled directly from

the HANA Database through the search models.

13

The UI for the Analytical/Smart Business Apps are still rendered via the ABAP

Front-End Server.

The SAP Web Dispatcher is configured to recognized OData for Analytical

Apps. If its request for Analytical / Smart Business Apps, the OData call will get routed directly to HANA XS Engine.

The data for analytical and smart business apps come from HANA through the

XS Engine. SAP Fiori leverages the XS Engine by using virtual data models.

Notice within the XS engine there are 2 components: the HANA Live App

content for the respective business suite and the Smart business component

with the KPI modeler. Within the HANA Live content the VDM reuse content

exists which can be modified for extensibility purposes. The frontend server is

leveraged for analytical apps for the Launchpad and the KPI framework.

14

SAP NetWeaver Gateway facilitates easier provisioning and consumption of

business logic and content of SAP back-end systems for mobile and web

applications. It aims to reduce the complexity and the skill set required to

access SAP data, thereby removing deployment barriers. Simple interfaces

also help to shorten development times.

It is a framework that connects business users to SAP systems using consumer

technologies, groupware, and mobile devices and is based on open standards

(such as the Atom Publishing Protocol and OData) that offer simple services

based on the REST principle.

16

SAP recommends this central hub deployment, especially for productive

deployment. Because in the sandbox you can get away with embedded

deployment for testing purpose.

Documentation is written under the pretense that you used this deployment.

For more details, please review Deployment Options and Embedded

Versus Hub Deployment.*

17

Embedded hub deployment is not recommended by SAP, especially for a

customer with multiple backends. This scenario is usually used for sandbox

purposes only.

18

The NW UI Add-On provides SAP UI Library, renders the Launchpad, and Fiori

foundation for shared control, utilities.

The Product specific UI renders the views and UI part for the Fiori apps.

20

NW Gateway provides the framework which provides development &

generation tools to create & handle OData services via trusted RFC to backend

Business Suite to pull data from target clients. This is where the view &

metadata for the apps reside.

The data provider and model provider makes up the Fiori OData integration in

the backend. Through trusted RFC, provides data from backend business suite

to the apps.

21

HANA Extended Application Services (sometimes referred to unofficially

as XS or XS Engine). The core concept of SAP HANA Extended Application

Services is to embed a full featured application server, web server, and

development environment within the SAP HANA appliance itself. However this

isn't just another piece of software installed on the same hardware as SAP

HANA; instead SAP has decided to truly integrate this new application services

functionality directly into the deepest parts of the SAP HANA database itself,

giving it an opportunity for performance and access to SAP HANA

differentiating features that no other application server has.

22

The SAP HANA Live scenario as delivered contains Private Views which are the base views that directly use the SAP Tables.

The next level of views is the Reuse Views which consist of one or more Private views joined in combination to produce a composite view that forms a reusable unit related to a particular area or function within the system.

The top level of views is the Query Views which consist of one or more Reuse views joined in combination to expose the major attributes and measures that are needed to report on the various business scenarios. These

Query Views are the only views that are exposed to the Client applications .These views/contents can be consumed by Fiori applications through OData

services.

XSE Engine supports OData service definition and development .

23

Download the Installation Guide from http://help.sap.com/Fiori

Approach the prerequisites from Front End and Back End requirements & the

apps which are in scope. Requirements differs for apps in different products.

If customer has or will install NW 7.4 for front end, all NW Central UI Add-On &

NW GW components are included in the installation. No separate installation is

needed.

If customer has NW 7.31 for front end, components for NW Central UI Add-On

and NW GW 2.0 have to be installed separately.

In addition, if customer utilizes Approval Apps, the NW GW component SAP IW

PGW 100 has to be installed.

The principal Wave 1 apps for ERP and SRM only need to meet the minimum

requirements for Wave 1 apps.

HANA database requirements is only required for Fact Sheets & Analytical

Apps.

25

SAP Official Fiori Documentation: SAP Fiori Main Help Page: http://help.sap.com/fiori SAP Service Market Place Download Center: http://service.sap.com/swdc SAP Product Availability Matrix: http://service.sap.com/pam SAP Quick Sizer: http://service.sap.com/quicksizer

Additional Related Information to SAP Fiori: SAP Web Dispatcher

SAP NetWeaver GW 2.0

SCN (SAP Community Network): What is SAP Fiori

SAP for Mobile

27

Development & Implementation: SAP Fiori provided by RIG Workshop schedule, enablement materials, and contacts,

etc.

Fast And Fiorious (Fiori) Enablement & Design Design & development enablement materials. Provided by Development team.

F&F Info-Sessions & Complimentary Curriculum Info sessions relating to SAP Fiori development & design. Provided by Development team.

FIORI Wave 2 documentation (DRAFT VERSION)

GTM & Other Info:

Mobile GTM: SAP Fiori GTM Community

28

Documents

Fiori