Architecture
The SAP Operation Monitoring Assistant is built in layers, each on an open standard. People ask where they already work; the assistant talks to them over A2A and reaches your systems through MCP servers; governance runs across all of it. Nothing in your SAP products is changed.
Where people ask
The agent, on SAP BTP
Connectors (MCP servers)
Your systems and documents
Governance, across every layer
The layers
| Layer | What it is | How it connects |
|---|---|---|
| Where people ask | SAP Joule, Microsoft Copilot Studio, or another agent | A2A, the open Agent2Agent protocol |
| The agent | The assistant, running on SAP BTP; its language model runs on SAP AI Core | |
| Connectors | MCP servers that give the assistant its tools: AIF, the landscape, SAP Integration Suite, document search and the known solutions | MCP, the open Model Context Protocol |
| Systems and documents | SAP S/4HANA or ECC, SAP Integration Suite, SAP Cloud ALM, and your documents in Amazon S3 or SharePoint | OData services, APIs and confirmed landscape snapshots |
The agent
The assistant is an A2A agent on SAP BTP, Cloud Foundry, deployed with Boidra Platform. When it starts, it reads its configuration from the SAP operations platform (its settings, its tools, its grounding collections and the systems it may read, as set in the Agents app), then connects one MCP client to each tool it was given. Its language model runs on SAP AI Core, and every request is traced in Boidra Platform.
In SAP Joule it comes with a Joule capability of two scenarios: questions, answered in the same response, and restarts, whose result arrives later as an A2A push notification. See Joule & A2A.
The SAP operations platform
Everything the agents share is deployed together, as one platform per SAP BTP subaccount:
| Part | What it does |
|---|---|
Landscape service (lsx-srv, on PostgreSQL) | Keeps the confirmed landscape snapshots and their graph, the configuration of every agent and the known solutions. Its services: LandscapeService for the Connectors app, LandscapeReadService for the confirmed landscape, AdminService for the Agents app, AgentConfigService with myConfig, which each agent reads, and SolutionService for the known solutions. |
MCP server (aif-mcp-server) | One endpoint per domain, each with its own tools and scope (below), and a REST API, /api/aif/v1, for the restart and the cancel of AIF messages. |
| Three SAP Fiori apps in SAP Build Work Zone | Connectors, Agents and Known Solutions. |
| SAP BTP destinations | SAP_OPS_AGENT_CONFIG for the landscape service, and SAP_OPS_MCP_AIF, SAP_OPS_MCP_LANDSCAPE, SAP_OPS_MCP_CIS, SAP_OPS_MCP_GROUNDING and SAP_OPS_MCP_SOLUTIONS for the MCP endpoints: the agents find the platform by these names. Every deploy updates them. |
| Security and audit | Two XSUAA instances, one for the landscape service and one for the MCP server, and the SAP Audit Log service. See Roles & access. |
For demos and tests, the MCP server can read an AIF mock instead of the AIF OData service of an SAP system. Restarts and cancels are switched on only with the mock until SAP's own AIF restart and cancel APIs are verified.
MCP endpoints
| Endpoint | Tools | Scope |
|---|---|---|
/mcp/aif | AIF errors, statistics, interfaces and their configuration, message logs and payloads, value-mapping lookups and the AIF help search; the restart and the cancel of a message | Monitor; Payload for payloads; Restart for the restart and the cancel |
/mcp/landscape | landscape_coverage, landscape_search, landscape_path, landscape_usage, landscape_flows | LandscapeRead |
/mcp/cis | The cis_* tools: SAP Integration Suite errors, message logs, statistics, deployments and expiring certificates | CisMonitor |
/mcp/grounding | grounding_collections, grounding_search | GroundingRead |
/mcp/solutions | solution_search, solution_save, solution_feedback | SolutionRead; SolutionWrite to save |
Versions
| Component | Version |
|---|---|
| SAP operations platform | 0.7.1 |
| The assistant | 0.11.2 |
| Joule capability | 2.3.0 |
Deploy the platform first, then the assistant, whose XSUAA needs the platform's scopes, then the Joule capability.
Governance
Every layer is governed, by tools your administrators already know:
- Boidra Platform registers and approves agents, MCP servers and skills, and shows the traces, usage and cost of every request. See How approval works.
- The Agents app decides what each agent may use: its tools, grounding collections, systems and settings. See Agents app.
- The Connectors app decides what landscape data exists for agents: only confirmed snapshots, without the areas you hide. See Landscape connector.
- The Known Solutions app decides which proven fixes agents reuse: administrators edit, retire and reactivate them. See Known solutions.
- SAP BTP security signs every caller in (SAP BTP XSUAA, SAP Cloud Identity Services), keeps connection details in SAP BTP destinations, and records changes in the SAP Audit Log service. See Roles & access.
Choose your connectors
The connector layer is open. The assistant reaches every source through MCP, and every tool through its own SAP BTP destination. So you can keep the connectors that come with the assistant, or bring a source through the MCP servers you already run:
| Option | When it fits |
|---|---|
| SAP operations MCP server (included) | Ready to use: AIF, the landscape, SAP Integration Suite, grounding and the known solutions, read-only by default |
| SAP Integration Suite MCP Gateway | You expose your APIs through SAP Integration Suite and want one governed gateway for every MCP tool |
| SAP products' own MCP servers | An SAP product offers its own MCP server, and you prefer the vendor's connector |
| Your own MCP servers | Your team built MCP servers for your systems, for example with SAP MCP Builder |
You decide per tool and per system, and you can mix them: for example AIF through the included server and SAP Integration Suite through your MCP Gateway.
How a change works:
- Choose the source for a tool (
aif,landscape,cisorgrounding). - Point that tool's SAP BTP destination at the MCP server you chose.
- We map the assistant's skills to the tools that server offers, as part of the setup.
SAP Joule, the prompts people use and the format of the answers stay the same.
Built on SAP standard, not into it
The assistant uses SAP Joule, SAP AI Core, SAP Integration Suite and SAP BTP as SAP ships them. Removing it leaves your SAP landscape exactly as it was.