LLM integration
In CAP Java the answer is a Maven dependency rather than a cds-plugin: cap-java/cds-aicap-java/cds-aiBridges CAP Java to SAP AI Core and adds AI-powered field recommendations to Fiori draft UIs, as two alpha Maven modules with mock fallbacks for local development.sap official, cap carries the bridge to SAP AI CoreSAP AI CoreSAP's AI service on BTP: the runtime for AI assets, and through the Generative AI Hub inside it the access to foundation models, the orchestration service with its templating, masking, filtering and grounding modules, the Prompt Registry and Document Grounding.sap official, btp and the Fiori field recommendations, and an agent reaches a chat model through the cds-adapter-agent dependency, with LangChain4j's Ollama integration added to srv/pom.xml for a local one. The cds-plugins behind this door do not load here, so an artifact that registers a provider kind under cds.requires.llm answers on the Node.js flavor only.
Showing artifacts, examples and content with confirmed Java applicability. View All CAP
Overview
cap-java/cds-aicap-java/cds-aiBridges CAP Java to SAP AI Core and adds AI-powered field recommendations to Fiori draft UIs, as two alpha Maven modules with mock fallbacks for local development.sap official, cap is the bridge: com.sap.cds:cds-feature-ai-core covers resource group management, deployment lifecycle, configuration CRUD and the prediction API against SAP AI CoreSAP AI CoreSAP's AI service on BTP: the runtime for AI assets, and through the Generative AI Hub inside it the access to foundation models, the orchestration service with its templating, masking, filtering and grounding modules, the Prompt Registry and Document Grounding.sap official, btp, and com.sap.cds:cds-feature-recommendations calls SAP RPT-1 over the same connection for Fiori field recommendations. capire's plugin list says the Java version of the AI plugin is in alpha. An agent reaches a chat model through the cds-adapter-agent dependency, where kind is aicore, ollama or mocked.
Not covered: At the binding, as on Node.js: without an SAP AI Core binding the plugins fall back to mock implementations for local development, and the mocked chat model kind returns static responses without calling any model. The page that configures the chat model marks that configuration alpha, and reaching a model served by Ollama means adding LangChain4j's Ollama integration to srv/pom.xml separately.
No community artifact is documented here.
Licence
LicenceSAP Developer License Agreement 3.2 CAP§ 3AlwaysCovered SAP materials or a covered CAP customer application are used as training data or to develop or refine an AI model or system.
- § 3 Artificial Intelligence Training. The agreement prohibits use of the covered materials and customer applications for training artificial-intelligence models or systems.
Calling a model for inference is not automatically AI training. Section 3 matters when the covered material or application participates in training, model development, refinement or the text-and-data-mining uses it names.
SAP Developer License Agreement 3.2 CAP →Artifacts
Details
Coverage
Comparison properties
These are the questions used to compare what the artifacts do. Values come from their documentation and may apply to a particular ecosystem or runtime. Each recorded value in the comparison opens its statement and sources.
For your agent
- Ref
capability:llm-integration- JSON
- /capabilities/llm-integration.json
- MCP
- Connecting an agent