Deploy to different BTP subaccount with Cloud Connector destination

[PetraMi]

Dear experts, please advise how to use the Cloud Connector destination configured on a different BTP subaccount than the one where my MTA app was developed.

My environment:

edit - diagram for the environment

- there are 2 BTP accounts and respective subbacounts, one for SAP BAS and one for SAP Build Work Zone. My app was developed in SAP BAS on the first, and now needs to be deployed to the second

- there is a Cloud connector destination on each BTP account, with principal propagation, towards the same on-premise ABAP system. These destinations have exactly the same name "D1_PP" and identical attributes on both BTP accounts. I already verified both to be working correctly. According to this resource, it should be possible to use the new subbact destination if it has been configured identically:

https://community.sap.com/t5/technology-q-a/deploy-app-from-own-bas-to-custom-cloud-foundry/qaq-p/12...

- on the SAP BAS account there is also an older destination to the same on-prem ABAP with basic authentification. It was used for the development onset but since abandoned. That one has a different name, "D1". Also, the Build Work Zone used to be active on the old account but was since deactivated and is now not available.

- The MTA packaging and deployment was originally carried out when the app was using the old destination D1. It worked there without issues. Only then did the environment changed, removed Build Work Zone subscription from first to second BTP account and created the new destinations D1_PP on both. And the task is now to switch to new destination and deploy to new subaccount

- at the moment there are no issues in either switching in SAP BAS to D1_PP, neither in deployment to new BTP. The app appears in the HTML5 Apps section of the new subaccount, the destination instances appear in the CF space. However the app does not start, with message "...completed with status 500 Error while retrieving destination D1 from destination service. HTTP status code: 404...". So apparently the app is trying to use the old destination, not the new one.

- I did check the xs-app.json, the destination there is correctly set to new name D1_PP. I assume that the old name still lingers somewhere in the MTA files but I do not know where to look.

Thank you in advance for any suggestions how to proceed.

Petra Milinkovic

- 

[PetraMi · Accepted solution]

The solution was to repeat the MTA Build after switching the destination, in exactly the same way as for the initial build:

[WouterLemaire]

As far as I’m aware, xs-app.json should be the place to check.

Can you also check the mta.yaml and package.json?

anyway, have you tried doing a search across your project using the search function in bas? You can search over all the files. Probably somewhere you still use the old destination…