CAPM - Side By Side Extension - BTP Deployment - Part 2
HTML-код
- Опубликовано: 10 дек 2024
- CAPM - Side By Side Extension - BTP Deployment - Part 2
CAPM Side By SIde Extension - Part 1: • CAPM Side By SIde Exte...
#CAPM
#Side By Side Extension,
#SidebySide
#SAP
#btp #Deployment
#Destination
Hello Somnath,
It's really a very good video. Clear explanation. Thank you for such videos.👍
Thanks for your valuable feedback. Good to know it was helpful.
Hello Somnath,
Thank you again for making these videos. It keeps us motivated.
You said in the video, that we should be using Principal Propagation instead of Basic Authentication.
But how can we propagate a 'Technical user' using Principal Propagation. There are very few SAP blogs which describes it,
but are not really well documented.
It would be very helpful of you, if you could prepare a video on this topic.
Thanks.
Good to know my little efforts put certain motivations , thank you for your feedback. Principal propagation - is bit deeper concepts of security and i m not a security expert, but will try to explain in my own way in some other video.
Thanks you for sharing this, just a doubt.. why do we use both connectivity and destination service, can't we use only one either connectivity or Destination service to connect the on prem ? Instead of using both together
Great question indeed... Yes we need both as we are using on premise system to get external data. If you use internet based api like northwind .. destination service should be enough. I will encourage to check out part 1 of this topic to get the background more in detail. Thanks for your feedback though.
@@somnathpaul2020 thankyou. Just one more... In case of moving this deployed application to different subaccounts as part of prod movement, what all changes we need to make ?? I have a different name for cloud connector destination in the prod subaccount. Do i need to change the destination name in package json?
@@AbhinandPrem yes you need to create different profiles in package.json file. For production profile you have to maintain the correct destination name. While running application it will be like cds run --profile Production , the correct configuration will be picked up.
Thank you so much
Hello Somnath Da, My destination is working fine when I am testing it locally but after deploying to CF it is failing. The error gives resource-not-found. Ektu help lagbe tomar. LinkedIN e try korlam reachout korar but tomar profile e connect korte parlam na.
I hope you checked entire video and you validated your BTP destination. Is that working fine? Here i showed how we can get data entirely just thru destination using a curl command. Did you get a chance to check that out. Btw it only works from business application studio i think but not from vscode.