Name: Deploying Your App Manually Using SAP Fiori Tools
Uploaded: 2024-7-11
Duration: 116 s
Description: Learn about manual deployment of SAP Fiori elements apps using SAP Fiori tools.

<p>about your learning experience to help us improve.</p>

You've completed

cleanFiles/bookmap_enter_course_title_en-US_learning-sap-com_lsc-prod.zip (MMCP-DROPZONE) - 2025-02-28T12:44:05.000Z

Getting an Overview of the Deploy Options

<div id="content"><p tabindex="0">Watch the following video to get an overview on how to deploy your app manually using SAP Fiori Tools.</p><div class="kalturaVideoLessonWrapper"><div aria-label="Learn about manual deployment of SAP Fiori elements apps using SAP Fiori tools." class="kalturaVideoLessonContainer" data-testid="video" id="1_sej2qib8"></div></div></div>

Deployment of an SAP Fiori Elements App

Getting Started with Creating an SAP Fiori Elements App Based on an OData V4 RAP Service

<div><div><div><div>Learn about manual deployment of SAP Fiori elements apps using SAP Fiori tools.<br></div></div></div></div>

Deploying Your App Manually Using SAP Fiori Tools

When talking about deployment, we can basically distinguish two methods. Manual deployment and automated deployment as part of a pipeline. In most productive environments, an automated deployment to quality and productive accounts is configured and set up. In this course, we look at manual deployment, which can be done by the developer to validate her or his work into a development account. SAP Fiori tools helps you to manually deploy your app to different targets as single applications or so-called multi-target applications, which bundle several deployment artifacts together. In addition, SAP Fiori tools helps to add the SAP Fiori Launchpad configuration. The actual deployment consists of two steps. First, we need to create a configuration for the deployment. The configuration contains information about the application like ID, name, dependencies and destinations of our data services. The configuration remains the same as long as the environment you deploy to doesn't change. If there are changes, for instance, you want to deploy to another account, you need to update the configuration or create a new one. Second, we trigger the actual deployment, which will upload the package and make it available in the account. This will store and register applications in the HTML5 application repository at the required destinations and authorization services. These steps need to be repeated every time the application itself changes and you want the changes to be reflected in the deployed application.