Skip to content

Latest commit

 

History

History
88 lines (47 loc) · 4.41 KB

deploying-an-application-1b7a3be.md

File metadata and controls

88 lines (47 loc) · 4.41 KB

Deploying an Application

Deployment Overview

SAP Fiori tools support deployment to ABAP as well as deployment to Cloud Foundry (CF) on SAP Business Technology Platform. In contrast to the SAP Web IDE approach, the deployment target is not required during the application generation which allows a simplified user experience when the project is first created. This approach means that the decision can be deferred until the developer is ready to deploy the application.

Deploying to ABAP

Prerequisite. Ensure all prerequisites are met when using an OData service to load data to the SAPUI5 ABAP repository.

For deployment to ABAP, the SAPUI5 Repository service exposed by the ABAP system is used to upload a deployment artifact. The ABAP backend provides all functionality to run the application, such as hosting, routing, and authentication. As a result, the deployment artifact is just an SAP Fiori application. In other words, it's a zipped dist folder of the SAP Fiori tools project.

For more information see, Deployment to ABAP

Deploying to SAP Business Technology Platform Cloud Foundry

Similar to the SAPUI5 Repository service in ABAP, SAP Business Technology Platform offers an HTML5 Repository to upload and host application. To access the HTML5 Repository, it is required to create an instance of an HTML Repository service. All other functionality required for running the application in an ABAP system comes out of the box and needs to be made accessible by creating instances of the corresponding services.

Deployment Process

The process to deploy the application involves the following steps:

Troubleshooting Tips

The backend system contains the SAP_UI component version 7.53 or newer, but the SAPUI5 repository service cannot be reached.

The SAPUI5 repository service is active and reachable but whenever I deploy an application, I see the following error: Request failed with status code 400.

  • There are multiple reasons for this error. check the console for more information, or open the transaction /IWFND/ERROR_LOG and check the server logs. A common issue is that during the setup, configuring a virus scan profile is forgotten. This can be corrected in the transaction /IWFND/VIRUS_SCAN.

Note:

You can retrieve more detailed logging information when deploying to ABAP by executing the following commands during deployment.

  • For detailed log messages from the backend services during deployment:

    macOS/Linux: DEBUG=ux-odata-client npm run deploy

    Windows: set DEBUG=ux-odata-client & npm run deploy

  • For detailed log messages from archiving and deploying the artefacts:

    macOS/Linux: DEBUG=ux-odata-client npm run deploy

    Windows: set DEBUG=ux-odata-client & npm run deploy

Note:

For any issues, create an incident in SAP Support Portal for the component CA-UX-IDE.

SAP Fiori tools CLI help

SAP Fiori tools CLI offers additional help options to find more information about the various commands and their options for deployment plus other commands.

  • Execute the following command to list all the available commands: npx fiori help.
  • Execute the following command to get the details about a specific command. For example: npx fiori deploy help.