CAP Service SDK for Java

Reference Documentation

Getting Started

How to start a new CAP Java project and how to run it locally.

Versions & Dependencies

Learn in this chapter about CAP Java versions and their dependencies.

Working with CDS Models

The Model Reflection API is a set of interfaces, which provide the ability to introspect a CDS model and retrieve details on the services, types, entities, and their elements that are defined by the model.

Working with CDS Data

This section describes how CDS data is represented and used in CAP Java.

Working with CDS CQL

Learn here about working with CDS CQL.

Services

Services are one of the core concepts of CAP. This section describes how services are represented in the CAP Java SDK and how their event-based APIs can be used. One of the key APIs provided by services is the uniform query API based on CQN statements.

CQN Services

CQN Services are the core services of CAP that deal with CDS data. One of the key APIs provided by these services is the uniform query API based on CQN statements.

Event Handlers

This section describes how to register event handlers on services. In CAP everything that happens at runtime is an event that is sent to a service. With event handlers the processing of these events can be extended or overridden. Event handlers can be used to handle CRUD events, implement actions and functions and to handle asynchronous events from a messaging service.

Fiori Drafts

This section describes which events occur in combination with SAP Fiori Drafts.

Messaging

CAP Messaging provides support for publish-subscribe-based messaging, which is an asynchronous communication pattern well suited for scenarios where a sender wants to send out information to one or many receivers that are potentially unknown and/or unavailable at the time of sending.

Audit Logging

Find here information about the AuditLog service in CAP Java.

Change Tracking

Find here information about the change tracking feature in CAP Java.

Transactional Outbox

Find here information about the Outbox service in CAP Java.

Multitenancy

CAP applications can be run as software as a service (SaaS). That means, multiple customers (subscriber tenants) can use the application at the same time in an isolated manner. Optionally, subscriber tenants may also extend their CDS models being served.

Security

Describes authentication and authorization specific for CAP Java.

Spring Boot Integration

This section shows how CAP Java is smoothly integrated with Spring Boot.

Developing Applications

Learn here about developing a CAP Java application.

Operating Applications

Learn here about operating a CAP Java application.

Building Plugins

A collection of different mechanisms that can be used to build plugins for CAP Java.

Migration Guides

This chapter contains comprehensive guides that help you to work through migrations such as from CAP Java 1.x to CAP Java 2.x.