Skip to content

CAP Project to get you started with SAP BTP Private Link Service for Azure

Notifications You must be signed in to change notification settings

MartinPankraz/az-private-linky-cap

Repository files navigation

az-private-linky-cap

CAP Project to get you started with SAP BTP Private Link Service for Azure.

Find my blog post series on the topic here.

Additional Resources
Alternative Java Project using SAP Cloud SDK
Fiori Project using CAP or Java backend
iFlow example using CAP or Java backend
SAP's tutorial with CF CLI commands
SAP's official blog
SAP's Discovery Center Mission

We used the /sap/opu/odata/sap/epm_ref_apps_prod_man_srv OData service for this project.

Project context

Azure Private Link Service allows private connectivity between resources running on Azure in different environments. That includes SAP's Business Technology Platform when provisioned on Azure. SAP made that functionality available via a CloudFoundry Service.

Meaning you get now a managed component to expose your SAP backends to BTP on Azure without the need for a Cloud Connector. We developed against S4 primarily but anything executable in a service behind the Azure load balancer would be reachable. That involves for instance ECC, BO, PI/PO, SolMan etc.

Architecture overview

Getting Started from SAP Business Application Studio

  • npm install
  • Build mta (Right-Click mta.yaml)
  • Deploy MTA archive (Right-Click mta_archives > az-private-linky-cap_1.0.0.mtar)
  • Maintain your target on the deployed Destination service az-destinations
  • For local testing from BAS use cds bind az-private-linky-cap-srv -2 az-destinations followed by cds watch --profile hybrid
  • For resources only available from SAP Private Link open an SSH tunnel via CF. See this blog post for details.

For those of you looking to get into CAP authentication via XSUAA continue here

Destination config

key value
Name s4test
URL https://[your private hostname]/
Proxy Type PrivateLink
Authentication whatever you have here. We tested Basic Auth initially

If your version of the CloudSDK doesn't support the new ProxyType revert to "Internet". Be aware this is only a configuration issue and by no means does the traffic flow to the internet. It will be resolved by BTP Azure DNS directly to the private link.

Additional Properties

key value
sap-client your client no
TrustAll true
HTML5.DynamicDestination true
WebIDEEnabled true
WebIDEUsage odata_abap

TrustAll needed with https, because CAP v1 does not apply Destination custom trust store yet. See part 7 of the series for details.

Note: Consider upgrading the Cloud SDK for Javascript to support the new proxy type PrivateLink.

Reach out via the GitHub Issues page of this reposto talk about it some more :-)

About

CAP Project to get you started with SAP BTP Private Link Service for Azure

Topics

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published