onedevatlasBeta
Browse the atlas
AllCAPBTPUI5ABAP
SampleSampletypeA worked example you read or clone. Evidence: it demonstrates, it never provides.See every one →What this type is →independently maintainedindependently maintainedoriginPublished by one person or a small company outside SAP. Says nothing about quality; the readings say that.See every one →Starting point

az-private-linky-cap

A CAP project reaching an S/4 backend through SAP BTP Private Link Service for Azure, with the private hostname and the credentials held in a destination.

A deployable CAP service whose subject is one destination: proxy type PrivateLink, a URL that is a private hostname rather than an internet address, and TrustAll set because, as the README says, CAP v1 does not yet apply a Destination custom trust store. That is what stands in for a Cloud Connector in front of an on-premise system; the README calls it a managed component that exposes SAP backends to BTP on Azure without one, written against S4, with ECC, BO, PI/PO and SolMan named as reachable the same way. The CAP side is thin: it reads /sap/opu/odata/sap/epm_ref_apps_prod_man_srv, deploys as an MTA, and binds the az-destinations SAP Destination service instance through cds bind for hybrid testing. It stops at the backend, since the Fiori front end and the Integration Suite iFlow are separate repositories the README links, and provisioning SAP BTP Private Link Service for Azure itself is outside it.

GitHub0 ★
Issues

Facts

Last push

Where it sits

Lives in
CAP
Demonstrates
DestinationsCAPBTPDestinationscapabilityReaching 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.
Serves
BTP/BAIP
Flavors
Node.jsfrom its runtime
Runs
Cloud Foundryhybrid
Requires
SAP Destination serviceSAP Destination serviceartifactThe private hostname, the credentials and the PrivateLink proxy type are held in a destination named az-destinations, which the deployed application and the local hybrid profile both bind.

Who is behind it

Martin PankrazMartin PankrazPersonMaintains this
In the atlas: maintains 1, contributes to 2, wrote 4@MartinPankrazmaintainer

Before choosing this

Signals

LicenceNo licenseNeither the package manifest nor the repository tree declares a licence

Without a licence the default is all rights reserved. Ask the maintainer, or check for terms stated elsewhere, before depending on it.

What it declares

Every artifact

Type
Sample
Origin
Independently maintained
Runtime
Node.js
Runs on
Cloud Foundryhybrid

As a sample

Form
A tutorial's companion code

Connections2

ArchitectureBetaRead from the sample's deployment descriptor. Some of the connections it states are not drawn yet.

as mta.yaml states it at 32a2b19, read
Download
SAP BTP, Cloud Foundry Runtimeaz-private-linky-capaz-private-linky-cap-srv, nodejsaz-private-linky-cap…SAP Private Link Service, privatelink, standardSAP Private LinkServiceSAP Destination service, destination, liteSAP Destinationservice
SAPnot SAP's, or the project's own

Bound, and not drawn

Documented, with no instance in the document

README

quoted from MartinPankraz/az-private-linky-cap, read
MartinPankraz/az-private-linky-cap/README.mdOn GitHub

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.

excerpt, no licence read, read the rest, on GitHub

Details

Sources3
Added by handdiscovered herechecked
github.com/MartinPankraz/az-private-linky-captree, 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
runtimesnode
deploymentCloud Foundry, hybrid
discovered viaAdded by hand
first seen in the atlas
ecosystem and domaincap, integration-and-messaging
History in the atlas1
  1. First seen.
For your agent
Ref
artifact:martinpankraz-az-private-linky-cap
JSON
/artifacts/martinpankraz-az-private-linky-cap.json
MCP
Connecting an agent