System Landscape Recommendations for SAP Fiori

8/20/2019 System Landscape Recommendations for SAP Fiori

http://slidepdf.com/reader/full/system-landscape-recommendations-for-sap-fiori 1/26

Landscape Deployment Recommendations f

SAP Fior i Front-End Server

New Rollout Channel

The rollout channel for publishing landscape deployment recommendations c

Please have a look at our announcement.

You will find the newest version of this document here:

SAP Fiori Front-End Server

Disclaimer

This presentat ion out l ines our general product di rec t ion and sho uld n ot be rel ied o

purc hase decis ion. This presentat ion is no t subject to you r l icense agreement or aagreement with SAP. SAP has no ob l igat ion to purs ue any cours e of business o ut l

presentat ion or to d evelop or release any funct io nal i ty ment ion ed in this presenta

presentat ion and SAP's strategy and po ssible future developments are subject to

be changed by SAP at any t ime for any reason wi thout no t ice. This document is pr

warranty of any kind, ei ther express or impl ied, includ ing but no t l imi ted to, the im

of merch antabi l i ty , f i tness for a part icular purpo se, or no n- infr ingement. SAP assu

respons ib i l ity for er rors or om iss ions in th is d ocum ent , except i f such damages w

SAP intent ion al ly or grossly negl igent.

Agenda

Introduction

Methodology & Scope of Landscape Recommendations

Basic Landscape Setups

Recommendations for SAP Fiori

Additional Information

Using SAP Fiori (Analytical-, Transactional & Factsheet-Apps) with HANA Live

Using SAP Fiori Analytical Apps with HANA side-by-side

SAP Fiori mobile scenarios

IntroductionMethodology & Scope of Landscape Recommendations

System Landscapes at CustomersDesigning the Optimal Landscape Layout

Business Aspects

OperationsCosts

Speed of

Innovation

Security

ArchitecturalStrategy

Performance &Scalability

Legal Aspects

OS/DB platformstrategy

SLA &Availability

IT Aspects

Product Roadm

Technical Do(Planning, I

Configuration

Dual Stack

Solution Manager

Solution Mng

Component

AS ABAP

ECCServer

SAP ERP

Components

AS ABAP

SRMServer

SAP SRM

Components

AS ABAP

SCMServer

SAP SCM

Components

AS ABAP

CRMServer

SAP CRM

Components

AS ABAP

Business Warehouse

Central BI

Content

AS JAVA

BEx Web

BI JAVA

PI Dual Stack

Process Integration

ESR&SR

ESR Content

SolMan Content

SAP NetWeaver Hubs

SAP Business Suite

Backend Systems

EP Core

AS JAVA

Application Portal

Additional SAP BS Instance

Portal

Content

Solution Landscape

of Customer

Deployment Recommendations for SAP ProductsGuiding Principles

Allow flexibility by offering different deployment options (not one-size-fits-all)

Provide guidance by rating different options

Ease decisions by listing pros & cons

Simplify consumption of information by using a common methodology

Increase reliability by considering SAP product strategy, achieved landscape qual

cross-product alignment

High-Level Guidance

for optimized

Landscape Layouts

Dual Stack

Solution Manager

Solution Mng

Component

AS ABAP

Server

SAP ERP

Components

AS ABAP

Server

SAP SRM

Components

AS ABAP

Server

SAP SCM

Components

AS ABAP

Server

SAP CRM

Components

AS ABAP

Business Warehouse

Central BI

Content

AS JAVA

BEx Web

BI JAVA

PI Dual Stack

Process Integration

ESR&SR

ESR Content

SolMan Content

SAP NetWeaver Hubs

SAP Business Suite

Backend Systems

EP Core

AS JAVA

Application Portal

Additional SAP BS Instance

PortalContent

Solution Landscape

of Customer

Deployment R

for SAP

Ease Landscape Planning By Stronger GuidanceUsed Methodology

Clear recommendations by categorization of deployment

Outlining main important aspects

Optimal trade-off between flexibility and simplicity

Applied to main building blocks of SAP products

Alternative deployment options typically have different pros & c

Customer individual assessment is not compensated

Consider

Option IOption II

Option

IIIGeneral Recommend

Best choice for major

landscape use cases

Recommended by SA

Accepted by a wide b

customersReasonable Alternative

Useful choice for certain use

cases or customer scenarios Supported and confirmed by

SAP’s strategy

Possible Exception

Only useful for specific use cases

Supported by SAP, but limitations

might occur

High Level Product Overview (1/2)Make Experience Coherent Across the Enterprise

Provides only on the

relevant tasks andactivities for an end user

FinanceHuman

Resources CRM Procureme

High Level Product Overview (2/2)SAP Fiori UX

Concept

Role-based SimpleResponsive Coherent Delightful

TechnologyDesign

Information

ArchitectureVisual Design

Interaction

Patterns

User Interf

Business L

Scope of Landscape RecommendationsBuilding Blocks in System Landscapes for SAP Fiori

Considered main usage scenarios Enables SAP Fiori apps

Enables general UI5 framework content Enables consumption of ODATA-Services from

Considered main building blocks SAP Web Dispatcher serves as Reverse Proxy

Fiori Frontend Server (FES) containing Fiori Applications (UIs) inclusive Fiori Launchpad Cont

Central UI Technology provides UI5 framework and th

SAP Gateway content and Server (from NW 7.4 or higNW stack)

SAP Backend Systems Suite on any DB

Fiori Backend OData-Integration (via Add-Ons or SP

Gateway Enablement (from NW 7.40 or higher no nee

ERP, CRM, SRM on HANA Fiori Backend OData-Integration (via Add-Ons or SP

Gateway Enablement (from NW 7.40 or higher no nee

Example:

Fiori UI5 Applications

UI5 Applications following the Fiori development paradigm:

• Decoupling of UI (frontend) and business logic (backend)

• SAP Fiori UIs and OData services must be defined in different software components

• Synchronous Update not required

• Interoperability between UI and backend artefacts is ensured

• One SAP Fiori app - One dedicated oData service

• SAP Fiori UIs are built with SAPUI5

Examples:

• All SAP delivered Fiori applications e.g. People Profile, Request for Others

Basic Landscape SetupsRecommendations for Fiori Frontend Server (FES)

Deployment of Fiori Frontend Server (FES)Central Hub Deployment

General Recommendation

Deployment of Fiori Apps and UI content on separate systems

Deployment of the GW components as described in landscape us

of the GW landscape deployment recommendations Enablement of OData access for multiple SAP Backend systems

Benefits

Fiori UI Software Update cycles decoupled from backend sys

Better handling of innovations for Fiori UIs and UI content

FES deployed as one instance incl. central Fiori Launchpad

Routing mechanism in several backend systems

Scaling-Up is manageable independent from backend system

FES can be implemented in segmented networks (e.g. DMZ) Input validation functions and business logic on two different

Central management of connections, central access for devic

Backend development placed in the system where the data is

Considerations

Additional NW ABAP System

Web Dispatcher (Reverse Proxy) is mandatory when using a

Example:

Deployment of Fiori Frontend Server (FES) Add-on Deployment in Application Backend System

Possible Exception

Deployment of needed Fiori UI content on each requir

SAP Backend system (ERP, CRM etc.)

Multiple deployment/configuration of Gateway Server aGateway content (on each SAP Backend)

Acceptable for single system infrastructures e.g. Proof

productive systems (starting point for Fiori)

Benefits

No additional NW ABAP system needed less TCO

Less runtime overhead no remote-call

Direct access to metadata and business data

Later scale-out to central hub deployment possible

Considerations

Innovation speed of Fiori UI/GW and backend must be

Update strategy must reflect dependencies between s

Cross-System composition (e.g. usage of one Fiori La

SAP Backend must fulfill minimum system-requiremen

Possible scale-up of SAP backend (resizing)

Currently the majority of customers are on central hub

Example:

Landscape Use-CasesBest practice usage scenarios

Fiori Architecture ScenariosUsing Fiori (Transactional, Analytical & Factsheets) in an HANA Embe

General Recommendatio

Best suited scenario for Suite on HANA systems (Business

HANA XS enables direct ODATA access from WebDispatch

Benefits

Analytical apps run on HANA, executed and exposed

Usage of all Fiori Application types (incl. Search Func

Usage of HANA based virtual data models (VDMs)

Usage of SAP Smart Business KPI Framework

Considerations

Access to analytical apps only in an intranet scenario

Installation of HANA Live architecture

Example:

Fiori Architecture ScenariosUsing Fiori Analytical Apps with SAP HANA side-by-side with SAP Bus

Possible Exception

Data replication via SLT from SAP ERP system to HAN

HANA XS enables direct ODATA access from WebDisp

Benefits

Usage of Fiori analytical apps with SAP HANA si

Real time access on business data

Transition infrastructure to Suite on HANA or S/4

Considerations

Setup of SLT process, data replication required

Possible scale-up of existing HANA DB

Currently external access is only recommended b Application Firewall

More complex landscape setup

No Search functionality possible

Example:

Gateway

Server

AS ABAP

SAP FES

Central GWContent (opt)

Web Dispatcher

Central UITechnology

Fiori UIs for ERP

Frontend – HTML5

HTTP/ODATA

SAP HANA

XS Server

Fiori AppContent

HTTP/ODATA

ECC Server

SAP ERP

Gatewayenabl.

ERP content*

SAP CRM

SLTREPLICATION

S/4HANA Fiori ScenariosExtended landscape scenarios

Fiori Architecture Scenariosusing Fiori within a SAP S/4HANA on premise integration scenario

Integration landscape (S

Typical starting point for S/4H customers is an integrat

an existing enterprise infrastructure

Similar to the strategy before S/4H, the same benefits embedded or hub deployment of the Fiori FES are valid

Benefits

Easy integration of an S/4H system in an existingFiori FES

The additional S/4H UI content must simply be de

No more XS content (VDMs) – all analytics in S/4(Core Data Services), as a result no direct http chDispatcher to HANA XS is required anymore

Considerations

All systems with S/4H Fiori content must run on a

FES must be on min. NW 7.50

Currently there is a strict dependency between SAbackend release version and SP

Example:

S/4H Core

GatewayServer

AS ABAP onSAP DB*

SAP FES

Central GW

Content (opt)

Gatewayenabl.

sFinancials

Web Dispatcher

Central UI

Technology

Fiori UIs for ERP

Frontend – HTML5

HTTP/ODATA

SAP HANA for S/4 SystemHANA

Search

PRIMARY DBCONNECTION

SAP HANA for ERP System HANA

S/4 Fiori UIs*

ECCServer

ERP on HANA

Gatewayenabl.

Suite content*

Search

* if S/4 content isdeployed on FES

a SAP DB ismandatory

Fiori Mobile ScenariosExtended landscape scenarios

Fiori Architecture ScenariosUsing Fiori with SAP HCP Mobile Services (HCPms)

Extended Landscape Option

HCPms as Service on HANA Cloud Platform

Starting point for more HCP services like Web IDE, Mo

Mobile Secure

Benefits

Easy access to HCPms features via Cloud subsc

Secure channel from HCP to SAP system via Clo

Usage of special mobile features like Fiori offline

SMP administration cockpit with e.g. Application

Logging and Tracing features

Considerations

Setup of Cloud Connector to access backend da

Example:

Server

SAP ERP on HANA

Gateway

Server

AS ABAP

SAP FES

Gateway

enabl.

ERP content*

Fiori UIs for ERP

Frontend – HTML5

XS Engine

Fiori AppContent

HTTP/ODATA

SAP HANA System for SAP ERPHANA

VDM Reuse

Content

Search

Web Dispatcher

HTTP/ODATA

Cloud Connector

Internet

Fiori Architecture ScenariosUsing Fiori with SAP Mobile Platform (SMP)

Extended Landscape Option (o

SAP Mobile Platform as part of on premise landscape

SAP Mobile Platform as entry point for all Fiori internet

Benefits

Usage of Fiori Client App with SMP and additiona

Usage of special mobile features like Fiori offline

Additional security layer in front of SAP Fiori Fron

SMP administration cockpit with e.g. Application

Logging and Tracing features

Considerations

Additional SMP system in Fiori landscape

Additional installation of SMP

Example:

ECCServer

SAP ERP on HANA

GatewayServer

AS ABAP

SAP FES

Gatewayenabl.

ERP content*

Web Dispatcher + Web Application Firewall

Fiori UIs for ERP

Frontend – HTML5

HTTP/ODATA

XS Engine

Fiori AppContent

HTTP/ODATA

VDM ReuseContent

Search

SAP Mobile Platform

Web Dispatcher

HTTP/ODATA

Internet

Fiori Architecture ScenariosUsing Fiori mobile with SAP Authenticator without Mobile Platform

Extended Landscape Option (o

Usage of SAP Authenticator as SSO solution for Fiori

Usage of Device Browser or Fiori Client App (prepared

usage with SAP Authenticator)

Benefits

Easy to implement SSO solution based on SAML

Mobile SSO is available with SAP Single Sign-On 2.0 SP04

Onboarding/Registration via QR-Code

Deployment of SSO Library e.g. on Java based Enterprise

Easy to integrate in existing landscape infrastruc

Considerations

No SAP Mobile Platform features like Offline etc.

SAP SSO 2.0 has a separate licensing

Example:

Server

SAP ERP on HANA

Gateway

Server

AS ABAP

SAP FES

Central GW

Content (opt)

Gateway

enabl.

ERP content*

Web Dispatcher + Web Application Firewall

Central UI

Technology

Fiori UIs for ERP

XS Engine

Fiori AppContent

HTTP/ODATA

VDM ReuseContent

Search

Web Dispatcher

HTTP/ODATA

Internet

Mobile Device

SAP Authenticator App

SSO Library

Thank you

Contact information:

F name MI. L name

Address

Phone number

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP SE or an S

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SA

company) in Germany and other countries. Please see http://global12.sap.com/corporate-en/legal/copyright/index.epx for additional tradema

Some software products marketed by SAP SE and its distributors contain proprietary software components of other software vendors.

National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or warranty of a

affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate c

services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein sho

constituting an additional warranty.

In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or any related

or release any functionality mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategydevelopments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated

for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, cod

looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Reade

undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purcha

System Landscape Recommendations for SAP Fiori

Documents

Week 2: User Experience in SAP S/4HANA Unit 1: SAP Fiori ...€¦ · Roadmap of SAP Fiori SAP Fiori 2013 SAP Fiori 2.0 2016 SAP Fiori 3 SAP CoPilot SAP Business Suite ... National

LandsCape proteCtion & ManageMent - Planning · LandsCape proteCtion & ManageMent The implementation recommendations for the South West Victoria Landscape Assessment Study represent

Bellissimi fiori

System Landscape Recommendations for SAP Master …Deployment Recommendations for SAP Master Data Governance 7.0 SAP AG, ... Recommendations for SAP Master Data Governance 7.0 .

Landscape Deployment Recommendations ForSAP FioriFront-End Server

Cultural Heritage, Landscape & Rural Development · 2018. 9. 14. · Cultural Heritage, Landscape & Rural Development Good Practice, Methodology, Policy Recommendations & Guidelines

Ge fiori

Consegna fiori invia fiori online fioriflor.com

System Landscape Recommendations for SAP Master Data Governance 7.0

LANDSCAPE TREE RECOMMENDATIONS FOR THE … … · landscape tree recommendations for the eastern united states . btrl sr-06 2 latin name/ common name zone ht comments acer buergeranium

Katalog Fiori

System Landscape Recommendations for SAP NetWeaver Gateway

Key Elements and Recommendations for the Integration of Parkour in Landscape and Design

System Landscape Recommendations for SAP Fiori...Innovation speed of Fiori UI/GW and backend must be synchronized Update strategy must reflect dependencies between software components

SAP Fiori Launchpad - NOVO€¦ · SAP Fiori Apps für SAP Business Suite. SAP Fiori für SAP S/4HANA 1511. SAP Fiori für SAP S/4HANA 1610. SAP Fiori für SAP S/4HANA 1709. SAP Fiori

Sapx03 Fiori

Recommendations for landscape-level adaptive management

Cultural Heritage Landscape Assessment & Recommendations · conjecture rather than heritage research and analysis using accepted landscape assessment methods. This document provides

SAP Fiori Apps Recommendations Report€¦ · The SAP Fiori design language can be implemented through various UI technologies and platforms. SAP Fiori covers: Design • Design principles,

System Landscape Recommendations for Ariba Network Integration 1.0 for SAP Business Suite