When introducing S/4HANA, a Front End Server (FES) must be introduced in case of using APPs instead of classic transactions.
Can FES be in the cloud even if we have ERP on premise? What are the points of attention when defining an authorization model in this context?
SAP FIORI Architecture
We have already discussed this in another post devoted to the subject of SAP FIORI. In addition, it is a "hot" topic being upgraded to the S/4HANA release.
One of the "innovations", there was also in the ECC context the possibility of using Fiori applications (APPs), is to have a Front End Server, which allows the availability of these applications to be managed, connected to a Back End Server (BES) where business information can be retrieved.
One example? I have an application that allows me to approve purchase orders (this is activated in the Front End Server - Launchpad) but the data that this application uses resides in the Back End Server.
Thus, there are different models that can be used at the architectural level. That is, FES and BES on the same machine. Or on different machines. Or even a single FES that "serves" multiple Back Ends. Clearly, each solution must be analyzed in its own context in order to choose the ideal one. Here the various scenarios "SAP Fiori Deployment Options and System Landscape Recommendation".
But can the Front End Server also be in the Cloud?
SAP Fiori Front End Server Cloud
One of the possible scenarios implemented is to use a separate Front End Server. This can clearly reside in the same network as the BES (Back End Server) but can also be in the Cloud.
In fact, there is a specific service in the SAP Business Technology Platform (SAP BTP).
- SAP Cloud Platform (BTP) Portal on Neo
- SAP Cloud Platform (BTP) Portal on Cloud Foundry (CF)
- SAP Cloud Platform (BTP) Launchpad Service (only on Cloud Foundry)
The difference between 1 and 2 above (assuming that the CF part is the newest compared to Neo) is that in Neo the APP applications reside in the portal service proper.
While in CF there may be two different approaches the portal and APPs are in the same repository (Portal and APP) “SAP Fiori Launchpad Module”
or decoupling the portal from the APPs, potentially creating n versions of stand-alone “Portal site”. This second approach is used to potentially create enterprise portals.
In fact, the roles are constructed and APPs are associated to them (these roles are then associated with SITES). And finally to users, via Role Collections.
Users see the APPs based on the groups where the APPs have been placed. Similarly in the on-premise context.
Topics: sap FIORI, SAP Cloud, sap btp, cloud platform