Connecting UI5 Components in BTP CloudFoundry in the same space
In one of my previous blog posts, I explained how to connect UI5 Components in BTP CloudFoundry across spaces. The same problem can occur when using the same space.
Previous blog post: https://blogs.sap.com/2023/11/09/connecting-ui5-components-in-btp-cloudfoundry-across-spaces/
In this blog post, I’m going to explain why this also occurs in the same space and how to solve this.
First, lets deploy both apps to the same space by also deploying app2 to space A.
All-in one space:
Opening app2 in WorkZone will not show app1:
And it will raise the same error:
Both apps/components need to use the same destination service instance. This can easily be solved by changing the destination service instance name in the mta.yaml of app2 to the same as the name of app1:
Build and deploy again.
Once this change has been deployed, the destination service instance of app2 needs to be deleted. In my case this was not cleaned up automatically.
Just delete it if this also occurs for you. I only causes conflicts and should not be used anymore:
In the end we would have only 5 service instances for the two apps:
- 2 times html app repo
- 2 times xsuaa
- 1 destination service instance
Refresh the HTML5 App content
Run the app again in WorkZone:
Both apps are available on GitHub: https://github.com/lemaiwo/ui5-ts-components