SAP Integration Suite artifacts to get you started with SAP BTP Private Link Service for Azure.
Find my blog post series on the topic here.
The package contains two iFlows. One configured against the CAP implementation and one for Java. They differ due to the chosen router configuration. They can be adapted as required.
| Additional Resources |
|---|
| CAP backend Project |
| Java backend Project using SAP Cloud SDK |
| Fiori Project consuming above backends |
| SAP's official blog |
We used the /sap/opu/odata/sap/epm_ref_apps_prod_man_srv OData service for this project.
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. For this example, 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, SAP CAR etc.
Reach out via the GitHub Issues page of this reposto talk about it some more :-)