Everything in the atlas
Type
Domain: 2
Origin
Signals
More: Java
Group by: Kind
Eclipse plugin linking ABAP transports to SAP Cloud ALM features
An Eclipse installation older than the 2026-03 release, or a Java below 21, cannot take it: both are listed prerequisites, and 2026-03 is named as the oldest release the current ADT installs on. The tenant, region, client ID and client secret are entered per installation in Eclipse preferences, so each developer configures the Cloud ALM connection in their own IDE.
CAP Java plugin sending audit log events to SAP Audit Log service
CAP Java handler for SAP Audit Log service API version 2
Change log of annotated entity fields for CAP Java
Reads bound service credentials on SAP BTP, Cloud Foundry for CAP Java
OAuth2 token validation from XSUAA and SAP Cloud Identity Services
Reads SAP BTP Operator service bindings on Kyma for CAP Java
Multitenancy for CAP Java: tenant lifecycle and per-tenant containers
Former XSUAA JWT validation for CAP Java, removed in CAP Java 3.0
Maven bill of materials pinning CAP Java module versions
MCP server for ABAP on the ADT session, in Eclipse or standalone
In the Eclipse mode the server lives in a developer's IDE, binds to 127.0.0.1 and answers any request carrying an `Origin` header with HTTP 403, so a pipeline or a remote agent has nothing to reach; the standalone mode on the runtime of the ADT for VS Code extension is the documented route with no IDE open. A new connection starts in write mode, so the 11 write tools are live against a connected system until someone presses Toggle Read-Only. The dropins route for the two bundles is documented as untested.
CAP Java authorization checks tried case by case
Neither the package manifest nor the repository tree declares a licence.
Ten short CAP Java references, one document per topic