Show TOC

Implementation Overview Locate this document in the navigation structure

 

To use the SAP Fiori apps, you need to install the necessary front-end components and the Gateway services to make a connection to the back end possible.

We recommend separating the business logic and the back-end data from the UI layer for the following strategic advantages:

  • Decoupling the lifecycle of the UI apps from the back end, especially for the apps also that run on any database, which has these advantages:

    • Faster iterations for the UI apps

    • Changes to the UI are possible without having development authorizations in the back end.

  • Single point of maintenance for UI issues, such as browser support and updated versions of SAP UI5 libraries

  • Central place for theming and branding SAP Fiori apps

To separate back-end from front-end components, set up SAP NetWeaver Gateway with the deployment option Central Hub Deployment. This means you must install SAP NetWeaver Gateway independent of consumer technologies in a standalone system, either behind or in front of the firewall, depending on whether you want to enable users to consume the Fiori apps only internally or also externally.

In this scenario, the complete UI layer consisting of the central UI add-on, the product-specific UI add-ons and the SAP NetWeaver Gateway is contained in the ABAP front-end server. The central UI add-on contains the SAP UI5 control library and the SAP Fiori launchpad. In addition, the product-specific UI add-ons contain the UI developments for the respective Business Suite product, ERP or SRM. SAP NetWeaver Gateway is a development framework, which offers development and generation tools to create OData services to a variety of client development tools. Put simply, it establishes a connection between SAP Business Suite data and target clients, platforms, and programming framework.

The ABAP back-end server contains the business logic, the back-end data and the integration add-ons for your respective Business Suite product, ERP or SRM.

The SAP Web dispatcher is the entry point for HTTP(s) requests. It can reject or accept connections. When it accepts a connection, it selects an appropriate application server and balances the load to ensure an even distribution across the servers.

The figure below shows an overview of the necessary steps that need to be completed to install and configure Fiori apps.

This graphic is explained in the accompanying text.

Overview of Necessary Implementation Steps

All the steps to install and configure a Fiori app from the figure above are explained below.

  1. Install SAP NetWeaver Gateway components (front end)

  2. Install central and product-specific UI add-ons (front end)

  3. Install integration add-ons for your product (back end)

  4. Configure SAP NetWeaver Gateway (front end)

  5. Configure central UI add-on (front end)

  6. Configure product-specific UI add-ons (front end)

  7. Configure back end (back end)

    Copy and adjust delivered back-end roles and assign users to them.

    For more information, see Installation Overview and Configuration.

More Information

For more information about the installation, configuration and operation of Fiori apps, see Installation Overview and Configuration.

For more information about security, see Security.

For more information about extensibility of Fiori apps (such as adding new fields or layout options), see Extending SAP Fiori Applications.

For more information about the individual Fiori apps (such as the names of the PFCG roles for each app, the name of the gateway service, the system prerequisites), see the functional description and the implementation documentation for each app in the product documentation for the respective product (ERP and SRM).

For more information about SAP NetWeaver Gateway deployment options, see SAP Library for SAP NetWeaver Gateway 2.0 SPS07 on SAP Help Portal at   http://help.sap.com/nwgateway20   Application Help   Support Package 07   SAP NetWeaver   SAP NetWeaver Gateway Master Guide   Deployment Options, and Embedded Versus Hub Deployment  .