FIORI_SAPUI5advanced
Deployment and Lifecycle
Deploying Fiori apps to ABAP and BTP, transports, versioning and caching.
Overview
Deploying Fiori apps to ABAP and BTP, transports, versioning and caching.
Lessons in this topic
- Fiori Deployment Part 1: Deploying to the ABAP Repository and TransportsDeploy UI5 apps to an on-premise ABAP system: deployment with SAP Fiori tools to the UI5 repository as a BSP application, package and transport assignment, app index update, and moving apps through the landscape.
- Fiori Deployment Part 2: Deploying to SAP BTP — HTML5 Repository and Managed ApprouterDeploy Fiori apps on SAP BTP: multi-target applications (MTA) that put apps in the HTML5 application repository, the managed approuter serving them through SAP Build Work Zone, destinations for back-end calls and xs-app.json routing.
- Fiori Deployment Part 3: Versioning, Caching and UI5 Version ManagementKeep deployed apps healthy over time: app versions in the manifest, cache busting so users get updates, choosing and pinning the UI5 version, maintenance of UI5 releases and planning upgrades for custom apps.
Interview questions covered
- Describe how you deploy a Fiori app to an on-premise S/4HANA system.
- How do you deploy and run a Fiori app on SAP BTP that reads data from on-premise S/4HANA?
- How do you keep custom Fiori apps healthy after go-live?