Skip to content

docs: improve on-premise deployment prerequisites and debugging guide #157

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
longieirl merged 1 commit into from
May 21, 2026
Merged

docs: improve on-premise deployment prerequisites and debugging guide #157

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
24 changes: 17 additions & 7 deletions misc/onpremise/deployment.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -16,21 +16,26 @@ Table of Contents

## Prerequisites

Before deploying, confirm the following on your back-end system:
To use the OData service `/UI5/ABAP_REPOSITORY_SRV` to upload an SAPUI5 application, component, or library to the SAPUI5 ABAP repository, ensure the following requirements are met:

- `/UI5/ABAP_REPOSITORY_SRV` is activated.
- You have the required `S_DEVELOP` authorizations.
- Activate the `/UI5/ABAP_REPOSITORY_SRV` service in your back-end system.
- You have `S_DEVELOP` authorisation in your back-end system.
- For SAP BTP destinations, ensure the `HTML5.Timeout` property is configured with a minimum value of `60000`.

For more information, see [Using an OData Service to Load Data to the SAPUI5 ABAP Repository](https://ui5.sap.com/#/topic/a883327a82ef4cc792f3c1e7b7a48de8).
More information about `/UI5/ABAP_REPOSITORY_SRV` and completing these prerequisites can be found [here](https://ui5.sap.com/#/topic/a883327a82ef4cc792f3c1e7b7a48de8).

Any errors during deployment are reported in the HTTP status reports, either success or errors which may have occurred during the operation. The response header or the response body contains additional information, and below is a list of common issues when deploying to an ABAP target system.

---

## Debugging Deployment Errors (HTTP 401 and HTTP 403)

- Review the ABAP transaction logs `/IWFND/ERROR_LOG` and `/IWFND/GW_CLIENT`. These logs indicate missing authorizations and other local issues.
- For more information, see [Deployment to ABAP On-Premise System](https://ga.support.sap.com/index.html#/tree/3046/actions/45995:45996:50742:46000).
- **HTTP 401 Unauthorized** — authentication failed. Check credentials, destination configuration, and trust setup.
- **HTTP 403 Forbidden** — authenticated but missing back-end authorization. Verify `S_DEVELOP` authorisation for your user.

Review the ABAP transaction log `/IWFND/ERROR_LOG` for missing authorization details and other back-end issues.

To capture verbose deployment debug output:
To debug on the client side, capture verbose deployment output by setting the `DEBUG` environment variable before running the deploy command:

```bash
# Mac / Linux
Expand All @@ -40,6 +45,11 @@ DEBUG=* npm run deploy
set DEBUG=* && npm run deploy
```

**Resources**

- [Deployment to ABAP On-Premise System](https://ga.support.sap.com/index.html#/tree/3046/actions/45995:45996:50742:46000)
- Video guide: [Analyzing the `/IWFND/ERROR_LOG` OData Error Log](https://www.youtube.com/watch?v=Tmb-O966GwM)

---

## Connection Test
Expand Down
Loading