SampleSampleA worked example you read or clone. Evidence: it demonstrates, it never provides.See every one →What this type is →independently maintainedindependently maintainedPublished by one person or a small company outside SAP. Says nothing about quality; the readings say that.See every one →
cap-cross-container
A sample of five CAP services reading each other's HANA tables across HDI containers, with the grantor service key turned into a user-provided service.
Facts
Last push
Where it sits
Lives in
Demonstrates
Database connectorsCAPDatabase connectorsConnecting an application’s data model and queries to a database, including the differences in supported queries, types and schema management between database implementations. Changing an existing schema belongs to [schema evolution](capability:schema-evolution).Service compositionCAPService compositionBuilding one solution out of parts other projects published: a reuse package brings its models, code, initial data and texts into your project through npm or Maven, you serve what you reference and extend what you import, and the same modules deploy as one application or as several on a shared database. Distinct from [service integration](capability:service-integration), which reaches a service that stays deployed elsewhere, and from [tenant extensibility](capability:tenant-extensibility), which is a subscriber extending a running SaaS.Native SAP HANA artifactsCAPNative SAP HANA artifactsUsing native SAP HANA database objects alongside an application’s generated data model, including objects and database features the modelling layer cannot express. Choosing a database is [database connectors](capability:database-connectors); changing an existing schema is [schema evolution](capability:schema-evolution).
Who is behind it
Mio YasutakeMio YasutakeMaintains this
In the atlas: maintains 47, contributes to 47, wrote 10@miyasutamaintainer
In the atlas: maintains 47, contributes to 47, wrote 10@miyasutamaintainer
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
As a sample
- Form
- A tutorial's companion code
Connections
Group by
NodeRelationBasis
Functional
Database connectorsDatabase connectorsConnecting a data model and its queries to a databaseSAP and community, narrow by design
demonstrates
authored
demonstrates Database connectors
Connecting a data model and its queries to a database
Native SAP HANA artifactsNative SAP HANA artifactsUsing native SAP HANA database objects beside the generated modelSAP only
demonstrates
authored
demonstrates Native SAP HANA artifacts
Using native SAP HANA database objects beside the generated model
Service compositionService compositionBuilding one solution from reuse packages other projects publishedSAP only
demonstrates
authored
demonstrates Service composition
Building one solution from reuse packages other projects published
Download
Learn more
Readings
- How to share tables across different CAP projectsHow to share tables across different CAP projectsFour scenarios for reading one CAP project's table from another, worked out as a matrix of what each one needs: the same HDI container and namespace, the same container under a different namespace, a different container, and a different Cloud Foundry space. The mechanics change with each step — @cds.persistence.exists on the reused entity throughout, an .hdbsynonym once namespaces diverge, .hdbrole and .hdbgrants once containers do, and a user-provided service built from the grantor's credentials once spaces do. The author flags the caveat themselves: these are learning scenarios, and consuming the OData service is often the better answer than reaching into another project's database. Dated corrections from twelve days after publication sit inline — synonyms need only the name because the configuration comes from .hdbsynonymconfig, SERVICE_REPLACEMENTS in mta.yaml removes the hard-coded service name, and the reused container need not be bound to the srv module.published 2021-10-03Mio Yasutake, SAP Community
Architecture
as 5 deployment descriptors state it at 4484080, readNamed in more than one descriptor
master-dbmaster-orgs, master-partners-vendors, master-partners, sales
accountingaccounting/mta.yaml
Download
SAP Authorization and Trust Management serviceThe OAuth server behind a BTP application: issues the JWT the app checks, holds the scopes and role collections it checks against, and brokers trust to an identity provider. Bound, never installed.sap official, btp
accounting-srv → SAP Authorization and Trust Management serviceStated in the descriptor, authentication, HTTP, outboundValidating the JWT a request carries against the keys XSUAA publishes, and fetching tokens from it.
SAPnot SAP's, or the project's ownauthenticationstated in the document
Bound, and not drawn
- accounting-srvhana
- accounting-db-deployerhana, ups-master-db
Documented, with no instance in the document
- @cap-js/hana requires SAP HANA Cloudaccounting-srvconditionalThe database this is the service for: capire's standard database for production, reached with the credentials
cds watchorcds runfetch from the binding at runtime.Using SAP HANA Cloud for Production — capire, Prepare for ProductionThis configures deployment for SAP HANA. The configuration is added to a `[hybrid]` profile in your _package.json_.
Using SAP HANA Cloud for Production — capire, cds deployWith this information, `cds watch`/`run` can fetch the SAP HANA credentials at runtime, so that the server can connect to it.
Databases — capire, overview (the 2 is the page's footnote mark)in production, SAP HANA 2 is used by default
- @sap/xssec requires Cloud Identity Servicesaccounting-srv
Bound in the descriptor, not joined to an entry
hana
master-orgsmaster-orgs/mta.yaml
Download
SAP Authorization and Trust Management serviceThe OAuth server behind a BTP application: issues the JWT the app checks, holds the scopes and role collections it checks against, and brokers trust to an identity provider. Bound, never installed.sap official, btp
master-orgs-srv → SAP Authorization and Trust Management serviceStated in the descriptor, authentication, HTTP, outboundValidating the JWT a request carries against the keys XSUAA publishes, and fetching tokens from it.
SAPnot SAP's, or the project's ownauthenticationstated in the document
Bound, and not drawn
- master-orgs-srvmaster-db
- master-orgs-db-deployermaster-db
Documented, with no instance in the document
- @cap-js/hana requires SAP HANA Cloudmaster-orgs-srvconditionalThe database this is the service for: capire's standard database for production, reached with the credentials
cds watchorcds runfetch from the binding at runtime.Using SAP HANA Cloud for Production — capire, Prepare for ProductionThis configures deployment for SAP HANA. The configuration is added to a `[hybrid]` profile in your _package.json_.
Using SAP HANA Cloud for Production — capire, cds deployWith this information, `cds watch`/`run` can fetch the SAP HANA credentials at runtime, so that the server can connect to it.
Databases — capire, overview (the 2 is the page's footnote mark)in production, SAP HANA 2 is used by default
- @sap/xssec requires Cloud Identity Servicesmaster-orgs-srv
master-partners-vendorsmaster-partners-vendors/mta.yaml
Download
SAP Authorization and Trust Management serviceThe OAuth server behind a BTP application: issues the JWT the app checks, holds the scopes and role collections it checks against, and brokers trust to an identity provider. Bound, never installed.sap official, btp
master-partners-vendors-srv → SAP Authorization and Trust Management serviceStated in the descriptor, authentication, HTTP, outboundValidating the JWT a request carries against the keys XSUAA publishes, and fetching tokens from it.
SAPnot SAP's, or the project's ownauthenticationstated in the document
Bound, and not drawn
- master-partners-vendors-srvmaster-db
- master-partners-vendors-db-deployermaster-db
Documented, with no instance in the document
- @cap-js/hana requires SAP HANA Cloudmaster-partners-vendors-srvconditionalThe database this is the service for: capire's standard database for production, reached with the credentials
cds watchorcds runfetch from the binding at runtime.Using SAP HANA Cloud for Production — capire, Prepare for ProductionThis configures deployment for SAP HANA. The configuration is added to a `[hybrid]` profile in your _package.json_.
Using SAP HANA Cloud for Production — capire, cds deployWith this information, `cds watch`/`run` can fetch the SAP HANA credentials at runtime, so that the server can connect to it.
Databases — capire, overview (the 2 is the page's footnote mark)in production, SAP HANA 2 is used by default
- @sap/xssec requires Cloud Identity Servicesmaster-partners-vendors-srv
master-partnersmaster-partners/mta.yaml
Download
SAP Authorization and Trust Management serviceThe OAuth server behind a BTP application: issues the JWT the app checks, holds the scopes and role collections it checks against, and brokers trust to an identity provider. Bound, never installed.sap official, btp
master-partners-srv → SAP Authorization and Trust Management serviceStated in the descriptor, authentication, HTTP, outboundValidating the JWT a request carries against the keys XSUAA publishes, and fetching tokens from it.
SAPnot SAP's, or the project's ownauthenticationstated in the document
Bound, and not drawn
- master-partners-srvhana
- master-partners-db-deployerhana
Documented, with no instance in the document
- @cap-js/hana requires SAP HANA Cloudmaster-partners-srvconditionalThe database this is the service for: capire's standard database for production, reached with the credentials
cds watchorcds runfetch from the binding at runtime.Using SAP HANA Cloud for Production — capire, Prepare for ProductionThis configures deployment for SAP HANA. The configuration is added to a `[hybrid]` profile in your _package.json_.
Using SAP HANA Cloud for Production — capire, cds deployWith this information, `cds watch`/`run` can fetch the SAP HANA credentials at runtime, so that the server can connect to it.
Databases — capire, overview (the 2 is the page's footnote mark)in production, SAP HANA 2 is used by default
- @sap/xssec requires Cloud Identity Servicesmaster-partners-srv
Bound in the descriptor, not joined to an entry
hana
salessales/mta.yaml
Download
SAP Authorization and Trust Management serviceThe OAuth server behind a BTP application: issues the JWT the app checks, holds the scopes and role collections it checks against, and brokers trust to an identity provider. Bound, never installed.sap official, btp
sales-srv → SAP Authorization and Trust Management serviceStated in the descriptor, authentication, HTTP, outboundValidating the JWT a request carries against the keys XSUAA publishes, and fetching tokens from it.
SAPnot SAP's, or the project's ownauthenticationstated in the document
Bound, and not drawn
- sales-srvhana
- sales-db-deployerhana, master-db
Documented, with no instance in the document
- @cap-js/hana requires SAP HANA Cloudsales-srvconditionalThe database this is the service for: capire's standard database for production, reached with the credentials
cds watchorcds runfetch from the binding at runtime.Using SAP HANA Cloud for Production — capire, Prepare for ProductionThis configures deployment for SAP HANA. The configuration is added to a `[hybrid]` profile in your _package.json_.
Using SAP HANA Cloud for Production — capire, cds deployWith this information, `cds watch`/`run` can fetch the SAP HANA credentials at runtime, so that the server can connect to it.
Databases — capire, overview (the 2 is the page's footnote mark)in production, SAP HANA 2 is used by default
- @sap/xssec requires Cloud Identity Servicessales-srv
Bound in the descriptor, not joined to an entry
hana
README
quoted from miyasuta/cap-cross-container, readmiyasuta/cap-cross-container/README.mdthe maintainer’s wordsOn GitHub
cap-cross-container
CAP Cross container examples
This project is for the following blog post: https://blogs.sap.com/2021/10/03/how-to-share-tables-across-different-cap-projects/
Details
Sources
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 API · miyasuta
first seen in the atlas
ecosystem and domaincap, data-and-persistence
History in the atlas
- First seen.
For your agent
- Ref
artifact:miyasuta-cap-cross-container- JSON
- /artifacts/miyasuta-cap-cross-container.json
- MCP
- Connecting an agent