SAP Fiori

Deployment Options & Fiori Cloud

16 flashcards · answers and review in the app

Name the two deployment options for the SAP Fiori front-end components and state precisely what sits where in each.
What is the difference between the cloud connector's developer and productive versions, and when does the developer version suffice?
In a central hub deployment, which components run on the dedicated front-end server, and what stays on the back end?
After the cloud connector installation, how do you reach its administration UI, and what are the initial credentials?
Besides a pure on-premise landscape, in which other ways can SAP Fiori launchpad be deployed?
What speaks for an embedded deployment rather than a central hub?
In an embedded deployment, where do the Fiori UI add-ons and SAP Gateway live?
What was SAP Fiori, cloud edition, and what did it promise customers?
What was SAP Cloud Platform — later renamed SAP BTP — positioned as, and what could you build with it?
Classic guidance recommended the central hub deployment. What does SAP recommend for S/4HANA today, and why did the recommendation flip?
In the classic cloud edition architecture, which services ran in the cloud, and how did they reach on-premise data?
Why would an architect pick a central hub deployment for a landscape with several back ends? List its advantages.
After the trust setup with your cloud account, what do you configure in the cloud connector to expose an on-premise system?
In the classic Business Suite era, which Fiori deployment option did SAP recommend, and what was its only listed drawback?
What role does the cloud connector play between cloud services and an on-premise SAP landscape, and in which installation flavors does it ship?
Why was an embedded deployment considered risky for high-load landscapes with several Business Suite systems?
Deployment Options & Fiori Cloud (SAP Fiori) · KnowCard