Lesson 1 of 5
Hybrid landscape reality
9 min
Listen to this lesson
After go-live, Contoso's landscape is not one system. Production runs in CMP, SAP S/4HANA Cloud Private Edition under RISE. Integration flows for bank statements and supplier messages run in SAP Integration Suite on Contoso's SAP BTP subaccount. EDI orders and invoices with Great Lakes Fleet Services pass through it to the customer's systems. The legacy ECC systems stay read-only for audit until they are retired, still watched by SAP Solution Manager 7.2. And from Wave 2, company code 1910 brings Monterrey users, interfaces and jobs into the same CMP. A business process such as order to cash crosses several of these components on every order.
Who sees what
Every layer has its own observers. Under RISE, SAP ECS monitors system availability and critical technical states as a standard service; SAP's roles and responsibilities document notes that this does not include solutions, customer configuration, interfaces, connections and jobs. SAP reports the status of its cloud services in SAP for Me. The ECC support team still has Solution Manager. None of these on its own answers the question Maria asks at 7 a.m.: did last night's orders, deliveries and invoices go through?
| Component | Monitoring options | Notes |
|---|---|---|
| CMP, CMQ (private edition) | SAP Cloud ALM: health, integration and exception, job and automation, business process, real user monitoring | SAP ECS's own technical monitoring runs in parallel under RISE |
| SAP Integration Suite on SAP BTP | SAP Cloud ALM integration and exception and health monitoring | BTP cloud services are imported into Cloud ALM landscape management from SAP's system landscape information service |
| SAP cloud service status and maintenance | SAP Cloud ALM Business Service Management, fed from SAP for Me events | Shows disruptions and maintenance per business service |
| Read-only ECC and Solution Manager | SAP Solution Manager 7.2 until retirement | Mainstream maintenance ends 31 December 2027 |
| Web front ends and partner-facing URLs | Real user monitoring and synthetic user monitoring in SAP Cloud ALM | Outside-in view of what users experience |
Components and their monitoring options at Contoso. Supported products change; check SAP's expert portal.
Choosing the platform
SAP's ALM FAQ positions SAP Cloud ALM for cloud-centric solutions and states that RISE includes the Cloud ALM entitlement. It positions SAP Focused Run, a separately licensed product, for end-user and integration scenarios that span large on-premise and cloud estates and as the platform for service providers. SAP's 2026 Cloud ALM operations strategy deck repeats the advice: start with SAP Cloud ALM, and consider Focused Run for customers keeping a large on-premise footprint, needing more flexible custom extensions, or unable to use any SAP cloud solution. Contoso's estate is cloud-centric after the conversion, so Cloud ALM is the operations home; Solution Manager covers the shrinking ECC remainder until it retires.
- Is the estate mainly SAP cloud services and private cloud ERP?Yes → SAP Cloud ALM as the operations home · No → next question
- Will a large on-premise footprint stay for years, or are custom monitoring extensions essential?Yes → evaluate SAP Focused Run · No → SAP Cloud ALM
- Is a provider monitoring many customers?Yes → Focused Run is SAP's suggestion · No → Cloud ALM
- Is legacy SAP Solution Manager still running?Yes → plan its retirement and the remaining scope · No → one home
Whatever the platform, the first design artifact is a monitoring map: every component, its owner, which tool observes it, which signals are collected and who receives them. Gaps show up immediately. In Contoso's first draft, the bank statement flow in Integration Suite had no owner, and the Monterrey plant's label printers were monitored by nobody at all.
What would you do?
Grace asks whether Contoso still needs its own monitoring at all, since SAP ECS monitors CMP around the clock under RISE. What should Sam answer?
- A hybrid landscape spans private cloud ERP, SAP BTP, SAP cloud services, on-premise remnants and partners; processes cross all of them.
- Under RISE, SAP's standard monitoring covers technical availability, not interfaces, jobs or business processes.
- SAP positions Cloud ALM for cloud-centric estates (included with RISE) and Focused Run for large hybrid estates and providers.
- Start with a monitoring map: component, owner, tool, signals, recipients.
Check your understanding · not graded
Lesson check
1. According to SAP's ALM FAQ, which product is positioned for service providers monitoring many customers?
2. How are subscribed SAP BTP cloud services usually brought into SAP Cloud ALM landscape management?
3. What is the first design artifact for operations in a hybrid landscape?
4. Which question shows why platform monitoring alone is not enough for Contoso?