Deployment
Getting an application onto a runtime and keeping it there — build descriptors, deployment topology and lifecycle on Cloud Foundry or Kubernetes. Cloud Foundry is buildpacks, a manifest and services bound by name; Kyma is Kubernetes with SAP's modules, containers and Helm. Which of the two a subaccount runs decides how every service is bound, how logs are shipped and which tooling applies: an MTA targets one, a Helm chart the other.
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
A Java coverage assessment has not been written. View all flavors
Licence
LicenceSAP Developer License Agreement 3.2 CAP§ 1, 2AlwaysA productive CAP customer application is deployed using materials covered by this agreement.
- § 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.
- § 2 Intellectual Property. The agreement retains SAP's rights in the covered materials and limits making APIs, tools or software available to third parties, while preserving ownership of customer applications subject to SAP's underlying rights.
The CAP-specific agreement makes the deployment platform part of the permitted productive-use condition, so deployment choices need the applicable agreement checked rather than treated as purely technical.
SAP Developer License Agreement 3.2 CAP →Artifacts
Details
Coverage
For your agent
- Ref
capability:deployment- JSON
- /capabilities/deployment.json
- MCP
- Connecting an agent