Data federation
Reading data that lives in another system as if it were local — by federating the query, by copying the rows, or by caching what was read. Three different answers to one question, and the choice is about how stale you can afford to be.
Showing artifacts, examples and content with confirmed Java applicability. View All CAP
Overview
No SAP artifact is confirmed here for Java.
A Java coverage assessment has not been written. View all flavors
No community artifact is confirmed here for Java.
A Java coverage assessment has not been written. View all flavors
Licence
LicenceSAP Developer License Agreement 3.2 CAP§ 1AlwaysReplication by a covered CAP application moves data from an SAP product into a non-SAP product.
- § 1 License. Productive customer applications are limited to SAP BTP or another SAP-licensed platform, and mass extraction to a non-SAP product is restricted except where solely required for SAP interoperability.
Section 1 restricts mass extraction to a non-SAP product and states a scoped interoperability exception. That boundary is central to a replication design and must be checked against the actual use.
SAP Developer License Agreement 3.2 CAP →Artifacts
Nothing is mapped here yet.
Details
Coverage
Comparison properties
These are the questions used to compare what the artifacts do. Values come from their documentation and may apply to a particular ecosystem or runtime. Each recorded value in the comparison opens its statement and sources.
For your agent
- Ref
capability:replication- JSON
- /capabilities/replication.json
- MCP
- Connecting an agent