cancel
Showing results for 
Search instead for 
Did you mean: 

Building side-by-side extensions on SAP BTP: error not found after deployment

InesRomero
Discoverer
0 Kudos
260

Hello everyone!

I've been trying to complete this tutorial for a while: https://learning.sap.com/learning-journeys/build-side-by-side-extensions-on-sap-btp/exercise-perform...

I've started from scratch many times, but I always encounter the same error. Everything works correctly until I deploy the application.

After assigning the 'RiskManager' role to my user, I go to the Applications section in my SAP BTP cockpit. I choose the risk-management application:

InesRomero_2-1724673955019.png

When I click on the application route, I get this:

InesRomero_1-1724673135361.png

And when I access locally, this is what I get:

InesRomero_3-1724674080138.pngInesRomero_4-1724674218319.pngInesRomero_5-1724674314727.png

I have already tried to do it by clearing the cache and from an incognito window, but it gives the same error.

Prior to deployment, the application worked fine locally.

Thank you all in advance.



 

goncalvesp
Explorer
0 Kudos

Regarding the deployment, I was getting the same issue as well and after a little more time searching, @Mark_Quincy provided a simple working solution here (basically copy the files generated in the "router" folder into the "app" folder and replace a few things to make it simpler).

Regarding the "Forbidden" error, there are 3 things that matter:

  1. xs-security.json
  2. mta.yaml
  3. role assignment for your trial subaccount user

From my understanding, the roles are generated as soon as you have a successful deployment. If so, that might be your main issue. After that, rebuild and redeploy. If it is successful, you should now be able to assign the roles and use the app.

 

FYI, my deployment after those corrections was still not successful, because I was getting a "no space in device" error in the (deployed) application logs. I fixed it by a combination of two things:

  1. Increasing the memory and disk values for my instance
  2. Adding these as "user variables"  (found here)

 

npm_config_cache: .npmcache
npm_config_prefer_offline: true​

 

After that, everything was working properly!

Accepted Solutions (0)

Answers (0)