CUSTOMER
December 2017, SAP SE
Deployment Recommendations forSAP Fiori Front-End Server & SAP Fiori Cloud
2CUSTOMER 2017 SAP SE or an SAP affiliate company. All rights reserved.
Change Log
Version ChangesFebruary 2017 Smaller updates
July 2017 S/4HANA option added; SMP option deleted; SFC information added
October 2017 S/4HANA multi release option added
December 2017 Several updates / fixes in the S/4H section; Embedded deployment as generalrecommendation for S/4HANA
3CUSTOMER 2017 SAP SE or an SAP affiliate company. All rights reserved.
This presentation outlines our general product direction and should not be relied on in making a purchasedecision. This presentation is not subject to your license agreement or any other agreement with SAP. SAPhas no obligation to pursue any course of business outlined in this presentation or to develop or releaseany functionality mentioned in this presentation. This presentation and SAP's strategy and possible futuredevelopments are subject to change and may be changed by SAP at any time for any reason withoutnotice. This document is provided without a warranty of any kind, either express or implied, including butnot limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. SAP assumes no responsibility for errors or omissions in this document, except if suchdamages were caused by SAP intentionally or grossly negligent.
Disclaimer
4CUSTOMER 2017 SAP SE or an SAP affiliate company. All rights reserved.
Introduction Methodology & Scope of Landscape Recommendations
Basic Landscape Setups Recommendations for SAP Fiori Using SAP Fiori with S/4HANAAdditional Information SAP Fiori Cloud Using SAP Fiori (Analytical-, Transactional & Factsheet-Apps) with HANA Live Using SAP Fiori Analytical Apps with HANA side-by-side SAP Fiori Mobile Scenarios
Agenda
5CUSTOMER 2017 SAP SE or an SAP affiliate company. All rights reserved.
System Landscapes at CustomersDesigning the Optimal Landscape Layout
Business Aspects
IT Aspects
Product Roadmaps
Technical Documentation(Planning, Installation &
Configuration Guides, etc.)
Deployment Recommendationsfor SAP Products
SLD
Dual Stack
SAPSolution Manager
ABAP
JEE
Solution MngComponent
AS ABAP
ECCServer
SAP ERP
ABAP
ERPComponents
AS ABAP
SRMServer
SAP SRM
ABAP
SRMComponents
AS ABAP
SCMServer
SAP SCM
ABAP
SCMComponents
AS ABAP
CRMServer
SAP CRM
ABAP
CRMComponents
BW
AS ABAP
Business Warehouse
SEM
Central BIContent
ABAP
EP
AS JAVA
BEx Web
JEE
BI JAVA
BICS
PI
PI Dual Stack
Process Integration
ABAP
JEE
ESR&SR
ESR Content
SLD
SolMan Content
SAP NetWeaver Hubs
SAP Business SuiteBackend Systems
EP Core
AS JAVA
Application Portal
JEE
Additional SAP BS Instance
PortalContent
ADOBE
Solution Landscapeof Customer
IntroductionMethodology & Scope of Landscape Recommendations
7CUSTOMER 2017 SAP SE or an SAP affiliate company. All rights reserved.
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 qualities and
cross-product alignment
High-Level Guidancefor optimized
Landscape Layouts
SLD
Dual Stack
SAPSolution Manager
ABAP
JEE
Solution MngComponent
AS ABAP
ECCServer
SAP ERP
ABAP
ERPComponents
AS ABAP
SRMServer
SAP SRM
ABAP
SRMComponents
AS ABAP
SCMServer
SAP SCM
ABAP
SCMComponents
AS ABAP
CRMServer
SAP CRM
ABAP
CRMComponents
BW
AS ABAP
Business Warehouse
SEM
Central BIContent
ABAP
EP
AS JAVA
BEx Web
JEE
BI JAVA
BICS
PI
PI Dual Stack
Process Integration
ABAP
JEE
ESR&SR
ESR Content
SLD
SolMan Content
SAP NetWeaver Hubs
SAP Business SuiteBackend Systems
EP Core
AS JAVA
Application Portal
JEE
Additional SAP BS Instance
PortalContent
ADOBE
Solution Landscapeof Customer
Deployment Recommendationsfor SAP Products
https://uxexplorer.hana.ondemand.com/_item.html?id=11029
8CUSTOMER 2017 SAP SE or an SAP affiliate company. All rights reserved.
Ease Landscape Planning By Stronger GuidanceUsed Methodology
Clear recommendations by categorization of deployment options
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 & cons Customer individual assessment is not compensated
Goal
Consider
Option IOption II
OptionIII
General Recommendationn Best choice for majority of typical
landscape use casesn Recommended by SAPs strategyn Accepted by a wide base of
customersReasonable Alternative
n Useful choice for certain usecases or customer scenarios
n Supported and confirmed bySAPs strategy
Possible Exceptionn Only useful for specific use casesn Supported by SAP, but limitations
might occur
9CUSTOMER 2017 SAP SE or an SAP affiliate company. All rights reserved.
High Level Product Overview (1/2)Make Experience Coherent Across the Enterprise
Provides only on therelevant tasks and
activities for an end user
Finance HumanResources CRM Procurement
10CUSTOMER 2017 SAP SE or an SAP affiliate company. All rights reserved.
High Level Product Overview (2/2)SAP Fiori UX
Concept
Role-based SimpleResponsive Coherent Delightful
TechnologyDesignInformationArchitectureVisual Design
InteractionPatterns
User Interface
Business Logic
Official Fiori Design Guidelines
https://experience.sap.com/guidelines/https://experience.sap.com/guidelines/
11CUSTOMER 2017 SAP SE or an SAP affiliate company. All rights reserved.
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 SAP backend
Considered main building blocks SAP Web Dispatcher serves as Reverse Proxy
Static or Smart Routing possible (details) Fiori Frontend Server (FES) containing
Fiori Applications (UIs) inclusive Fiori Launchpad Content Central UI Technology provides UI5 framework and the Fiori Launchpad (FLP) SAP Gateway optional content and Server (from NW 7.4 or higher SAP_GWFND is
part of the NW stack) If S/4H content is deployed on FES a SAPDB (HANA, MaxDB, ASE) is required
SAP Backend Systems Business Suite (ERP, SRM, CRM, ) on any DB or on HANA
Fiori Backend OData-Integration (via Add-Ons or SPs) Gateway Enablement (from NW 7.40 or higher no need for separate deployment of IW_BEP)
S/4HANA Product specific update dependencies between backend product versions (SPS) and
frontend product versions (SPS)
Example:
SRMServer
SAP SRM
ABAP
GatewayServer
AS ABAP
Fiori Frontend Sever
ABAP
Central GWContent (opt)
Gatewayenabl.
SRM content*
ECCServer
ERP on HANA
HANA
Gatewayenabl.
Suite content*
Web Dispatcher
Central UITechnology
Fiori UIs
Frontend HTML5
SAP CRM
S/4Server
S/4HANA
Gateway enabl.
HANA
S/4H content*
Basic Landscape SetupsRecommendations for Fiori Frontend Server
13CUSTOMER 2017 SAP SE or an SAP affiliate company. All rights reserved.
Deployment of Fiori Frontend Server (FES)Central Hub Deployment Single Backend System per Product
General Recommendationn Deployment of Fiori Apps and UI content on separate systemsn Deployment of the GW components as described in landscape use case II
of the GW landscape deployment recommendationsn Enablement of OData access for multiple SAP Backend systems
Benefitsn Better handling of innovations for Fiori UIs and UI contentn FES deployed as one instance incl. central Fiori Launchpadn Routing mechanism in several backend systemsn Scaling-Up is manageable independent from backend systemn FES can be implemented in segmented networks (e.g. DMZ) to serve security needsn Input validation functions and business logic on two different systems (security requirement)n Central management of connections, central access for devicesn Backend development placed in the system where the data is stored
Considerationsn Additional NW ABAP Systemn User and authorization management to be done in FES and backend, with identical user IDn Web Dispatcher (Reverse Proxy) is mandatory when using analytical Fiori appsn Support of one release-version per product (e.g. not multiple S/4H releases)n Product specific update dependencies between backend product versions (SPS) and
frontend product versions (SPS) might require synchronous updates of FES and backendn If S/4H content is deployed on
