onedevatlasBeta
Browse the atlas
AllBTPCAPUI5ABAP
SampleSampletypeA worked example you read or clone. Evidence: it demonstrates, it never provides.See every one →What this type is →by SAPby SAPoriginPublished by SAP itself. A visible facet, never an input to a reading — a dormant official plugin reads exactly like a dormant independent one.See every one →Reference

btp-private-link-approuter

Configuration patterns that put @sap/approuter in front of SAP Private Link Service, for the two SAP services that cannot use it directly yet.

Cloud Integration and SAP Build Work Zone, standard edition cannot use SAP Private Link Service directly, which the README states each time it says the product team is working on direct integration. The repository bridges that gap with @sap/approuter as a proxy, across three scenarios with their own configuration steps: Cloud Integration to an SAP S/4HANA system on Microsoft Azure, frontend extensions of that system surfaced through Build Work Zone, and Azure Blob Storage reached from Cloud Integration. The frontend scenario covers the extensions themselves; the README puts federated SAP S/4HANA content out of scope.

GitHub11 ★

Facts

Last pushLicenceApache-2.0

Where it sits

Lives in
BTP/BAIP
Demonstrates
DestinationsBTPDestinationscapabilityReaching a system that is not yours — an S/4HANA tenant, an on-premise service, a third-party API — without the address, the credentials or the tunnel being written into the application. The destination is the indirection, and the reason an endpoint can move without a redeploy.
Requires
@sap/approuter@sap/approuterartifactthe proxy every scenario is built on, configured per use case in its own directorySAP Private Link ServiceSAP Private Link Serviceartifactthe private network connectivity to the backend that each scenario is arranged around
Optional
Cloud IntegrationCloud Integrationartifactthe consumer in two of the three scenarios, reaching SAP S/4HANA on Azure and Azure Blob Storage through the proxySAP Build Work Zone, standard editionSAP Build Work Zone, standard editionartifactwhere the frontend extensions are accessed from in the second scenarioSAP S/4HANASAP S/4HANAoutside the atlasthe backend system the private connectivity reaches in the first two scenarios

Who is behind it

SAP SamplesSAP SamplesOrganisationMaintains this
In the atlas: maintains 222@SAP-samplesmaintainerAjinkya PatilPersonContributes to this
In the atlas: contributes to 112@ajinkyapatil8190Brian BernardPersonContributes to this
In the atlas: contributes to 64@btbernardDominik HeimPersonContributes to this
In the atlas: contributes to 25@heimwegeHarut Ter-MinasyanPersonContributes to this
In the atlas: contributes to 3@hterminasyan4 contributors

What it declares

Every artifact

Type
Sample
Origin
By SAP
Use as
A reference

As a sample

Form
does not say

Connections6

Download
btp-private-link-approuter connectionsbtp-private-link-approuterPROVIDES→ demonstrates1demonstrates authoredDestinationsNEEDS→ needs2needs stated the proxy every scenario is built on, configured per use case in its own directory SAP-samples/btp-private-link-approuter — README, SAP Private Link service with SAP Cloud Integration: https://github.com/SAP-samples/btp-private-link-approuter SAP-samples/btp-private-link-approuter — README, How to achieve this?: https://github.com/SAP-samples/btp-private-link-approuter@sap/approuterneeds stated the private network connectivity to the backend that each scenario is arranged around SAP-samples/btp-private-link-approuter — README, SAP Private Link service with SAP Cloud Integration: https://github.com/SAP-samples/btp-private-link-approuterSAP Private Link Service→ optionally needs3optionally needs stated If: the Cloud Integration scenarios; the frontend-extension scenario uses SAP Build Work Zone, standard edition instead the consumer in two of the three scenarios, reaching SAP S/4HANA on Azure and Azure Blob Storage through the proxy SAP-samples/btp-private-link-approuter — README, Description: https://github.com/SAP-samples/btp-private-link-approuter SAP-samples/btp-private-link-approuter — README, Azure Blob Storage connectivity: https://github.com/SAP-samples/btp-private-link-approuterCloud Integrationifoptionally needs stated If: the frontend-extension scenario; the other two scenarios run with SAP Cloud Integration where the frontend extensions are accessed from in the second scenario SAP-samples/btp-private-link-approuter — README, SAP Private Link service for frontend applications: https://github.com/SAP-samples/btp-private-link-approuterSAP Build Work Zone, standard editionifoptionally needs stated If: the two SAP S/4HANA scenarios; the third reaches Azure Blob Storage instead the backend system the private connectivity reaches in the first two scenarios SAP-samples/btp-private-link-approuter — README, SAP Private Link service with SAP Cloud Integration: https://github.com/SAP-samples/btp-private-link-approuter SAP-samples/btp-private-link-approuter — README, SAP Private Link service for frontend applications: https://github.com/SAP-samples/btp-private-link-approuterSAP S/4HANAif

README

quoted from SAP-samples/btp-private-link-approuter under Apache-2.0, read
SAP-samples/btp-private-link-approuter/README.mdOn GitHub

SAP Private Link Service Use Cases for SAP Cloud Integration and SAP Build Work Zone, Standard Edition

REUSE status

Description

SAP Private Link service with SAP Cloud Integration for building diverse integration scenarios

The SAP Cloud Integration capability of SAP Integration Suite enables enterprises to connect different systems and applications in hybrid and cloud landscapes, that are developed and maintained on different technology stacks. These stacks, usually follow different security standards and requirements.

With the help of the SAP Private Link service, you can extend your hybrid integration scenarios to suit stricter security policies and communicate with your SAP S/4HANA on Microsoft Azure through private network connectivity.

The main idea of this architecture is to use the Application Router as a proxy for the private connectivity between SAP S/4HANA and SAP Cloud Integration. The detailed configuration steps can follow here.

Please note that for the moment, we cannot use SAP Private Link service directly from SAP Cloud Integration; nevertheless, we can bridge this gap with help of SAP’s Application Router (approuter), which can play the role of a proxy between SAP Private Link service and SAP Cloud Integration, meanwhile product team is working to enable direct integration.

solution diagram

SAP Private Link service for frontend applications accessible from SAP Build Work Zone, Standard Edition

SAP Build Work Zone, Standard Edition plays an important role to increase users’ productivity and efficiency by enabling organizations to establish a central point of access to SAP, custom-build, third-party applications, and extensions.

The frontend extensions of your SAP S/4HANA system running on SAP BTP can now also benefit from the new SAP Private Link service by establishing private connectivity to your SAP backend systems.

Like the above-mentioned scenario, the main idea of this architecture is to use the Application Router as a proxy for the private connectivity between SAP S/4HANA and frontend extensions running on SAP BTP. Detailed configuration steps can be found here.

Please note that for the moment, we cannot use SAP Private Link service directly from SAP Build Work Zone; nevertheless, we can bridge this gap with help of SAP’s Application Router (approuter), which can play the role of a proxy between SAP Private Link service and SAP Build Work Zone, Standard Edition, meanwhile product team is working to enable direct integration.

Please note that this scenario covers only the frontend extensions. The federated SAP S/4HANA content is out of scope.

solution diagram

Azure Blob Storage connectivity to SAP Cloud Integration with help of SAP Private Link service

With the help of the SAP Private Link service, Azure Blob storage can now be linked to SAP Cloud Integration, enabling the easy exchange of massive amounts of unstructured data like images and documents. This integration provides a secure solution for businesses that need to transfer unstructured data between the two platforms.

The main idea of this architecture is to use the Application Router as a proxy for the private connectivity between Azure Blob Storage and SAP Cloud Integration. The detailed configuration steps can follow here.

Please note that for the moment, we cannot use SAP Private Link service directly from SAP Cloud Integration; nevertheless, we can bridge this gap with help of SAP’s Application Router (approuter), which can play the role of a proxy between SAP Private Link service and SAP Cloud Integration, meanwhile product team is working to enable direct integration.

solution diagram

How to achieve this?

Application Router is a package available in the public npm repository, usually used as a single-entry point to your applications. It can help dispatch incoming requests to other microservices, facilitate authentication & authorization, and finally integrate other SAP BTP services like the Destination service or the HTML5 Application Repository.

These main capabilities of the Application Router with the latest release (as of today - 11.3.2) can help you establish the above-mentioned proxy role for Private Link.

The detailed configuration of the Application Router you can find in usecase details.

Known Issues

No known issues.

How to obtain support

Create an issue in this repository if you find a bug or have questions about the content.

For additional support, ask a question in SAP Community.

Contributing

If you wish to contribute code, offer fixes or improvements, please send a pull request. Due to legal reasons, contributors will be asked to accept a DCO when they create the first pull request to this project. This happens in an automated fashion during the submission process. SAP uses the standard DCO text of the Linux Foundation.

License

Copyright (c) 2022 SAP SE or an SAP affiliate company. All rights reserved. This project is licensed under the Apache Software License, version 2.0 except as noted otherwise in the LICENSE file.

Apache-2.0, read

Details

Sources3
GitHub organisations and accountsdiscovered herechecked
github.com/SAP-samples/btp-private-link-approutertree, pushes, contributors, CIchecked
README.mdquoted, and what the entry declareschecked

Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.

Compatibility and provenance
discovered viaGitHub organisations and accounts
first seen in the atlas
ecosystem and domainbtp, integration-and-messaging
Contributors4
Ajinkya PatilBrian BernardDominik HeimHarut Ter-Minasyan

From the repository’s contributor list, .

History in the atlas1
  1. First seen.
For your agent
Ref
artifact:sap-samples-btp-private-link-approuter
JSON
/artifacts/sap-samples-btp-private-link-approuter.json
MCP
Connecting an agent