Page tree
Skip to end of metadata
Go to start of metadata


 *** This wiki is now outdated and is in the process of being retired.  Please refer to SAP Fiori Deployment Options and Landscape Recommendations guide for the latest information on SAP Fiori Frontend Server architecture options. The guide is updated every few months. ***

Introducing SAP Fiori Front-End Server


What is FES?


SAP Fiori front-end server (FES) offers a bundle of technology components that are required to run SAP Fiori scenarios. It contains the following:

  • UI development toolkit for HTML5 (SAPUI5) framework and the components to run the SAP Fiori launchpad on the ABAP stack.
  • SAP Gateway core components on the ABAP stack.
  • SAP Fiori Implementation Foundation.
  • SAP Fiori Basis Apps (available only with SAP NetWeaver 7.5 or higher).

SAP Fiori FES does not provide any new technical components. It has been created to define the exact stacks required for SAP Fiori application versions and thereby simplify customer consumption.

What Deployment of FES is Optimal?


This topic is mostly valid for IT or solution architects who need to establish an optimal deployment of SAP Fiori FES on a given system landscape. Before implementing SAP Fiori FES, IT departments need to decide what is the best deployment option of this product within their system landscape. For this reason, the information about the deployment architecture of SAP Fiori FES needs to be analyzed and the suitable deployment options have to be evaluated. Then, the planned landscape architecture needs to be determined, and finally, SAP Fiori FES has to be implemented and integrated into the existing system landscape.
A change of the system landscape architecture at a later point requires considerable effort and resources in most of the cases. Therefore, it is important to design a landscape architecture that fully meets the company needs and requirements and will last longer and reliably in the future.

To offer guidance, SAP provides various landscape deployment options for SAP Fiori FES. These options, with their advantages and points for consideration, are outlined in the remainder sections of this WIKI page, for your reference and informed decision. For more information, see: Deployment Recommendations for SAP Fiori Front-End Server & SAP Fiori Cloud


At the end of this Wiki page you can find a collection of links to further sources of information that will supplement the info outlined in the remainder sections below.

Further Sources of Information


Deployment Architecture of FES


The purpose of the information below is to help you understand the intended landscape deployment of the SAP Fiori FES product. This section also outlines the two general deployment options for SAP Fiori FES.

Deployment Architecture

The deployment architecture of SAP Fiori FES is based on the following main technical components:

  • SAP Web Dispatcher
    Serves as a reverse proxy and enables either static or smart routing.
  • SAP Fiori front-end server (FES)
    It is based on SAP NetWeaver AS ABAP (either embedded, or as a hub), and includes the following:
    • Fiori Apps (UIs)
      Including the Fiori Launchpad Content.
    • Central UI technology
      It provides the UI5 framework and the Fiori Launchpad (FLP) runtime.
    • SAP Central Gateway Optional Content
    • SAP Gateway Server
      Note that as of SAP NetWeaver 7.4 and higher SAP _GWFND component is part of the SAP NetWeaver AS ABAP stack.
  • SAP backend application systems
    The backend application systems can be either Business Suite systems (ERP, SRM, CRM, etc.) on any DB or on SAP HANA; or SAP S/4HANA systems and include the following:
    • Fiori Backend OData integration
      OData integration is enabled either via add-ons or support packages.
    • SAP Gateway enablement backend components
      Note that the IW_BEP is already part of SAP NetWeaver 7.4 and higher.
    • A corresponding system server.

Note that the SAP S/4HANA systems rely on product specific update dependencies between backend product versions (SPS) and frontend product versions (SPS).

SAP Fiori Apps

SAP Fiori UI5 applications following the SAP Fiori development paradigm stick to the design principles as described in the SAP Fiori Design Guidelines and outlined below:

  • SAP Fiori UIs (front-end) and OData services (backend) are divided in different software components.
  • A synchronous software update of both parts is not required (decoupled updates).
  • Interoperability between UI and backend artifacts is ensured.
  • One SAP Fiori app corresponds to one dedicated OData service.
  • SAP Fiori UIs are built with SAPUI5.

For more information about a catalog of SAP Fiori Applications following this architectural paradigm, see: Catalog of SAP Fiori Apps.

Overview of Landscape Scenarios and Deployment Options
The currently supported landscape deployment options for SAP Fiori FES are individually described including their advantages, potential drawbacks, and points for consideration. More information about the deployment options is added under the corresponding landscape scenario section. The following list outlines a brief summary of the possible landscape scenarios that are better described in the remainder of this WIKI page.

  • General Deployment Options
    General description (as part of the introductory concept information section) of the basic deployment options of SAP Fiori FES.
  • SAP S/4HANA Scenario
    Focuses on the integration scenario of SAP Fiori FES with SAP S/4HANA On-premise systems.
  • SAP Fiori Cloud Scenario
    Contains descriptions of options where the Fiori apps are provided by the help of the SAP Cloud Platform.
  • Other Scenarios
    Focuses on the deployment options of SAP Fiori FES components for mobile-relevant business cases.

Go to Top


General Deployment Options for FES


Prior to the integration of SAP Fiori FES, we recommend that a detailed analysis of the customer system landscape and business scenarios are carried out. Presumably, this will ensure the best possible decision regarding the deployment of SAP Fiori FES.
SAP Fiori FES allows various deployment options, which result in different system landscape architectures. Each architecture has advantages and points for considerations. Therefore, in the end it is up to the parties involved in the integration to decide, which deployment option of SAP Fiori FES best fits to their IT and business needs.
SAP provides reviews of the system landscape deployment options for SAP Fiori FES to support customers to make the right decisions. These reviews are based on a defined methodology to ensure consistency across different products. A common template-based structure and layout simplifies the consumption of this  information.
Disclaimer: Note that these reviews do not substitute any individual assessment. The specific customer environment cannot be considered by SAP on a general basis and always needs to be analyzed independently.

Embedded FES Deployment


SAP Fiori FES can be deployed in a system landscape as an add-on deployment in each backend application system. This deployment option is possible in a system landscape when deploying SAP Fiori apps for multiple different SAP applications at multiple systems with the same product.





What's in it?
  • SAP Fiori UIs are decoupled from the backend functionality as a separate software component.
  • SAP Fiori FES offers a local deployment of the UIs and a local enablement of OData access for each backend application system.
  • Fiori apps are deployed in the related backend application system. UIs are also deployed with the related OData services in the backend system.
Advantages

Deployment

  • Additional SAP NetWeaver AS ABAP system is not required.
  • Remote calls are not needed resulting in less runtime overhead.
  • Direct access to metadata and business data.
  • Simplified user and authorization management (within one system).
  • Possibility for scale-out to a central hub deployment at a later point. However, for SAP S/4HANA systems, some constraints might apply, and therefore, further analysis might be needed.
For landscapes of multiple SAP S/4HANA systems it is only possible to create a single-point of entry, for example a Fiori launchpad with common apps, running on a central hub. However, the other systems (and specific apps) will be accessible via link-tiles.
Consider

Adoption

  • Needed synchronization of the innovation of SAP Fiori UIs, SAP Gateway components, and the backend application, due to the shared platform.

Relation

  • Cross-system composition is not recommended (for example, usage of single Fiori launchpad).

Deployment

  • Software update strategy must reflect any dependencies between different software components due to the shared platform.
  • Each SAP application system must meet the minimum system requirements for the technical SAP Fiori FES deployment.
  • Possible scale-up of SAP application systems could be required (in case re-sizing needs to happen).

Other

  • Majority of existing customers at this point prefer an alternative deployment approach for SAP Fiori FES.

Go to Top


Central Hub FES Deployment


SAP Fiori FES can be deployed in a system landscape as a central hub. This deployment option is possible in a system landscape when deploying SAP Fiori apps for multiple different SAP applications at a single backend system per product.


What's in it?
  • SAP Fiori UIs are decoupled from the backend functionality as a separate software component.
  • SAP Fiori FES offers a central deployment of the UIs and a central enablement of OData access for multiple SAP backend application systems.
  • Fiori apps are deployed in separate systems. That is, UIs are on the FES, related OData services are on the backend systems.
Advantages

Adoption

  • SAP Fiori UI update cycles are decoupled from the backend application system.
  • Better handling of innovations for SAP Fiori UIs and UI content.
  • Backend development happens in the system where the business data is stored.

Relation

  • SAP Fiori FES is deployed as a single instance including the central Fiori launchpad.
  • Possible central routing mechanism to several backend systems.
  • Possible central management of connections and a central access for all devices.

Deployment

  • Manage scaling-up of overall landscape independently from the backend system.
  • To facilitate security requirements SAP Fiori FES can be implemented in segmented networks (for example, DMZ).
  • For specific security requirements input validation functions and business logic can be divided on two different systems.
Consider

Deployment

  • Additional SAP NetWeaver AS ABAP system is required.
  • User and authorization management has to be done on both SAP Fiori FES and the backend system, with identical user ID.
  • Support of one release-version per product. That is, multiple SAP S/4HANA releases are not supported.
  • Product specific update dependencies between backend product versions (SPS) and frontend product versions (SPS) might require synchronous updates of SAP Fiori FES and the backend system.
  • If SAP S/4HANA content is deployed on SAP Fiori FES, an SAP Database (SAP HANA, MaxDB, ASE, etc.) is required.

Other

  • A Web Dispatcher (Reverse Proxy) is mandatory for running analytical SAP Fiori apps.

Go to Top







SAP Fiori in SAP S/4HANA On Premise


Embedded FES Deployment


SAP Fiori FES can be deployed in each backend application system. This deployment option is recommended in a system landscape when deploying SAP Fiori apps for multiple different SAP applications at multiple systems with the same product.





What's in it?
  •  A starting point for customers who implement SAP S/4HANA On Premise. This includes both: brand new implementation, or conversions from prior ERP systems.
  • Large customer environments with multiple systems of the same product.
  • Suggested approach in a landscape scenario of multiple SAP S/4HANA systems.
Advantages
  •  Usage of optimized micro-hub within the SAP S/4HANA backend system. For more information, see: Cached Request Processing and Micro Hub
  • The SAP S/4HANA UI content is deployed directly in the backend system.
  • All analytics in SAP S/4HANA are via Core Data Services (CDS), no HANA XS.
Consider
  • Multiple Fiori launchpads will be needed. This option requires a dedicated Fiori launchpad for the additional SAP S/4HANA systems. All Fiori launchpads must be maintained and operated separately.
  • Upgrade of the SAP Fiori UI must be synchronized with the maintenance periods of the backend systems.

Go to Top


Central Hub FES Deployment


SAP Fiori FES can be deployed in a system landscape as a hub connected with a SAP S/4HANA and a SAP Business Suite on HANA system. This deployment option is possible in a system landscape when deploying SAP Fiori within a SAP S/4HANA on-premise integration scenario.

An integration of the new SAP S/4HANA on-premise system into the existing system landscape is a typical starting point for the SAP S/4HANA customers.

What's in it?
  • SAP Fiori UIs are decoupled from the backend system (separate shipment).
  • SAP Fiori FES offers a central deployment of the UIs and a central enablement of OData access for SAP S/4HANA and other SAP backend application systems.
  • The Fiori Apps are deployed in separate systems (UIs in the FES, related OData services in the backend systems).
Advantages

Adoption

  • Enables better handling of innovations for SAP Fiori UIs and UI content.
  • Backend development takes place in the system where the business data is stored.
Relation
  • SAP Fiori FES is deployed as one single instance including the central Fiori launchpad.
  • Possible central routing mechanism into SAP S/4HANA and other backend systems.
  • Possible central management of connections and a central access for all devices.
  • Easy integration of the SAP S/4HANA system in an existing landscape via a central SAP Fiori FES.

Deployment

  • Easy deployment of additional SAP S/4HANA UI content on SAP Fiori FES.
  • Manage scaling-up of overall landscape independently from the backend system.
  • To facilitate security requirements SAP Fiori FES can be implemented in segmented networks (for example, DMZ).
  • For specific security requirements input validation functions and business logic can be divided on two different systems.

Other

  • All analytics in SAP S/4HANA are designed via Core Data Services (CDS). As a result, a direct HTTP channel from Web Dispatcher to HANA XS is not required anymore and XS content (VDMs) are no longer used.
Consider

Relation

  • There is a strict version dependency between the SAP S/4HANA Fiori UI version and SAP S/4HANA backend system version (including the concrete support packages).

Deployment

  • An additional SAP NetWeaver AS ABAP System is required for the SAP Fiori FES. Version of SAP NetWeaver must be 7.5 or higher.
  • All systems with SAP S/4HANA Fiori content must run on an SAP database (SAP MaxDB, SAP ASE, or SAP HANA).

Go to Top






Mixed FES Deployment


SAP Fiori FES can be deployed in a complex system landscape as part of an additional system setup to the existing backend application systems. This deployment option is possible for large-scale system landscapes when separate system integrations occur in different points in time. Depending on the business case, the integration of systems may involve embedded and central hub deployments of SAP Fiori FES resulting in a landscape with a mixed deployment of SAP Fiori FES.




What's in it?
  • Possible scenario for large SAP S/4HANA customers for the integration of a new SAP S/4HANA system in the existing enterprise landscape.
  • Embedded deployment is suggested for the new SAP S/4HANA system.
Advantages
  • The existing landscape environment including the hub deployment of SAP Fiori FES is not affected.
Consider
  • Multiple Fiori launchpads will be needed. This option requires a dedicated Fiori launchpad for the additional SAP S/4HANA system. All Fiori launchpads must be maintained and operated separately.
  • All systems with SAP S/4HANA Fiori content must run on a SAP Database.
  • One Fiori launchpad with the corresponding UI product version is required for each SAP S/4HANA product release-version. Multiple SAP S/4HANA release-versions and mixed versions are not possible.
  • If the existing ERP system are converted to SAP S/4HANA, an embedded SAP Fiori FES deployment will be required.

Go to Top


SAP Fiori Cloud

SAP Business Suite Connector via SAP Cloud Platform OData Provisioning


Frontend services for SAP Fiori can be deployed in the cloud as SAP Fiori Cloud and integrated with on-premise applications via an external access point. This deployment option is possible for an on-premise system landscape with all frontend services for SAP Fiori deployed in the SAP Cloud Platform.


What's in it?
  • Frontend services for SAP Fiori are decoupled from the backend system (separate shipment of SAP Fiori Cloud). OData provisioning service is offered by SAP Cloud Platform.
  • SAP Fiori Cloud offers a central deployment of the UIs and a central enablement of OData access for multiple SAP backend application systems.
  • All frontend services for SAP Fiori (SAP Fiori UIs, SAPUI5 libraries, SAP Fiori launchpad, OData provisioning, etc.) are technically deployed in the cloud, separately from the backend applications and OData services.
  • For customers who do not run a dedicated ABAP Front-end server / Gateway hub (on-premise).
Advantages

Deployment

  • Minimized setup and maintenance for SAP Fiori infrastructure.

Adoption

  • SAP Fiori apps for SAP Business Suite provided in the cloud.
  • Cloud-based OData provisioning service on SAP Cloud Platform.
Consider

Relation

  • Setup of multiple backend systems requires the same version of OData service for the selected SAP Fiori application.

Adoption

Deployment

  • SAP Cloud Platform cloud connector is required to establish secure access between the customer account and the on-premise landscape.

Other

  • Gateway enablement and relevant Fiori backend components are required in the backend application systems at the on-premise landscape.

Go to Top








SAP Business Suite and SAP S/4HANA OP Connector via Embedded SAP Gateway


Frontend services for SAP Fiori can be deployed in the cloud as SAP Fiori Cloud and integrated with on-premise applications via an internal access point. This deployment option is possible for an on-premise system landscape with frontend services for SAP Fiori deployed in the cloud on SAP Cloud Platform besides the OData provisioning service that is deployed on-premise.

For more information, see Internal Access Point Landscape.





What's in it?
  • Frontend services for SAP Fiori are decoupled from the backend system (separate shipment of SAP Fiori Cloud). OData provisioning service is decoupled from the other frontend services for SAP Fiori. It is part of SAP Gateway server that is deployed in the on-premise system.
  • SAP Fiori Cloud offers a central deployment of the UIs.
  • UI-related front-end components are deployed in the cloud (SAP Fiori Cloud and SAP Cloud Platform). OData provisioning components are deployed on-premise (SAP Gateway).
  • A central management of OData services for multiple SAP application backend systems is achieved by a central SAP Gateway server component (on-premise).
Advantages

Adoption

  • SAP Fiori apps for SAP Business Suite provided in the cloud.
  • Full set of SAP Gateway capabilities is available.

Relation

  • SAP Gateway server manages OData services centrally.
Consider

Relation

  • Setup of multiple backend systems requires the same version of OData service for the selected SAP Fiori application.

Deployment

  • Customer needs to operate and maintain SAP Gateway server.
  • SAP Cloud Platform cloud connector required to establish secure access between customer account and on-premise landscape.
  • Gateway enablement and relevant Fiori backend components are required in the backend application systems at the on-premise landscape.

Go to Top


SAP Business Suite and SAP S/4HANA OP Connector via Discrete SAP Gateway Server


Frontend services for SAP Fiori can be deployed in the cloud as SAP Fiori Cloud and integrated with on-premise applications via an external access point. This deployment option is possible for an on-premise system landscape with Fiori apps in the cloud, while leveraging a central (discrete) SAP Gateway Server in an environment with multiple on-premise systems.

For more information, see External Access Point Landscape.

What's in it?
  • Frontend services for SAP Fiori is decoupled from the backend system (separate shipment of SAP Fiori Cloud). OData service management is offered by SAP Gateway as an on-premise deployment.
  • SAP Fiori Cloud offers a central deployment of the UIs.
  • SAP Fiori FES with SAP Gateway deployed on-premise offers a central enablement of OData access for multiple backend application systems.
Advantages

Adoption

  • Availability of SAP Business Suite and SAP S/4HANA Fiori apps via a cloud subscription.
  • Usage of Fiori 2.0.
  • Automated selection of Fiori app versions that are compatible with the connected backend systems.
  • Full set of SAP Gateway hub capabilities available.

Relation

  • Central SAP Gateway server to manage OData services.
  • Optional SAP Fiori FES embedded deployment in a single system landscape.
Consider

Deployment

  • Additional maintenance and operation of SAP Gateway server by customers.
  • SAP Cloud Platform cloud connector is required to establish secure access between customer account and on-premise landscape.
  • Gateway enablement and relevant Fiori backend components are required in the backend application system.

Go to Top




Other Deployment Scenarios


SAP Fiori with SAP Cloud Platform Mobile Services


SAP Fiori FES can be deployed in a system landscape that is integrated with SAP Cloud Platform Mobile Services. This deployment option is possible in an on-premise system landscape with SAP Fiori FES that is accessed from the internet.





What's in it?
  • Devices in the Internet access the on-premise applications via SAP Cloud Platform Mobile Services (a service on the SAP Cloud Platform).
  • SAP Fiori FES is deployed in the on-premise landscape and is connected to SAP Cloud Platform Mobile Services via the cloud connector.
  • It is possible to add further SAP Cloud Platform services, such as, Web IDE, Mobile Place, Mobile Secure, and so on.
Advantages
  • Effortless access to SAP Cloud Platform Mobile Services features via Cloud subscription (no installation needed).
  • A secure channel from SAP Cloud Platform to SAP system can be implemented via Cloud Connector
  • Possible usage of special mobile features like Fiori offline.
  • SMP administration cockpit offered with example application policies.
  • Logging and tracing features are available.
Consider
  • To access on-premise systems, it is required to set up the cloud connector.

Go to Top


SAP Fiori Mobile with SAP Authenticator Excluding Mobile Platform


SAP Fiori FES can be deployed in a system landscape integrated with mobile devices via the SAP Authenticator app. This deployment option is possible in an on-premise system landscape with SAP Fiori FES that is accessed from the internet.







What's in it?
  • Devices in the internet access the on-premise applications via a Web Application Firewall (on premise) without further mobile platform
  • SAP Fiori FES is deployed in the on-premise landscape and is directly accessed by the mobile devices via the Web Application Firewall.
  • SAP Authenticator is used as an SSO solution for Fiori.
  • Device Web browser or the Fiori Client App is used (configured for usage with SAP Authenticator).
Advantages
  • Easy implementation of an SSO solution based on SAML 2.0 assertion.
  • Easy integration in the existing landscape infrastructure.
Consider
  • SAP Mobile Platform features, such as, working offline and so on, are not available.
  • Separate licensing of SAP SSO 2.0.

Go to Top


Further Sources of Information



Documents

SAP Notes

Other

SAP Community Network

SAP Help Portal

Roadmap

Technical Requirements

Detailed technical requirements, together with complementary information such as product versions, release plans, technical release information and links to downloadable content can be found at the Product Availability Matrix (PAM).

The links below will guide you to the dedicated places for:



  • No labels