Independent engineering prototype with bounded live execution evidence

ABAP4C Cloud Deployment Pipeline — Architecture 2: Capella

Capella Governed Bridge — ABAP Cloud deployment sometimes needs a dedicated control plane, local Eclipse bridge, bounded execution controls, receipts and recovery evidence rather than a direct tool invocation path alone.

Ask Twin about this

Representative image

Architecture visual

Shown when a public-safe visual is available for this architecture; otherwise a neutral placeholder is used instead of a broken-image icon.

Context

Who it serves and what it addresses

AI or Coding Agent → VS Code / Cline / Python → Capella Control Plane → Local Eclipse Bridge → ADT / RIS / DDIC execution → SAP ABAP Cloud → receipts, evidence and rollback controls.

Intended users: SAP architects, platform owners, governed-delivery teams and automation engineers needing evidence-first ABAP Cloud deployment controls
Data dependencies: Approved Eclipse workspace session, ADT repository discovery, RIS search, DDIC update evidence, stateful session evidence, receipts and rollback references.
Last reviewed: 2026-07-27
Maturity: Independent engineering prototype with bounded live execution evidence

Core components

Verified architecture vocabulary

Architecture relationship

How the capability connects

Agent Hub: Represents the governed-bridge route for ABAP Cloud deployment when policy, recovery and receipts matter.

Engineering Control Center: Capella-style execution is governed through explicit lifecycle, validation, approval, execution receipts and rollback references.

Architecture 2 of the ABAP4C Cloud Deployment Pipeline capability: a Capella governed bridge with orchestration, policy controls, local Eclipse bridge, authenticated workspace, ADT repository discovery, RIS search, DDIC update, session handling, controlled retry, receipts and rollback references.

Governance and publication

Control and confidentiality boundaries

Live-verified and unverified object types are separated. Controlled retry and recovery are bounded by evidence receipts and human approval gates.

Public description excludes credentials, tenant details, local bridge secrets, private repository data and unrestricted SAP system evidence.

Publication boundary: Architecture-level description with bounded live-execution evidence language.
Source availability: Selected public architecture material may be released separately
Future direction: Improve target-system variation handling and recovery evidence without claiming universal superiority over Architecture 1.

Connected from existing metadata

Not yet published: 1 related item identified but hidden until the exact public URL is verified. No broken actions are rendered.