landscape deployment recommendations forsap fiorifront-end server
DESCRIPTION
Landscape Deployment Recommendations ForSAP FioriFront-End ServerTRANSCRIPT
Landscape Deployment Recommendations for
SAP Fiori Front-End Server
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 2Customer
New Rollout Channel
The rollout channel for publishing landscape deployment recommendations changed.
Please have a look at our announcement.
You will find the newest version of this document here:
SAP Fiori Front-End Server
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 3Customer
Disclaimer
This presentation outlines our general product direction and should not be relied on in making a
purchase decision. This presentation is not subject to your license agreement or any other
agreement with SAP. SAP has no obligation to pursue any course of business outlined in this
presentation or to develop or release any functionality mentioned in this presentation. This
presentation and SAP's strategy and possible future developments are subject to change and may
be changed by SAP at any time for any reason without notice. This document is provided without a
warranty of any kind, either express or implied, including but not 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 such damages were caused by
SAP intentionally or grossly negligent.
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 4Customer
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
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 6Customer
System Landscapes at CustomersDesigning the Optimal Landscape Layout
Business Aspects
Operations
Costs
Speed of
Innovation
Security
Architectural
Strategy
Performance &
ScalabilityLegal Aspects
…
OS/DB platform
strategy
SLA &
Availability
IT Aspects
Product Roadmaps
Technical Documentation(Planning, Installation &
Configuration Guides, etc.)
Deployment Recommendations
for SAP Products
SLD
Dual Stack
SAP
Solution Manager
ABAP
JEE
Solution Mng
Component
AS ABAP
ECC
Server
SAP ERP
ABAP
ERP
Components
AS ABAP
SRM
Server
SAP SRM
ABAP
SRM
Components
AS ABAP
SCM
Server
SAP SCM
ABAP
SCM
Components
AS ABAP
CRM
Server
SAP CRM
ABAP
CRM
Components
BW
AS ABAP
Business Warehouse
SEM
Central BI
Content
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 Suite
Backend Systems
EP Core
AS JAVA
Application Portal
JEE
Additional SAP BS Instance
Portal
Content
ADOBE
Solution Landscape
of Customer
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 7Customer
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 Guidance
for optimized
Landscape Layouts
SLD
Dual Stack
SAP
Solution Manager
ABAP
JEE
Solution Mng
Component
AS ABAP
ECC
Server
SAP ERP
ABAP
ERP
Components
AS ABAP
SRM
Server
SAP SRM
ABAP
SRM
Components
AS ABAP
SCM
Server
SAP SCM
ABAP
SCM
Components
AS ABAP
CRM
Server
SAP CRM
ABAP
CRM
Components
BW
AS ABAP
Business Warehouse
SEM
Central BI
Content
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 Suite
Backend Systems
EP Core
AS JAVA
Application Portal
JEE
Additional SAP BS Instance
Portal
Content
ADOBE
Solution Landscape
of Customer
Deployment Recommendations
for SAP Products
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 8Customer
Ease Landscape Planning By Stronger Guidance Used 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
Option
IIIGeneral Recommendation
Best choice for majority of typical
landscape use cases
Recommended by SAP’s strategy
Accepted by a wide base of
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
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 9Customer
High Level Product Overview (1/2)Make Experience Coherent Across the Enterprise
Provides only on the
relevant tasks and
activities for an end user
FinanceHuman
Resources CRM Procurement
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 10Customer
High Level Product Overview (2/2)SAP Fiori UX
Concept
Role-based SimpleResponsive Coherent Delightful
TechnologyDesign
Information
ArchitectureVisual Design
Interaction
Patterns
User Interface
Business Logic
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 11Customer
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
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 content and Server (from NW 7.4 or higher SAP_GWFND is part of the NW stack)
SAP Backend Systems Suite on any DB
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)
ERP, CRM, SRM 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)
Example:
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 12Customer
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 etc.
Basic Landscape SetupsRecommendations for Fiori Frontend Server (FES)
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 14Customer
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 use case II
of the GW landscape deployment recommendations
Enablement of OData access for multiple SAP Backend systems
Benefits
Fiori UI Software Update cycles decoupled from backend system
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) to serve security needs
Input validation functions and business logic on two different systems (security requirement)
Central management of connections, central access for devices
Backend development placed in the system where the data is stored
Considerations
Additional NW ABAP System
Web Dispatcher (Reverse Proxy) is mandatory when using analytical Fiori apps
Example:
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 15Customer
Deployment of Fiori Frontend Server (FES)Add-on Deployment in Application Backend System
Possible Exception
Deployment of needed Fiori UI content on each required
SAP Backend system (ERP, CRM etc.)
Multiple deployment/configuration of Gateway Server and
Gateway content (on each SAP Backend)
Acceptable for single system infrastructures e.g. Proof of Concepts or very small
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 synchronized
Update strategy must reflect dependencies between software components
Cross-System composition (e.g. usage of one Fiori Launch Pad) is not advisable
SAP Backend must fulfill minimum system-requirements
Possible scale-up of SAP backend (resizing)
Currently the majority of customers are on central hub deployment
Example:
Landscape Use-CasesBest practice usage scenarios
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 17Customer
Fiori Architecture ScenariosUsing Fiori (Transactional, Analytical & Factsheets) in an HANA Embedded Scenario
General Recommendation
Best suited scenario for Suite on HANA systems (Business Suite 7)
HANA XS enables direct ODATA access from WebDispatcher
Benefits
Analytical apps run on HANA, executed and exposed via XS Engine
Usage of all Fiori Application types (incl. Search Functionality)
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 recommended
Installation of HANA Live architecture
Example:
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 18Customer
Fiori Architecture ScenariosUsing Fiori Analytical Apps with SAP HANA side-by-side with SAP Business Suite
Possible Exception
Data replication via SLT from SAP ERP system to HANA DB
HANA XS enables direct ODATA access from WebDispatcher
Benefits
Usage of Fiori analytical apps with SAP HANA side-by-side extension
Real time access on business data
Transition infrastructure to Suite on HANA or S/4HANA
Considerations
Setup of SLT process, data replication required
Possible scale-up of existing HANA DB
Currently external access is only recommended by using a WAF (Web Application Firewall
More complex landscape setup
No Search functionality possible
Example:
Gateway
Server
AS ABAP
SAP FES
ABAP
Central GW
Content (opt)
Web Dispatcher
Central UI
Technology
Fiori UIs for ERP
Frontend – HTML5
TRFC
HTTP/ODATA
SAP HANA
HANA
XS Server
Fiori App Content
HTTP/ODATA
HTTP/ODATA
ECC Server
SAP ERP
ABAP
Gateway enabl.
ERP content*
SAP CRM
SLT REPLICATION
S/4HANA Fiori ScenariosExtended landscape scenarios
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 20Customer
Fiori Architecture Scenariosusing Fiori within a SAP S/4HANA on premise integration scenario
Integration landscape (S/4H)
Typical starting point for S/4H customers is an integration of a new S/4H system in
an existing enterprise infrastructure
Similar to the strategy before S/4H, the same benefits and considerations for an
embedded or hub deployment of the Fiori FES are valid
Benefits
Easy integration of an S/4H system in an existing landscape via central Fiori FES
The additional S/4H UI content must simply be deployed on FES
No more XS content (VDMs) – all analytics in S/4H designed via CDS (Core Data Services), as a result no direct http channel from Web Dispatcher to HANA XS is required anymore
Considerations
All systems with S/4H Fiori content must run on a SAP DB
FES must be on min. NW 7.50
Currently there is a strict dependency between SAP Fiori UI and SAP S/4H backend release version and SP
Example:
S/4H Core
S/4H
ABAP
Gateway
Server
AS ABAP on SAP DB*
SAP FES
ABAP
Central GW
Content (opt)
Gateway enabl.
sFinancials
Web Dispatcher
Central UI
Technology
Fiori UIs for ERP
Frontend – HTML5
HTTP/ODATA
SAP HANA for S/4 SystemHANA
Search
INA
PRIMARY DB CONNECTION
SAP HANA for ERP System HANA
PRIMARY DB CONNECTION
TRFC
S/4 Fiori UIs*
INA
ECC
Server
ERP on HANA
Gateway enabl.
Suite content*
Search
* if S/4 content is deployed on FES
a SAP DB is mandatory
ABAP
Fiori Mobile ScenariosExtended landscape scenarios
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 22Customer
Fiori Architecture ScenariosUsing Fiori with SAP HCP Mobile Services (HCPms)
Extended Landscape Option (Cloud)
HCPms as Service on HANA Cloud Platform
Starting point for more HCP services like Web IDE, Mobile Place/
Mobile Secure
Benefits
Easy access to HCPms features via Cloud subscription (Zero installation)
Secure channel from HCP to SAP system via Cloud Connector
Usage of special mobile features like Fiori offline
SMP administration cockpit with e.g. Application Policies
Logging and Tracing features
Considerations
Setup of Cloud Connector to access backend data
Example:
ECC
Server
SAP ERP on HANA
ABAP
Gateway
Server
AS ABAP
SAP FES
ABAP
Central GW
Content (opt)
Gateway enabl.
ERP content*
Central UI
Technology
Fiori UIs for ERP
Frontend – HTML5
TRFC
XS Engine
Fiori App Content
HTTP/ODATA
SAP HANA System for SAP ERPHANA
VDM Reuse Content
Search
INA
Web Dispatcher
HTTP/ODATA
Cloud
HTTP/ODATA
Cloud Connector
HCPHCPms
Internet
PRIMARY DB CONNECTION
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 23Customer
Fiori Architecture ScenariosUsing Fiori with SAP Mobile Platform (SMP)
Extended Landscape Option (on Premise)
SAP Mobile Platform as part of on premise landscape
SAP Mobile Platform as entry point for all Fiori internet requests
Benefits
Usage of Fiori Client App with SMP and additional security scenarios (SSO)
Usage of special mobile features like Fiori offline
Additional security layer in front of SAP Fiori Frontend-Server
SMP administration cockpit with e.g. Application Policies
Logging and Tracing features
Considerations
Additional SMP system in Fiori landscape
Additional installation of SMP
Example:
ECC
Server
SAP ERP on HANA
ABAP
Gateway
Server
AS ABAP
SAP FES
ABAP
Central GW
Content (opt)
Gateway enabl.
ERP content*
Web Dispatcher + Web Application Firewall
Central UI
Technology
Fiori UIs for ERP
Frontend – HTML5
TRFC
HTTP/ODATA
XS Engine
Fiori App Content
HTTP/ODATA
SAP HANA System for SAP ERPHANA
VDM Reuse Content
Search
INA
SAP Mobile Platform
Web Dispatcher
HTTP/ODATA
HTTP/ODATA
DMZ
Internet
PRIMARY DB CONNECTION
© 2015 SAP SE or an SAP affiliate company. All rights reserved. 24Customer
Fiori Architecture ScenariosUsing Fiori mobile with SAP Authenticator without Mobile Platform
Extended Landscape Option (on Premise)
Usage of SAP Authenticator as SSO solution for Fiori
Usage of Device Browser or Fiori Client App (prepared for
usage with SAP Authenticator)
Benefits
Easy to implement SSO solution based on SAML 2.0 assertion
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 Portal system
Easy to integrate in existing landscape infrastructure
Considerations
No SAP Mobile Platform features like Offline etc.
SAP SSO 2.0 has a separate licensing
Example:
ECC
Server
SAP ERP on HANA
ABAP
Gateway
Server
AS ABAP
SAP FES
ABAP
Central GW
Content (opt)
Gateway enabl.
ERP content*
Web Dispatcher + Web Application Firewall
Central UI
Technology
Fiori UIs for ERP
TRFC
HTTP/ODATA
XS Engine
Fiori App Content
HTTP/ODATA
SAP HANA System for SAP ERPHANA
VDM Reuse Content
Search
INA
Web Dispatcher
HTTP/ODATA
HTTP/ODATA
Outer DMZ
Internet
PRIMARY DB CONNECTION
JEE
Mobile Device
SAP Authenticator
App
IdP
SSO Library
HTTP
Inner DMZ
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
Thank you
Contact information:
F name MI. L name
Title
Address
Phone number
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
© 2015 SAP SE or an SAP affiliate company. All rights reserved.
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 SAP affiliate company.
SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP SE (or an SAP affiliate
company) in Germany and other countries. Please see http://global12.sap.com/corporate-en/legal/copyright/index.epx for additional trademark information and notices.
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 any kind, and SAP SE or its
affiliated companies shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP SE or SAP affiliate company products and
services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as
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 presentation, or to develop
or release any functionality mentioned therein. This document, or any related presentation, and SAP SE’s or its affiliated companies’ strategy and possible future
developments, products, and/or platform directions and functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time
for any reason without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or functionality. All forward-
looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers are cautioned not to place
undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in making purchasing decisions.