SAP Cloud ALM
SAP's application lifecycle management product, run by SAP as a service: implementation projects with their tasks, requirements, features, documents and test management, and the operations side of a landscape. For the things here it is the system a server reads over the published Cloud ALM APIs, on behalf of an agent.
Where it sits
Used by
Optionally used: the plugin is pointed at a tenant; demo mode shows sample data with no Cloud ALM connection the tenant whose features and transports it reads, with the Cloud ALM API enabled for the calm-api.features.read scope and a client ID and secret in the preferences
Functional boundary
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.
Required dependency. Credentials for SAP Cloud ALM's ITSM API are needed to authenticate and query installation data.
LicenceNeither the package manifest nor the repository tree declares a licence
Dependency relationship. where the four monitoring areas are worked and the data collection runs; part of the landscape the session prepared.
Dependency relationship. the central observability side of exercise 2, with real user monitoring, and one of the two observability tools exercise 1.3 validates the connection to.
Dependency relationship. where the alerts the automation reacts to are raised; access to it is one of the preconfigured prerequisites.
Connected from
data, outbound. Contributing CDS spans into the SAP Cloud ALM agent's tracing pipeline instead of running its own OpenTelemetry SDK.
data, HTTP, outbound, sync. calls the Cloud ALM services for the records an agent asked about, appending each service's path to the tenant's API base
data, HTTP, outbound, sync. fetches the features and transports for the selected ABAP object from the configured tenant at its own address, and times out after a few seconds when that tenant is unreachable
Functional boundary
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.
Details
Graph
For your agent
- Ref
external:sap-cloud-alm- JSON
- /externals/sap-cloud-alm.json
- MCP
- Connecting an agent