Everything in the atlas
Type
Domain: 3
Origin
Signals
More: Java
Group by: Ecosystem
MCP adapter turning a CAP Java service into an MCP server
SAP prohibits gateway/proxy use for SAP Application APIs; the Atlas separately excludes CAP wrappers around those APIs from its assessed scope. Data changes require application-defined unbound actions, and the adapter supplies no rate limiting, agent-action audit logging, approval workflows or policy enforcement.
OData V2 protocol adapter built into the CAP Java runtime
OData V4 protocol adapter for CAP Java Application Services
Connects a running CAP Java app to CAP console for monitoring
Browser dashboard for a running CAP Java service during development
Declarative status-transition flows on bound actions in CAP Java
Triggers n8n workflows from CAP Java through the outbox
Generates Open Resource Discovery documents from a CAP Java model
Maven plugin running CDS build steps in a CAP Java project
Maven archetype generating a new CAP Java project
Maven bill of materials pinning CAP Java module versions
Consumer side of a CAP Java parent pom promotion model with Renovate
Neither the package manifest nor the repository tree declares a licence.
Maven parent pom pinning cds-services-bom and Spring Boot for CAP Java
Neither the package manifest nor the repository tree declares a licence.
CAP Java service consuming a Business Partner API mocked in Node.js
Neither the package manifest nor the repository tree declares a licence.
Ten short CAP Java references, one document per topic
CAP Java service calling role collection APIs via a generated client
Neither the package manifest nor the repository tree declares a licence.
Calling an unbound CAP Java function from freestyle UI5
Neither the package manifest nor the repository tree declares a licence.
Eclipse plug-in turning JSON or XML into ABAP types and DDIC objects
On an [SAP BTP ABAP environment](artifact:btp-abap-environment) system only the generated code is left: DDIC creation is not supported on ABAP Cloud, because classic DDIC object creation over REST is not available there. Create DDIC is also disabled where ADT is not installed in the same Eclipse, and Insert into Editor then works with any editor implementing `ITextEditor` instead of the ABAP one.
Eclipse plugin bringing Claude into ABAP Development Tools
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.