Julie has built the SAP Fiori app that complies with all SAP Fiori guidelines and is based on user requirements.
So what comes next?
Marco and Julie both agree that SAP Fiori apps need to be launched from SAP Fiori Launchpad. Let's see why and how?
The launchpad home page presents tiles that allow the launch of apps, and may show additional information. The page can be personalized. Tiles can be added or removed and bundled in groups.
The tile catalog has two functions:
Tiles that are used most often can be added to the Home page
Tiles, that are used more seldom, can be accessed directly from the catalog, without adding them to the Home page
The tile catalog is provided by the SAP Fiori launchpad.
Overview of SAP Fiori Launchpad Architecture
To fully understand how SAP Fiori Launchpad supports SAP Fiori apps, lets look at the architecture of SAP Fiori Launchpad.
- ( a ) FioriLaunchpad.html: FioriLaunchpad.html is at the center of the SAP Fiori Launchpad architecture and act as the central point of entry to the SAP Fiori Apps.
- ( b ) Runtime Configuration - The Launchpad gets the RuntimeConfiguration from the SAP-system, containing the configuration provided by the SAP-system.
- ( c ) Shell Container - The so-called Shell Container is responsible for providing all relevant services like personalization or navigation to applications that are executed inside the SAP Fiori Launchpad.
- ( d ) Application Container - SAP Fiori applications are executed inside the so-called application container.
- ( e ) Shell Services - Each application can access the platform-independent shell service through the API of the shell container. Services that need platform-specific data handling or connection management use platform-specific adapters.