Landscape Deployment Recommendations for SAP Fiori Front-End
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 2015 SAP SE or an SAP affiliate company. All rights reserved. Customer 2
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. Customer 3
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 2015 SAP SE or an SAP affiliate company. All rights reserved. Customer 4
Introduction Methodology & Scope of Landscape Recommendations
JEE JEE JEE JEE System Landscapes at Customers Designing the Optimal Landscape Layout Product Roadmaps SAP ERP SAP SRM SAP SCM SAP CRM ERP SRM SCM CRM Components Components Components Components Business Aspects ECC SRM SCM CRM AS AS AS AS SAP Solution Manager SAP Business Suite Backend Systems SolMan Content Solution Mng Component SLD Dual Stack SAP NetWeaver Hubs Application Portal Business Warehouse BEx Web Process Integration Operations Costs Architectural Strategy Security Additional SAP BS Instance Portal Content ADOBE EP Core AS JAVA SEM Central BI Content BW AS BICS BI JAVA EP AS JAVA ESR Content ESR&SR PI SLD PI Dual Stack Deployment Recommendations for SAP Products Speed of Innovation Performance & Scalability Legal Aspects Solution Landscape of Customer OS/DB platform strategy IT Aspects SLA & Availability Technical Documentation (Planning, Installation & Configuration Guides, etc.) 2015 SAP SE or an SAP affiliate company. All rights reserved. Customer 6
JEE JEE JEE JEE Deployment Recommendations for SAP Products Guiding Principles SAP ERP SAP SRM SAP SCM SAP CRM ERP SRM SCM CRM Components Components Components Components ECC SRM SCM CRM AS AS AS AS SAP Solution Manager SAP Business Suite Backend Systems SolMan Content Solution Mng Component SLD Dual Stack SAP NetWeaver Hubs Application Portal Additional SAP BS Instance Portal Content EP Core AS JAVA ADOBE Business Warehouse SEM Central BI Content BW AS BEx Web BICS BI JAVA EP AS JAVA Solution Landscape of Customer Process Integration ESR Content ESR&SR PI SLD PI Dual Stack High-Level Guidance for optimized Landscape Layouts Deployment Recommendations for SAP Products 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 2015 SAP SE or an SAP affiliate company. All rights reserved. Customer 7
Ease Landscape Planning By Stronger Guidance Used Methodology Clear recommendations by categorization of deployment options Possible Exception Only useful for specific use cases Supported by SAP, but limitations might occur Reasonable Alternative Useful choice for certain use cases or customer scenarios Supported and confirmed by SAP s strategy Option III Option II Option I General Recommendation Best choice for majority of typical landscape use cases Recommended by SAP s strategy Accepted by a wide base of customers Goal Consider 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 2015 SAP SE or an SAP affiliate company. All rights reserved. Customer 8
High Level Product Overview (1/2) Make Experience Coherent Across the Enterprise Finance Human Resources CRM Procurement Provides only on the relevant tasks and activities for an end user 2015 SAP SE or an SAP affiliate company. All rights reserved. Customer 9
High Level Product Overview (2/2) SAP Fiori UX Concept Role-based Responsive Simple Coherent Delightful Design Technology Visual Design Information Architecture Interaction Patterns User Interface Business Logic 2015 SAP SE or an SAP affiliate company. All rights reserved. Customer 10
Scope of Landscape Recommendations Building Blocks in System Landscapes for SAP Fiori Example: Considered main usage scenarios Enables SAP Fiori apps Enables general UI5 framework content Enables consumption of -Services from SAP backend Considered main building blocks SAP Web Dispatcher serves as Reverse Proxy Fiori Frontend (FES) containing Fiori Applications (UIs) inclusive Fiori Launchpad Content Central UI Technology provides UI5 framework and the Fiori Launchpad (FLP) SAP Gateway content and (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) 2015 SAP SE or an SAP affiliate company. All rights reserved. Customer 11
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. 2015 SAP SE or an SAP affiliate company. All rights reserved. Customer 12
Basic Landscape Setups Recommendations for Fiori Frontend (FES)
Deployment of Fiori Frontend (FES) Central Hub Deployment Example: 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 System Web Dispatcher (Reverse Proxy) is mandatory when using analytical Fiori apps 2015 SAP SE or an SAP affiliate company. All rights reserved. Customer 14
Deployment of Fiori Frontend (FES) Add-on Deployment in Application Backend System Example: Possible Exception Deployment of needed Fiori UI content on each required SAP Backend system (ERP, CRM etc.) Multiple deployment/configuration of Gateway 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 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 2015 SAP SE or an SAP affiliate company. All rights reserved. Customer 15
Landscape Use-Cases Best practice usage scenarios
Fiori Architecture Scenarios Using Fiori (Transactional, Analytical & Factsheets) in an HANA Embedded Scenario Example: General Recommendation Best suited scenario for Suite on HANA systems (Business Suite 7) HANA XS enables direct 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 2015 SAP SE or an SAP affiliate company. All rights reserved. Customer 17
Fiori Architecture Scenarios Using Fiori Analytical Apps with SAP HANA side-by-side with SAP Business Suite Example: Frontend HTML5 Web Dispatcher Possible Exception Data replication via SLT from SAP ERP system to HANA DB HANA XS enables direct access from WebDispatcher SAP FES Fiori UIs for ERP Central UI Technology Central GW Content (opt) 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 SAP CRM SAP ERP ERP content* Gateway enabl. ECC TRFC Gateway AS SAP HANA Fiori App Content XS HANA 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 SLT REPLICATION 2015 SAP SE or an SAP affiliate company. All rights reserved. Customer 18
S/4HANA Fiori Scenarios Extended landscape scenarios
Fiori Architecture Scenarios using Fiori within a SAP S/4HANA on premise integration scenario Example: INA Frontend HTML5 Web Dispatcher SAP FES INA 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 S/4 Fiori UIs* Fiori UIs for ERP Central UI Technology Central GW Content (opt) Gateway AS on SAP DB* TRFC * if S/4 content is deployed on FES a SAP DB is mandatory 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 S/4H Search sfinancials Gateway enabl. S/4H Core PRIMARY DB CONNECTION ERP on HANA Search Suite content* Gateway enabl. ECC PRIMARY DB CONNECTION SAP HANA for ERP System HANA 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 SAP HANA for S/4 System HANA 2015 SAP SE or an SAP affiliate company. All rights reserved. Customer 20
Fiori Mobile Scenarios Extended landscape scenarios
Fiori Architecture Scenarios Using Fiori with SAP HCP Mobile Services (HCPms) Example: Frontend HTML5 HCPms HCP Internet Cloud Extended Landscape Option (Cloud) HCPms as Service on HANA Cloud Platform Starting point for more HCP services like Web IDE, Mobile Place/ Mobile Secure Cloud Connector Web Dispatcher SAP FES Fiori UIs for ERP Central UI Technology Central GW Content (opt) Gateway AS INA 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 TRFC SAP ERP on HANA Search Considerations Setup of Cloud Connector to access backend data ERP content* Gateway enabl. ECC PRIMARY DB CONNECTION Fiori App Content VDM Reuse Content XS Engine SAP HANA System for SAP ERP HANA 2015 SAP SE or an SAP affiliate company. All rights reserved. Customer 22
Fiori Architecture Scenarios Using Fiori with SAP Mobile Platform (SMP) Example: Frontend HTML5 Web Dispatcher + Web Application Firewall Internet DMZ 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 SAP Mobile Platform Web Dispatcher SAP FES Fiori UIs for ERP Central UI Technology Central GW Content (opt) Gateway INA 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- SMP administration cockpit with e.g. Application Policies Logging and Tracing features AS TRFC SAP ERP on HANA Search ERP content* Gateway enabl. ECC PRIMARY DB CONNECTION Fiori App Content VDM Reuse Content XS Engine Considerations Additional SMP system in Fiori landscape Additional installation of SMP SAP HANA System for SAP ERP HANA 2015 SAP SE or an SAP affiliate company. All rights reserved. Customer 23
Fiori Architecture Scenarios Using Fiori mobile with SAP Authenticator without Mobile Platform Example: Mobile Device SAP Authenticator App Web Dispatcher + Web Application Firewall Internet Outer DMZ 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) HTTP IdP SSO Library JEE Inner DMZ Web Dispatcher SAP FES INA Benefits Easy to implement SSO solution based on SAML 2.0 assertion Fiori UIs for ERP Central UI Technology Central GW Content (opt) 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 TRFC SAP ERP on HANA Gateway AS Considerations No SAP Mobile Platform features like Offline etc. SAP SSO 2.0 has a separate licensing Search ERP content* Gateway enabl. ECC PRIMARY DB CONNECTION Fiori App Content VDM Reuse Content XS Engine SAP HANA System for SAP ERP HANA 2015 SAP SE or an SAP affiliate company. All rights reserved. Customer 24
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 forwardlooking 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. 2015 SAP SE or an SAP affiliate company. All rights reserved.