Async processing
Doing work outside the request that triggered it, with a guarantee that it eventually happens — deferred jobs, retries, and periodic work. Distinct from messaging, which is about telling other systems.
Showing artifacts, examples and content with confirmed Java applicability. View All CAP
Overview
Exposes CAP's transactional event queues as outbox services. The runtime ships two default outboxes, used internally for messaging and for the audit log, and custom outbox services can be registered for further isolation or scaling.
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§ 1AlwaysA covered CAP application sends SAP product data through an external broker where it is copied, saved or processed in 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.
Messaging is not automatically mass extraction, but an external broker can cross the boundary named in section 1. The data flow, volume and interoperability purpose therefore need to be checked for the concrete design.
SAP Developer License Agreement 3.2 CAP →Artifacts
Details
Coverage
For your agent
- Ref
capability:async-processing- JSON
- /capabilities/async-processing.json
- MCP
- Connecting an agent