Deployment Recommendations for SAP Fiori Front-End Server & SAP Fiori Cloud

Transcription

1 Deployment Recommendations for SAP Fiori Front-End & SAP Fiori Cloud December 2017, SAP SE

2 Change Log Version February 2017 July 2017 October 2017 December 2017 Changes Smaller updates S/4HANA option added; SMP option deleted; SFC information added S/4HANA multi release option added Several updates / fixes in the S/4H section; Embedded deployment as general recommendation for S/4HANA 2

3 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 noninfringement. SAP assumes no responsibility for errors or omissions in this document, except if such damages were caused by SAP intentionally or grossly negligent. 3

4 Agenda Introduction Methodology & Scope of Landscape Recommendations Basic Landscape Setups Recommendations for SAP Fiori Using SAP Fiori with S/4HANA Additional 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 4

5 JEE JEE JEE JEE System Landscapes at Customers Designing the Optimal Landscape Layout Product Roadmaps SAP ERP SAP SRM SAP SCM SAP CRM ERP Components SRM Components SCM Components CRM Components Business Aspects ECC AS SRM AS SCM AS CRM 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 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 Solution Landscape of Customer IT Aspects Technical Documentation (Planning, Installation & Configuration Guides, etc.) 5

6 Introduction Methodology & Scope of Landscape Recommendations

7 JEE JEE JEE JEE Deployment Recommendations for SAP Products Guiding Principles SAP ERP SAP SRM SAP SCM SAP CRM ERP Components SRM Components SCM Components CRM 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 Application Portal Additional SAP BS Instance Portal Content EP Core AS JAVA ADOBE SAP NetWeaver Hubs 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 7

8 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 8

9 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 9

10 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 Official Fiori Design Guidelines 10

11 Scope of Landscape Recommendations Building Blocks in System Landscapes for SAP Fiori Example: Frontend HTML5 Web Dispatcher Considered main usage scenarios Enables SAP Fiori apps Enables general UI5 framework content Enables consumption of ODATA-Services from SAP backend Fiori Frontend Sever Fiori UIs Central UI Technology Central GW Content (opt) AS ERP on HANA Suite content* enabl. ECC HANA SAP CRM SAP SRM SRM content* enabl. SRM S/4HANA enabl. S/4H content* S/4 HANA Considered main building blocks SAP Web Dispatcher serves as Reverse Proxy Static or Smart Routing possible (details) Fiori Frontend (FES) containing Fiori Applications (UIs) inclusive Fiori Launchpad Content Central UI Technology provides UI5 framework and the Fiori Launchpad (FLP) SAP optional content and (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) 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) 11

12 Basic Landscape Setups Recommendations for Fiori Frontend

13 Deployment of Fiori Frontend (FES) Central Hub Deployment Single Backend System per Product Example: Frontend HTML5 HTTP/ ODATA Web Dispatcher 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 ERP on HANA Suite content* enabl. ECC HANA HTTP/ ODATA Fiori Frontend S/4H Fiori Uis** Fiori UIs for ERP, SRM Central UI Technology Central GW Content (opt) AS TRFC S/4HANA enabl. S/4H content* S/4 HANA ** if S/4 content is deployed on FES a SAP DB is mandatory * Fiori Backend SWCVs SAP CRM SAP SRM SRM content* enabl. SRM Benefits 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 User and authorization management to be done in FES and backend, with identical user ID Web Dispatcher (Reverse Proxy) is mandatory when using analytical Fiori apps Support of one release-version per product (e.g. not multiple S/4H releases) Product specific update dependencies between backend product versions (SPS) and frontend product versions (SPS) might require synchronous updates of FES and backend If S/4H content is deployed on FES a SAPDB (HANA, MaxDB, ASE) is required 13

14 Deployment of Fiori Frontend (FES) Embedded Deployment Multiple Systems with same Product Example: Frontend HTML5 HTTP/ODATA Frontend HTML5 HTTP/ODATA Web Dispatcher Frontend HTML5 HTTP/ODATA General Recommendation Deployment of needed Fiori UI content on each SAP Backend system (ERP, CRM, S/4H etc.) Multiple configuration of and content (on each SAP Backend) Recommended for landscapes with multiple systems of the same product Option for single system infrastructures e.g. PoCs or single instance productive systems (starting point for Fiori) HTTP/ODATA HTTP/ODATA HTTP/ODATA Benefits No additional NW system needed less TCO E.g. S/4HANA 1610 SPS1 E.g. S/4HANA 1610 SPS3 E.g. S/4HANA 1709 SPS1 Less runtime overhead no remote-calls Direct access to metadata and business data (cached request processing) S/4H Fiori UIs S/4H Fiori UIs S/4H Fiori UIs Later scale-out to central hub deployment in general possible (not for S/4H) Search Industry components Search Industry components Search Industry components Simplified user and authorization management (within one system) Considerations Synchronized innovation speed of Fiori UI/GW and backend enabl. S/4H Core enabl. S/4H Core enabl. S/4H Core FLP with corresponding UI product version for each S/4H product release-version (not multiple S/4H release-versions and no mixed versions)ł Multiple FLPs must be configured / operated AS HANA AS AS Update strategy must reflect dependencies between software components Cross-System composition (embedded FES used as hub) is not advisable Potential scale-up of SAP backend (resizing) 14

15 SAP S/4HANA on premise Fiori Scenarios Landscape scenarios

16 Overview Typical Customer Options Business Suite landscape (Multi Product) e.g. ERP, SRM Business Suite landscape (Multi System/Release) e.g. multiple ERPs Single S/4H system Multiple S/4H systems (available or planned) Comment Embedded FES FES as Hub Mixed Scenario recommended: FES as hub - Co-deployment of different products (e.g. ERP, CRM) possible recommended: FES as hub - Multiple versions of one product (e.g. ERP) possible with restrictions (to be checked on app level) Options: - embedded deployment - Co-deployment on hub in parallel to Fiori for business suite possible per S/4H System - recommended: Embedded deployment Optional extension: FES hub as single entry point for shared services (e.g. ESS/MSS) + Launcher tiles to launch S/4H system specific FLPs - Fiori Architecture Scenarios using Fiori within a SAP S/ Fiori Architecture Scenarios using Fiori within a SAP S/4... Fiori Architecture Scenarios using Fiori within SAP S/4HA... Fiori Architecture Scenarios using Fiori within SAP S/4HA... Fiori Architecture Scenarios using Fiori within a SAP S/4... Deployment of Fiori for S/4HANA on central FES Hub not recommended: only possible, if all connected S/4HANA systems have identical release. Synchronous upgrade of frontend and all backends required. - Fiori Architecture Scenarios using Fiori within a multi S... - Fiori Architecture Scenarios using Fiori within a multi S... 16

17 Fiori Architecture Scenarios using Fiori within SAP S/4HANA on premise (embedded FES) Example: FLP 1 Frontend HTML5 FLP 2 Web Dispatcher Embedded FES in S/4HANA on premise Starting point for S/4H on premise customer (net-new, or conversion from ERP) Larger customer environments with multi systems of the same product Recommended approach if using a S/4H multi-system landscape scenario INA INA HTTP/ ODATA S/4HANA S/4H Fiori UIs HTTP/ ODATA S/4HANA S/4H Fiori UIs Benefits Usage of optimized micro-hub within S/4H backend system The S/4H UI content is deployed directly in the backend All analytics in S/4H via CDS (Core Data Services), no HANA XS Search Industry components enabl. S/4H Core Search Industry components enabl. S/4H Core Considerations Multiple FLPs: Dedicated FLP for additional S/4H system Any FLP must be configured / operated UI upgrade must be planned in sync with backend maintenance window PRIMARY DB CONNECTION SAP HANA for S/4 System PRIMARY DB CONNECTION SAP HANA for S/4 System 17

18 Fiori Architecture Scenarios using Fiori with a SAP S/4HANA on premise system (FES as a Hub) Example: INA FLP 1 Frontend HTML5 Web Dispatcher HTTP/ ODATA SAP FES INA FES as a Hub with S/4HANA Integration of a new S/4H system in an existing enterprise landscape Same benefits and considerations for hub deployment of the Fiori FES are valid Not recommended for new FES deployments in landscapes with more than one S/4H or ERP systems S/4H Fiori UIs** S/4H Search Industry comp. enabl. S/4H Core Fiori UIs for ERP Central UI Technology Central GW Content (opt) HANA SAP HANA for S/4 System PRIMARY DB CONNECTION AS on SAP DB* TRFC ** if S/4 content is deployed on FES a SAP DB is mandatory ERP on HANA Search Suite content* enabl. ECC PRIMARY DB CONNECTION SAP HANA for ERP System * Fiori Backend SWCVs HANA Benefits Integration of an S/4H system in an existing landscape via central Fiori FES The additional S/4H UI content can be deployed on FES All analytics in S/4H via CDS (Core Data Services), no HANA XS Considerations If S/4H content is deployed on FES a SAPDB (HANA, MaxDB, ASE) is required FES requires min. NW 7.50 Connected ERP system cannot be converted to S/4H because of version dependencies (see here) embedded FES deployment required 18

19 Fiori Architecture Scenarios using Fiori with multiple SAP S/4HANA on premise systems (Mixed scenario) Example: FLP 1 Frontend HTML5 FLP 2 Web Dispatcher HTTP/ ODATA Mixed landscape for S/4HANA Scenario for large S/4HANA customers is an integration of a new S/4HANA system in an existing enterprise landscape (with Suite & S/4HANA systems) Recommendation: Embedded deployment for new S/4H system INA SAP FES INA S/4H Fiori UIs* Fiori UIs for ERP Central UI Technology Central GW Content (opt) HTTP/ ODATA INA Benefits No impact on existing FES as a hub environment S/4H (1610) Search Industry comp. enabl. S/4H Core PRIMARY DB CONNECTION AS on SAP DB* TRFC SAP HANA for S/4 System * if S/4 content is deployed on FES a SAP DB is mandatory SAP HANA for ERP System HANA ERP on HANA Search Suite content* enabl. ECC PRIMARY DB CONNECTION HANA S/4H (1709) S/4H Fiori UIs* Search Industry comp. enabl. S/4H Core PRIMARY DB CONNECTION Considerations Multiple FLPs: Dedicated FLP for additional S/4H system Any FLP must be configured / operated For FES Hub: All systems with S/4HANA Fiori content must run on a SAP DB One FLP with corresponding UI product version is for each S/4H product release-version required (not multiple S/4H release-versions and no mixed versions) When converting the ERP system to S/4HANA, embedded FES deployment needed (see here) SAP HANA for S/4 System HANA 19

20 SAP Fiori Cloud SAP Fiori Cloud integrated with on-premise system landscapes

21 Internal & External Access Point Scenarios Internal Access Point External Access Point ON-PREMISE PUBLIC CLOUD UI SERVICES DATA & PROCESSES SAP Cloud Platform SAP Fiori apps & launchpad SAP Web Dispatcher OData SAP Hub / Embedded SAP backend + SAP service implementation A B * SAP Cloud Platform https SAP Fiori apps & launchpad SAP Cloud Connector OData SAP Hub / Embedded SAP backend + SAP service implementation SAP Cloud Platform SAP Fiori apps & launchpad OData OData provisioning* SAP Cloud Connector SAP Business Suite (SAP service impl.) Users access launchpad and apps via internal SAP Web Dispatcher, no business data leaves the intranet Users access launchpad and apps on SAP Cloud Platform via internet connection * Option B: SAP Business Suite scenarios only, * for restrictions see note: #

22 SAP Fiori Cloud Supported Access Point Scenarios SAP Business Suite SAP (on premise) SAP Cloud Platform, OData provisioning External Access Point (EAP) Supported Supported Internal Access Point (IAP) Supported not relevant SAP S/4HANA SAP (on premise) SAP Cloud Platform, OData provisioning External Access Point (EAP) Supported not applicable* Internal Access Point (IAP) Supported not relevant * SAP S/4HANA comes with build-in OData provisioning capabilities, restrictions see note: #

23 Landscape Deployment of SAP Fiori Cloud Connect to SAP Business Suite via SAP Cloud Platform OData provisioning Example External access to SAP Business Suite Fiori frontend services in the cloud (Fiori UIs, SAPUI5 libraries, Fiori launchpad, OData provisioning, etc.) For customers who do not run a dedicated Frontend server / hub (on-premise) Benefits Fiori apps for SAP Business Suite provided via cloud subscription Cloud-based OData provisioning service Minimized setup and maintenance for Fiori infrastructure Considerations SAP CP OData provisioning service does not provide the complete SAP hub functionality (Note # ) SAP CP Cloud connector required to establish secure access between customer account and on-premise landscape enablement and relevant Fiori backend components required in backend system Not valid for S/4H 23

24 Landscape Deployment of SAP Fiori Cloud Connect to SAP Business Suite & S/4HANA on-premise via SAP server Example External access to SAP Business Suite & SAP S/4HANA Allow customers to run, extend and develop Fiori apps in the cloud, while leveraging a central SAP server (on-premise hub) in multi-system environments Benefits SAP Business Suite & S/4HANA Fiori apps via cloud subscription Usage of Fiori 2.0 Automated selection of Fiori app versions compatible to the connected backend(s) Central SAP server to manage OData services Full set of SAP hub capabilities available (optional) FES embedded deployment in single system landscape Considerations Customer needs to operate and maintain SAP server SAP CP Cloud connector required to establish secure access between customer account and on-premise landscape enablement and relevant Fiori backend components required in backend system 24

25 Landscape Deployment of SAP Fiori Cloud Connect to SAP Business Suite or SAP S/4HANA via SAP embedded Example Internal access to SAP Business Suite & SAP S/4HANA SAP on premise (Hub or Embedded) Frontend services in the cloud (Fiori UIs, S/4H Fiori UIs, FLP) Benefits SAP Business Suite & S/4HANA Fiori apps via cloud subscription OData provisioning via on premise Minimized setup and maintenance for Fiori infrastructure (Optional) as Hub in multi-system landscapes Automated selection of Fiori app versions compatible to the connected backend(s) Considerations configuration and relevant Fiori backend components required in backend system 25

26 Business Suite Landscape Scenarios Use-cases

27 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 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 27

28 Fiori Architecture Scenarios Using Fiori Analytical Apps with SAP HANA side-by-side with SAP Business Suite Example: Frontend HTML5 HTTP/ ODATA Web Dispatcher Possible Exception Data replication via SLT from SAP ERP system to HANA DB HANA XS enables direct ODATA access from WebDispatcher HTTP/ ODATA HTTP/ ODATA 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* enabl. ECC TRFC 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 28

29 Fiori Scenarios for Mobile Extended landscape scenarios

30 Fiori Architecture Scenarios Using Fiori with SAP Cloud Platform Mobile Services (CPms) Example: Extended Landscape Option (Cloud) CPms as Service on SAP Cloud Platform Starting point for more SAP CP services like Web IDE, Mobile Place/ Mobile Secure Benefits Easy access to SAP CPms features via Cloud subscription (Zero installation) Secure channel from SAP CP 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 30

31 Fiori Architecture Scenarios Using Fiori mobile with SAP Authenticator without Mobile Platform Example: Mobile Device HTTP/ ODATA 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/ ODATA HTTP IdP SSO Library JEE Inner DMZ Web Dispatcher HTTP/ ODATA SAP FES INA HTTP/ ODATA 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 AS Considerations No SAP Mobile Platform features like Offline etc. SAP SSO 2.0 has a separate licensing Search ERP content* enabl. ECC PRIMARY DB CONNECTION Fiori App Content VDM Reuse Content XS Engine SAP HANA System for SAP ERP HANA 31

32 Additional Information Static vs. Smart Routing

33 Static vs. Smart Routing in productive SAP Fiori Landscapes UI Routing via SAP Web Dispatcher a reverse proxy is typically required in any productive setup SAP Web Dispatcher is ideal for simple or static routing static routing is sufficient in singleinstance landscapes Recommendation: perform routing of OData / REST service requests via SAP Web Dispatcher in single-instance landscapes reverse proxy / SAP Web Dispatcher HTTP ICF S/4 HANA backend HANA HTTP ICF service request processing on hub RFC RFC RFC Routing via hub (on FES) a (for instance on an FES) is well suited for context-driven smart routing (like multi-origin, userbased routing) in environments with multiple S/4 backend systems the overall duration for the service request increases slightly by the service request processing and the additional RFC request Recommendation: perform routing of OData / REST service requests via hub in multi-instance landscapes 33

34