4.0 The Technical Foundation: System Architecture and Key Components
SAP Fiori’s distributed architecture is intentionally designed for security, scalability, and a clear separation of concerns. This model decouples the user interface layer from the back-end business logic, allowing for more flexible and secure deployments. Understanding this architecture is key to planning a Fiori implementation.
The high-level system architecture consists of four primary components:
- SAP Web Dispatcher: This component serves as the initial entry point for all HTTP/HTTPS requests originating from end-user devices. It acts as a reverse proxy, handling web requests and routing them to the appropriate server, and can be configured to accept or reject connections to the Fiori system.
- SAP ABAP Front-End Server: This server contains all the user-facing components. This includes the central UI add-ons, SAP UI5 control libraries, the Fiori Launchpad itself, and SAP NetWeaver Gateway, which facilitates communication with the back-end.
- SAP ABAP Back-End Server: This server houses the core business logic and back-end data. It contains the application data and search models required by the Fiori applications to execute business processes.
- SAP HANA Database and HANA XS Engine: This is the high-performance, in-memory database and its embedded application server engine. It is a mandatory component for running Analytical Apps and Fact Sheets, containing the necessary HANA Live content and Virtual Data Model (VDM) reuse content.
The Pivotal Role of SAP NetWeaver Gateway
SAP NetWeaver Gateway is a critical technology that acts as the bridge between the SAP business suite and various client platforms. It uses OData (Open Data Protocol) services to expose back-end data and functions in a standardized, REST-based format that modern web and mobile applications can easily consume. The deployment strategy for the Gateway has significant architectural implications.
| Deployment Option | Description |
| Central Hub Deployment | SAP Recommended. The Gateway is installed on a dedicated front-end server, separate from the back-end system. This provides a single point of access, enhanced security as there is no direct back-end access, and a central place for UI maintenance and branding. The primary disadvantage is the requirement for a separate server system. |
| Embedded Deployment | The Gateway is installed on the same system as the SAP Business Suite back-end. This reduces a remote call, which can offer a slight performance advantage. However, this approach requires Gateway to be configured multiple times in a multi-system landscape and is recommended by SAP only for sandbox purposes. |
The communication between these architectural layers is standardized through the OData protocol, which enables the flexible delivery and customization of the user experience.