✒️Los componentes de la arquitectura SAP Fiori
Los componentes de la arquitectura SAP Fiori
1. Components of SAP Fiori Architecture
- Client: Represents a desktop browser, mobile browser, or SAP Fiori client. In an on-premise scenario, clients access SAP Fiori through the SAP Fiori Launchpad by clicking a link that points to an SAP Web Dispatcher or a front-end server.
- SAP Web Dispatcher: A service between the internet and the client's internal services, usually in a DMZ network zone, used to expose internal services to the internet, adding an extra security layer. Key features include:
- Acts as a reverse proxy with additional functions.
- Helps SAP Fiori applications obtain data from multiple sources.
- Can block or enable access to internal resources.
- Functions as a load balancer if multiple SAP NetWeaver servers are present.
- Front-End Server (FES): The SAP Gateway server hosting the OData service, necessary for SAP Fiori applications to communicate with business data. It also hosts the SAP Fiori Launchpad and all SAP Fiori applications.
- Back-End Server (BES): The primary system where business data and logic reside, implementing an OData service.
- Database: Connected to the back-end server, storing all important business data. This can be any database, including SAP HANA.
- SAP Cloud Platform (SAP Business Technology Platform - SAP BTP): A platform-as-a-service (PaaS) offering from SAP that provides tools and technologies to accelerate application development.
- WEB IDE: A cloud development environment for developing and extending SAP Fiori applications, now using the SAP Business Application Studio (BAS).
- Application Repository: A repository in SAP Cloud Platform storing the user interface (UI) of each SAP Fiori application exposed to SAP Fiori Cloud.
- SAP Mobile Service: A cloud version of the SAP Mobile Platform solution.
- SAP Fiori Cloud: A service that allows hosting applications and the SAP Fiori Launchpad (FLP) in the cloud. It connects to the local back-end system for business data along with OData provisioning, potentially replacing the front-end server.
- OData Provisioning: A service in SAP Cloud Platform for registering and exposing OData services developed in the back-end system.
- Cloud Connector: A lightweight server that is part of the local server infrastructure, exposing the local system to SAP Cloud Platform securely.
2. The SAP Cloud Connector
What is a Connector?
A connector is an application that facilitates communication between SAP and non-SAP systems using different programming languages. SAP connectors enable the integration of various applications and technologies with SAP systems through open standards.
Advantages of Using Cloud Connector:
- No need to configure the local firewall for external access from SAP BTP to internal systems.
- Supports HTTP and additional protocols.
- Connects local databases or BI tools to SAP HANA databases in the cloud.
- Propagates the identity of cloud users securely to local systems.
- Easy to install and configure with standard SAP support.
3. SAP Fiori System Landscape
Main Components:
- Front-End Server (FES): Basic ABAP application server hosting SAP Gateway for OData communication and the central UI for Fiori.
- Back-End Server (BES): SAP Business Suite containing applications and data, with SAP Gateway and ABAP coding for application logic.
4 | Installation Infrastructure
Many clients are hesitant to expose their business data to the cloud but want to benefit from a cloud-based SAP Fiori infrastructure. The styles of installation can be classified based on how the user accesses the SAP Fiori launchpad: from within the network or from the internet.
Based on this, the architectural types are as follows:
- Internal Access Point
- External Access Point
On-Premise vs. Cloud Environments
On-Premise Environment: When we say we have Fiori on-premise, it means it is installed on physical servers at our location. We are responsible for managing all component installations and security. SAP Fiori applications obtain data from SAP via OData services, an open communication protocol based on HTTP. These OData services are created and managed in SAP using a component called SAP NetWeaver Gateway, which retrieves business data through ABAP classes. SAP NetWeaver Gateway comes pre-installed with SAP NetWeaver 7.40.
- Installed on physical servers managed by the business.
- Requires significant investment for hardware configuration, licensing, integration capabilities, and system updates.
- OData services managed via SAP NetWeaver Gateway.
Benefits of SAP Web Dispatcher:
Serves as a single communication point with routing rules to forward requests to the correct systems.
Balances requests efficiently.
Cloud Environment:In contrast to on-premise environments, deploying systems and applications in the cloud is carried out in virtual data centers managed entirely by the cloud provider. Both internal and external users access the SAP Fiori Launchpad by connecting to SAP BTP. SAP BTP connects to on-premise systems via the SAP Cloud Connector, a small server hosted as part of the local network. OData service calls are obtained from the SAP Gateway system through the Cloud Connector.
- Systems and applications deployed in virtual data centers managed by the cloud provider.
- Users access the SAP Fiori Launchpad through SAP BTP.
- OData services routed through SAP BTP without needing a local SAP NetWeaver Gateway.
- Cost-effective with pay-per-use models.
5 | SAP Fiori Architecture
Central Entry Point
SAP aims to establish a central entry point in SAP BTP for users. This means allowing users to access all their applications and navigate between them from a single place, such as for notifications or task searches, with a single sign-on.
SAP Fiori is considered a single point of access for users. The development framework SAPUI5, based on HTML5, JS, and CSS, is used to build Fiori applications. Using these tools, we can access back-end data through OData services and standard internet protocols like HTTP (Rest).
When a user launches the Fiori Launchpad application, the browser loads various UI components and libraries from the front-end server. The front-end server's UI data is then read to understand the user's roles and personalize their experience, including the Fiori Launchpad and individual applications.
Access from Mobile and Classic UIs
Users can access Fiori from Android or iOS devices, which can integrate with the back-end system via the SAP BTP mobile service. Classic UIs can also be accessed using SAP GUI for HTML or Web Dynpro if an SAP S/4HANA or SAP Business Suite system is used as the back-end.
Fiori applications access the back-end via OData services provided by SAP Gateway, a component included in the front-end server.
Sobre el autor
Publicación académica de Jaime Eduardo Gomez Arango, en su ámbito de estudios para la Carrera Consultor en SAP Fiori.
SAP Expert
Jaime Eduardo Gomez Arango
Profesión: Ingeniero de Sistemas y Computación - España - Legajo: SW34C
✒️Autor de: 149 Publicaciones Académicas
🎓Cursando Actualmente: Consultor en SAP Fiori
🎓Egresado de los módulos:
Disponibilidad Laboral: FullTime
Presentación:
Ingeniero de sistemas y computación con 8 años de experiencia el desarrollo frontend & backend (react/node) y en cloud (aws), actualmente desarrollando habilidades en sap btp, ui5, abap y fiori.
Certificación Académica de Jaime Gomez
