Unable to deploy application with cdm.json – 404 errors in Build Work Zone

[Juliuspereira]

Hello,

Our project involves deploying a Fiori/UI5 application and its associated library to the BTP subaccount DEV_TAL (region: Europe Netherlands – eu20), where deployments through BAS and Cloud Foundry normally succeed without errors. We are encountering persistent issues when attempting to migrate deployment of our application through a cdm.json in SAP Build Work Zone.

When deploying from SAP Business Application Studio via Cloud Foundry (mbt build > cf deploy app.mtar), the process works as expected: the application appears in the HTML5 Applications repository, can be managed in the Content Manager, and finally runs correctly when exposed in a site.

The difficulties arise specifically when switching to a CDM-based deployment. Our goal is to automate group and role creation and ensure consistent provisioning of application tiles. For testing, we are deploying a minimal MTA consisting of one application and one library. After setting up the CDM and RT destinations, creating the content provider, and assigning the required roles to both user and site, the tile appears correctly in Build Work Zone.

However, once launched, the application fails to load properly: in the HTML5 Applications repository, the application runs without errors – the database not being connected is normal at this point. In Build Work Zone, the tile opens but the application immediately crashes with a flurry of 404 errors. As a result, the application does not boot at all, and the intended library resources remain inaccessible.

We have followed the official tutorial Designing UI5 Apps as Business Solution for SAP Build Work Zone and reproduced its GitHub template, but the outcome remains the same. The issue appears to be tied to the CDM integration and how the application accesses its library and resources once deployed in Build Work Zone.

Environment

• Subaccount: DEV_TAL
• Subdomain: dev-tal-ks9oev3t
• Subaccount ID: 8b106794-ec42-4ee1-bacf-a039900b13cb
• Tenant ID: 8b106794-ec42-4ee1-bacf-a039900b13cb
• Org Name (CF): ARGONandCO_dev-tal-ks9oev3t
• Org ID (CF): cafe0aa6-6373-455c-9dd1-f52e2e435364
• Region: Europe (Netherlands) – eu20
• API Endpoint: https://api.cf.eu20-001.hana.ondemand.com
• Space: dev

Reproduction Steps

1. Run mbt to generate .mtar.
2. Deploy via cf deploy app.mtar.
3. Application appears in HTML5 Applications repository in cockpit.
4. Create a Content Provider using both cdm and rt destinations
5. Add role to both User and website
6. Tile appears in BWZ.
7. Launch the tile.

Observed Behavior

• Tile name appears correctly in BWZ.
• In the HTML5 Applications repository: application launches with its library
• In the BWZ: application crashes and shows numerous 404 errors appear in the console.
• Application does not boot.

Expected Behavior

• Application should launch without errors.
• Library should be available, and components should load.
• Groups and roles should be automatically created by CDM.

Tests Performed

• Added and removed the cap-ui prefix to all destinations: no effect, 404 errors persist.
• Changed _schema-version between "3.1" and "3.2" and the the library path from "/cap-ui.argonuilib-1.0.0" to "/cap-ui.argonuilib", as per the template: no effect, same errors observed.

Attachments

• cdm.json
• mta.yaml
• screenshots from BWZ and HTML5 error logs
• manifests of both application and library
• index.html of the application

References

• Tutorial followed: Designing UI5 Apps as Business Solution for SAP Bu... - SAP Community (GitHub template reproduced).

Request

• Confirm whether additional tenant-specific configuration (e.g. contentProvider mapping) is required.
• Clarify which files are critical in CDM deployment that could block the process (mta.yaml, cdm.json, manifest.json, xs-app.json, ui5.yaml…).
• Clarify the pathing necessary to and from the library from the application (e.g. resourceRoots in manifest.json, data-sap-ui-resourceroots in index.html, etc.).
• Clarify where and when the sap.cloud.service should be attached to destinations

mta_yml.txt

lib_manifest_json.txt

cdm_json.txt

app_manifest_json.txt

[Juliuspereira]

Hello jma75,

I assume this is a custom fiori application that you are trying to create and that it works fine when deployed from BAS to BTP CF. I had one question. What do you mean by "switching to a CDM-based deployment." Can you elaborate what exactly you are doing in the CDM-based deployment?

Julius

[jma75]

"Hello Julius, It is indeed a custom application, that currently works fine when deployed from BAS to CF. Currently we are deploying it to the build Work Zone by adding it manually, along with groups and roles. A 'CDM-based deployment' entails the creation and attribution of roles, groups (or spaces/pages) directly through the CDM, so as to automate the manual deployment : the steps we have taken to ensure that: creating a cdm.json and adding it to the mta.yaml creating two routes (design time and run time, so as to add a content provider in the BWZ) Thank you for your answer, and I hope this clear things up."

[jma75]

xxx