week 1: introduction unit 1: sap cloud alm for operations

Week 1: Introduction

Unit 1: SAP Cloud ALM for Operations in a Nutshell

2PUBLIC© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ

SAP Cloud ALM for operations in a nutshell

openSAP course overview

Week 1

Introduction

Week 4

Week 2 Monitoring and Alerting

Week 3 Event Management

Final Exam

Weekly assignment

Video 1 Self-test 1

Video 2 Self-test 2

Video 3 Self-test 3

Video 4 Self-test 4

Weeks 1 through 3

▪ 4-5 video units and self-tests

▪ 1 weekly assignment

▪ Online discussion forum (collaborate, ask questions)

▪ ~3-4 hours of effort each week

Week 4

▪ Final exam

Record of achievement

▪ Collect at least 50% of the total points available in all

online tests during the course



Why do we need a central operations platform for cloud-centric landscapes?

Lead-to-Cash

Create

Order

Create

Invoices

Fulfill

Order

Collect

Cash

Sell

Product

Market

Product

SAP S/4HANA

SAP Service

Cloud

SAP Customer

Data Cloud

SAP Marketing

Cloud

Lead-to-Cash

Create

Order

Create

Invoices

Fulfill

Order

Collect

Cash

Sell

Product

Market

Product

SAP Business Technology Platform

SAP S/4HANA

SAP Sales

Cloud

SAP Commerce

Cloud

SAP S/4HANA

SAP Subscription

Billing

SAP Global

Track and Trace

SAP S/4HANA

SAP Commerce

Cloud

SAP Revenue

Cloud

SAP Commerce

Cloud

SAP Revenue

Cloud

Challenges:

▪ Transformation from a monolithic to a multi-

service landscape

▪ Increased complexity to find and analyze

issues in a distributed environment

▪ Increased need to consider business

processes end-to-end

Answers:

▪ To find and analyze anomalies during business

process execution ➔ business process

monitoring

▪ To identify and correct message flows and

integration-related exceptions ➔ integration

and exception monitoring

▪ To diagnose performance of user scenarios ➔

real user and performance monitoring

▪ To understand healthiness of applications, cloud

services and systems ➔ application

monitoring and health monitoring

SAP ERPSAP CRM



Different strategic operations platforms for different target groups

SAP Cloud ALMSAP Focused Run

▪ Fully integrated ALM suite for

on-prem-centric medium and

larger customers

▪ Customers who are satisfied

with the currently provided

functional scope

▪ Operations platform for service

providers and high-end hybrid

customers

▪ Customers with advanced needs,

which go beyond SAP Solution

Manager and SAP Cloud ALM

▪ Fully integrated ALM suite for

cloud-centric small, medium,

and larger customers

▪ Customers who request

standardized cloud-based

operations platform

+

SAP Solution Manager



SAP Cloud ALM – a brand-new, cloud-based ALM offering

For the Intelligent Enterprise

▪ For cloud-centric customers

▪ Manages cloud and hybrid solutions

▪ Supports all components of the

Intelligent Enterprise

In the public cloud

▪ Rethought, newly designed, and built

on modern cloud technology

▪ Immediate consumption, always up to date

▪ Cost-efficient for customers

is cloud-native and open

SAP Cloud ALM

Fair usage rights included with SAP Enterprise Support, cloud editions



SAP Cloud ALM for operations – value proposition

Ensure business continuity in your SAP landscape by monitoring and alerting – Increase operating

efficiency by automating operational tasks – Avoid anomalies by proactive problem prediction

▪ SAP Cloud ALM enables customers to increase operational efficiency by

automating corrective actions as well as regular operational tasks

▪ SAP Cloud ALM helps to predict anomalies in business process

and application operation by event correlation and learning out of

the collected data (AI Ops)

▪ SAP Cloud ALM provides transparency regarding availability of

business services, including business downtimes, business events

and business SLAs

SAP Cloud ALM empowers customers to understand the healthiness

of SAP business solutions:

▪ Provides full-stack monitoring and alerting covering business

processes, integration, users, applications, and healthiness of cloud

services and systems

▪ Allows to conduct root cause analysis on technical as well as on

business process level

▪ Acts as collaboration platform between LoB and IT


External monitoring, event & alerting

infrastructures – Integrated with SAP Cloud ALM

Health monitoring – Focused on technical

healthiness of cloud services and systems

Embedded

operation

automation

Execution of

corrective

actions

triggered by

events to

reduce mean

time-to-

resolution

Automation of

regular

operations

tasks to

increase

efficiency and

quality

Job & automation monitoring – Focused on

application aspects as jobs and automation

Integration & exception monitoring – Focused

on integration flows and integration exceptions

User & performance monitoring – Focused on

performance and usage for synthetic & real user

Business process monitoring – Focused on

business process KPIs and documentsEmbedded

alert

management

Calculation of

use case-

specific alerts

based on

dedicated

thresholds

Unified alert

handling and

follow-up

activities

Support of

alert grouping

and atomic

alerts

Business service management – Provides transparency for business service availability, including business downtime

management, business event calendar, business SLA management, and business event management

Embedded

analytics &

intelligence

Allows use

case-specific

root cause

analysis

Works on

real-time/raw

data as well

as historical/

aggregated

data

Includes

machine

learning and

prediction

Intelligent

event

processing

Central event

hub to

connect

different use

cases with

each other

Enables

event

correlation

Is open for

inbound and

outbound

event

processing


SAP Cloud ALM for operations – available and planned scope in detail

Incident

management

External

analytics &

intelligence

Collaboration

management

External

automation

management

U

n

i

f

i

e

d

A

P

I

L

a

y

e

r



Cloud ALM for operations – use cases

▪ Business process monitoring

▪ Integration and exception monitoring

▪ Real user and performance monitoring

▪ Job and automation monitoring

▪ Health monitoring

▪ Intelligent event processing

▪ Business service management



Problem management covered by SAP Cloud ALM

External Monitoring, Event and

Alerting Infrastructures

Health Monitoring

Job and Automation Monitoring

Integration and Exception

Monitoring

User and Performance Monitoring

Business Process Monitoring

Problem Detection Problem Routing

* Planned functionality

Intelligent Event

Processing

Embedded Alert

Management

Operation Automation

Embedded

Operation

Automation*

External

Automation

Management

Embedded Channels

eMail Chat*

Ticket*Instant

Messages*

Problem Resolution

Root Cause Analysis

Embedded

Analytics &

Intelligence

External

Analytics &

Intelligence*

Generic Channels*

Incident

Management

Collaboration

Management



Business process monitoring

KPI 1

Customer Landscape

(Cloud and On-Premise)

Business Processes of the Intelligent Suite

KPI 2 KPI n

Visualize process performance and disruptions

Identify business disruptions and exceptions

Business

Process

Monitoring

▪ Provides transparency on end-to-end

business processes within a distributed

and hybrid solution landscape

▪ Ensures business continuity to increase

business process execution quality and

performance

▪ Monitors processes’ health and detects

anomalies during process execution,

including drill down in business

documents

▪ Alerts users directly on process

disruptions, including automated

problem resolution

▪ Delivers predefined process content,

including auto-discovery of relevant

business process KPIs to be switched on


▪ End-to-end monitoring by

correlating single messages

to end-to-end message

flows across cloud services

and systems

▪ Monitoring of integration-

related exceptions

▪ Support for peer-to-peer

interfaces as well as

orchestrated integration

▪ Supports efficient problem resolution process and

collaboration between business and IT:

− Monitoring to visualize healthiness of integration aspects

− Alerting to inform responsible persons in business and IT

− Search and track to identify business-driven problems

− Analytics to analyze identified critical issues

− Operation automation to trigger corrective activities

Cloud

On-Premise

SAP Integration Suite Cloud Integration

SAP S/4HANA

SAP S/4HANA

Cloud

Integration and Exception

Monitoring


Integration and exception monitoring


Browser or

Mobile Device

Cloud Service Cloud Service

Real User and Performance

Monitoring


Real user and performance monitoring

On-Premise

System

▪ Provides transparency regarding performance as experienced by end

users as well as the utilization of business functionality

▪ Measurement at frontend and server side to identify actual root cause

of performance problems (frontend, network, cloud services and/or

systems)

▪ Utilization of SAP Passport technology allows to correlate performance

data measured at frontend, cloud service and/or system side



Job and automation monitoring

Cloud Service B

Job B

1. Execution of Job B

2. Execution of Job B

Job F

1. Execution of Job F

2. Execution of Job F

Job D

1. Execution of Job D



Cloud Service A

Job A

1. Execution of Job A

2. Execution of Job A

Job C

1. Execution of Job C

2. Execution of Job C

Job E

1. Execution of Job E



Job and

Automation

Monitoring

▪ Ensures efficient job and automated task

execution to increase operational quality:

− by monitoring job/task executions health

and detection of anomalies

− by directly alerting both business and IT

users on disruptions and exceptions

− by providing details at job/task execution

level to enable root cause analysis

− by reducing configuration effort through

use of historical execution information

▪ Job and automation monitoring is planned to

be enhanced with operation flows to trigger

corrective actions e.g. job restarts and job and

automation analytics to enable trend analysis

based on historical data



Health monitoring

Health Monitoring

Subscribed Cloud

ServicesCustomer On-

Premise Systems

Monitoring Analytics Alerting

Health status, metrics

▪ Visualizes the healthiness of cloud services

and systems to identify service disruptions or

degradations

▪ Health monitoring is planned to be enhanced with

embedded alerting, including predefined

operation flows to trigger corrective actions e.g.

service restarts

▪ Allows to execute application health checks for

SAP cloud services to check status of

persistency, jobs, connectivity, …

▪ Supports health checks for customer-built cloud

services and on-prem systems including trends

and usage metrics

▪ Provides embedded analytics to identify the root

cause of the discovered problem



Business service and event management covered by SAP Cloud ALM

Other

monitoring

use cases

Health

Monitoring

Operation

Automation

Cloud Availability Center

provides planned and unplanned

downtimes as well as other events

from SAP perspective

Business

Downtime

Management

External

Automation

Management

Embedded

Channels

Business Service Management

eMail

Chat*

Instant

Messages*

Tickets*

Business Service A

Business Service B

Business Service C

Business Event

Calendar*

Business SLA

Management*

Business Event

Scheduling*

Embedded

Operation

Automation*

Landscape Management

Event & Alert

Management

Cloud Landscape Directory

Generic

Channels*

* Planned functionality

Intelligent

Event

Processing



Intelligent event processing

Intelligent Event

Processing

Embedded

Monitoring &

Alerting

Embedded

Alerting

to enable unified

alert handling

Other internal

applications e.g.

business service

management

External

Monitoring &

Alerting

Embedded

Automation

External

Automation

Other external

applications e.g.

incident

management

Embedded

Channels

to support eMail,

instant messages,

tickets, chat

Operation

Automation

to support embedded

and external

automation

Generic

Channels

to provide APIs to be

utilized by 3rd party

vendors or

customers

▪ Unification of incoming events

sent by SAP Cloud ALM applications

or external senders (inbound

unification)

▪ Efficient event processing based

on central configuration and

forwarding to one or multiple

receivers (outbound unification)

▪ Handling of events independently

from alert management e.g. usage

of same event handling for

monitoring use cases and business

service management

▪ Provides foundation of intelligent

correlation of events e.g.

correlation of manually generated

with automatically generated alert



Business service management

Business Service Management

Business Service A Business Service B Business Service C

Business

Downtime

Management

Business

Event CalendarBusiness SLA

Management

Business

Event

Scheduling

▪ Business service management is planned to be enhanced:

– Definition of service times based on service level agreements (SLA) on business service level

– Measurement of actual availability at technical service level and consolidation to business service level

– Calculation of compliance to defined SLAs

– Embedded analytics to enable SLA reporting

▪ Business service as collection of

technical services (cloud service tenants

or system clients) to represent business

functionality

▪ Processing of maintenance, disruptions,

degradation, and communication events

as exposed by Cloud Availability Center

▪ Propagation of received events from

technical service to business service

level

▪ Definition of customer-specific

operational events at business service

level



SAP Cloud ALM for operations – onboarding and usage

Step 3: Configure and

use the applications

Step 2: Set up technical

prerequisites and connectivity

All information related to demo

environments and onboarding can

be found at the SAP Cloud ALM

Home Page and SAP Help Portal

All information related to the technical

setup can be found at the SAP Cloud

ALM for Operation Expert Portal

All information related to application

configuration and usage can be found in

built-in SAP Web Assistant, SAP Cloud

ALM for Operation Expert Portal and

SAP Help Portal

Step 1: Try it out and

onboard yourself

https://support.sap.com/en/alm/sap-cloud-alm.html

https://help.sap.com/viewer/08879d094f3b4de3ac67832f4a56a6de/LATEST/en-US/80b2c30a8d194ae8aff496bcff057cf0.html

https://support.sap.com/en/alm/sap-cloud-alm/operations/expert-portal.html


https://help.sap.com/viewer/product/CloudALM/2021-04-07/en-US?task=discover_task



Summary

In this unit you learned:

▪ How SAP Cloud ALM fits in the portfolio of our operations

platforms

▪ How SAP Cloud ALM supports your IT operations

▪ Which applications are available in SAP Cloud ALM for

operations

▪ How SAP Cloud ALM will be delivered to customers

In the next unit you will learn:

▪ How you can access the SAP Cloud ALM demo system

▪ How you can find helpful information on using SAP Cloud ALM

Thank you.

Contact information:

[email protected]

© 2021 SAP SE or an SAP affiliate company. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of

SAP SE or an SAP affiliate company.

The information contained herein may be changed without prior notice. Some software products marketed by SAP SE and its

distributors contain proprietary software components of other software vendors. National product specifications may vary.

These materials are provided by SAP SE or an SAP affiliate company for informational purposes only, without representation or

warranty of any kind, and SAP or its affiliated companies shall not be liable for errors or omissions with respect to the materials.

The only warranties for SAP or SAP affiliate company products and services are those that are set forth in the express warranty

statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional

warranty.

In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or

any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation,

and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platforms, directions, and

functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason

without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or

functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ

materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, and they

should not be relied upon in making purchasing decisions.

SAP and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered

trademarks of SAP SE (or an SAP affiliate company) in Germany and other countries. All other product and service names

mentioned are the trademarks of their respective companies.

See www.sap.com/trademark for additional trademark information and notices.

www.sap.com/contactsap

Follow all of SAP

http://www.sap.com/trademark

https://www.sap.com/registration/contact.html

https://plus.google.com/+SAP

https://www.linkedin.com/company/sap

https://www.youtube.com/user/SAP

https://twitter.com/sap

https://www.facebook.com/SAP


Unit 2: Access to the SAP Cloud ALM Demo System


Access to the SAP Cloud ALM demo system

SAP Cloud ALM resources

▪ SAP customers can find the following publicly available

resources for SAP Cloud ALM:

− The ALM Media Center

− A Public Demo Environment

▪ To access them, go to

https://support.sap.com/en/alm/demo-systems.html

https://support.sap.com/en/alm/demo-systems.html



ALM Media Center

In the ALM Media Center you can

find offline demos or recordings on

the various SAP Cloud ALM

capabilities

Demos can be played in different

modes:

▪ Demos

▪ Presentations

▪ Play Video

▪ Try it Yourself

▪ Hands-On Guide

▪ Documentation



SAP Cloud ALM – public demo tenant

A public demo tenant is available for all SAP

customers at no cost

▪ The tenant runs on SAP Business Technology

Platform and is refreshed on a regular basis

▪ Demo users are provided for different end-user

roles on the SAP Cloud ALM demo system

support portal page

▪ Demo data is available in the tenant to allow

customers to try out the different applications



SAP Cloud ALM Web assistant

The Web assistant is an interactive help inside

of SAP Cloud ALM UIs

▪ Select the UI element you are interested in to get

more information on its purpose and usage

▪ Select a topic from the Help Topics list to find the

corresponding button in the UI



Demo



Summary


▪ How the SAP Cloud ALM Media Center and public

demo system help customers learn more about SAP

Cloud ALM and try it out for themselves

▪ How to use the Web assistant in SAP Cloud ALM


▪ How the system landscape is managed in SAP Cloud

ALM

Thank you.


[email protected]










warranty.














Follow all of SAP









Unit 3: Landscape Management


Landscape management

Introduction

To use SAP Cloud ALM for operations capabilities,

you must first make the managed cloud services

and on-premise systems available in the

landscape management application in SAP Cloud

ALM.

You can find the following areas in the landscape

management application

▪ Cloud Services: Public cloud services

▪ On-Premise Systems: The technical systems that are

installed locally in the customers’ IT infrastructure

▪ Business Services: A business service groups the

cloud services and business services that technically

work together for one business purpose or use case



Importing cloud services and registering on-premise systems

Landscape

management

Cloud landscape

directory

On-premise /

hosted systems

Import subscribed

cloud services

Register customer

systems



Import cloud services

* Customers with several customer numbers please see next slide

Cloud service information can be imported or created

as follows:

▪ Import from the System Landscape Information service

(SLIS), a service in the SAP support backbone (preferred

option)

▪ Automatic creation by means of service registration

(available for push-enabled cloud services)

▪ Manual creation (only if required)

Setup steps for SLIS import:

1. On the Cloud Services page, click ‘Status of My

Subscribed SAP Services’

2. Use the “Activate Daily Import” button to activate daily

updates

3. If you don’t want to wait for the daily job, you can also

trigger the immediate import via ‘Import My Subscribed

SAP Services’

For more information, visit: https://help.sap.com/viewer/08879d094f3b4de3ac67832f4a56a6de/LATEST/en-US/d5f36cc72b4443f6abfa95f6e1a17782.html

https://help.sap.com/viewer/08879d094f3b4de3ac67832f4a56a6de/LATEST/en-US/d5f36cc72b4443f6abfa95f6e1a17782.html



Import cloud services for several customer numbers

Customers with more than one customer number can use

one SAP Cloud ALM tenant to manage all the cloud

services for all their customer numbers:

▪ You need an S-User with overall CCoE authorizations, that

has the required authorizations to access the data of all other

S-Users

Setup steps for service import for all customer numbers:

1. Access the Cloud Services configuration

2. Add the S-User in the ‘S-User’ tray

3. On the Cloud Services page, click ‘Status of My Subscribed

SAP Services’

4. Use the “Activate Daily Import” button to activate daily

updates

5. If you don’t want to wait for the daily job, you can also trigger

the immediate import via ‘Import My Subscribed SAP

Services’

For more information, visit: https://help.sap.com/viewer/08879d094f3b4de3ac67832f4a56a6de/LATEST/en-US/d5f36cc72b4443f6abfa95f6e1a17782.html




Registering on-premise systems

On-premise systems can be registered or added manually

as follows:

▪ System registration via ABAP transaction

(available for push-enabled on-premise systems)

▪ Manual creation (only if required)

Setup steps for system registration:

1. Check prerequisites

1. Verify that the parameter icm/HTTPS/client_sni_enabled is set to

TRUE

2. Verify SAP_BASIS 7.40 SP20 or higher and ST-PI 7.40 SP14 or

higher

2. Call transaction /n/SDF/ALM_SETUP

3. Enter a name for the destination and press Enter

4. Enter the SAP Cloud ALM Service Key information under

“Update destination”

5. Press “Register”

6. Select the monitoring use-cases for which to send data

For more information, visit: https://help.sap.com/viewer/08879d094f3b4de3ac67832f4a56a6de/LATEST/en-US/d9d672a2e8944067af5a914cf1e22d82.html

https://help.sap.com/viewer/08879d094f3b4de3ac67832f4a56a6de/LATEST/en-US/d9d672a2e8944067af5a914cf1e22d82.html



Manual service/system creation

If the service or system cannot be imported or

registered automatically you can create it manually

Manual creation:

1. Click the “Add” button under Cloud Services or On-

Premise Systems

2. Enter the required information and save the system

For cloud services, visit:

https://help.sap.com/viewer/08879d094f3b4de3ac67832f4a56a6de/LATEST/en

-US/d5f36cc72b4443f6abfa95f6e1a17782.html

For on-premise systems, visit:

https://help.sap.com/viewer/08879d094f3b4de3ac67832f4a56a6de/LATEST/en

-US/d9d672a2e8944067af5a914cf1e22d82.html


https://help.sap.com/viewer/08879d094f3b4de3ac67832f4a56a6de/LATEST/en-US/d9d672a2e8944067af5a914cf1e22d82.html



Demo



Summary


▪ How you can propagate managed cloud services and

on-premise systems to the SAP Cloud ALM

landscape management application


▪ How monitoring data is collected by SAP Cloud ALM

▪ What steps have to be taken to enable the data

collection in a managed cloud service or on-premise

system

Thank you.


[email protected]










warranty.














Follow all of SAP









Unit 4: Data Collection Strategies


Data collection strategies

Introduction

SAP Cloud ALM for operations uses two

mechanisms for data collection

▪ PUSH: The managed service or system actively

pushes the monitoring data

▪ PULL: The data collection is triggered from

SAP Cloud ALM

▪ PUSH and PULL can be used by the same managed

service or system type for different use cases

▪ Whether PUSH or PULL is used depends on the

managed service or system



PULL vs PUSH data collection

PULL Data Collection PUSH Data Collection

Prerequisites ▪ Managed service or system must already exist in SAP Cloud

ALM landscape management (LMS), either via successful

import from System Landscape Information service (SLIS) or

manual creation

▪ Successful import of subscribed SAP cloud services from the

System Landscape Information service (SLIS)

Registration ▪ Registration via endpoint creation for the SAP cloud service

in the landscape management service (LMS)

▪ Registration via the Registry service in the managed system

Monitoring

Configuration

▪ Centralized monitoring configuration in SAP Cloud ALM

▪ Active configuration is only stored in SAP Cloud ALM

▪ Centralized monitoring configuration in SAP Cloud ALM

▪ Automatic initial configuration during service or system

registration

▪ Configuration is maintained in SAP Cloud ALM and active

version distributed to the managed service or system

Data Collection ▪ Data collection is controlled by SAP Cloud ALM based on the

current monitoring configuration

▪ Collection takes place even if no new data is available in the

managed service or system

▪ Data collection is controlled by the managed service or

system and happens either periodically or event-based

▪ Only if data is available does it get transferred to SAP Cloud

ALM (no unnecessary connections)

Self-Monitoring ▪ Self-monitoring inherent in SAP Cloud ALM during data

collection

▪ Self-monitoring via the heartbeat service in the managed

service or system

Deactivation ▪ Monitoring can be switched off centrally in SAP Cloud ALM ▪ Monitoring can be switched off centrally in SAP Cloud ALM,

heartbeat service will continue to work

▪ For complete deactivation, deregistration must take place in

the managed service or system



PULL data collection

Managed Service

or System

Use-Case

Runtime

Service

SAP Cloud ALM

Registration &

Connectivity UILMS

SLIS

Use-Case

Configuration Use-Case

Runtime

Client

Monitoring

Data

Use-Case

Configuration UI

Use-Case Configuration

Service

HTTP

R

Use-Case-Specific

Data Providers

Transactional

Data

Current

Configuration

12

3

4

▪ Step 1 – Cloud Service Registration

▪ Managed cloud service is imported from

SLIS to the landscape management

service in SAP Cloud ALM

▪ Step 2 – Cloud Service Connectivity

▪ Endpoint is created between SAP Cloud

ALM and the managed service or system

▪ Step 3 – Monitoring Configuration

▪ Monitoring use-case is configured in

SAP Cloud ALM to activate data collection

▪ Step 4 – Monitoring Runtime

▪ Monitoring data is transferred to SAP

Cloud ALM by the respective monitoring

runtime service corresponding to the

monitoring configuration



Step 1 – cloud service registration

▪ SAP cloud services subscribed by the customer

are automatically imported into the landscape

management service (LMS) after the customer is

onboarded to SAP Cloud ALM

▪ SAP cloud services known to the SAP Cloud ALM

tenant can be found in the landscape




Step 2 – cloud service connectivity

▪ To establish connectivity to the cloud

service, an HTTP endpoint has to be

created

▪ The endpoint is created in the landscape


▪ Before creating the endpoint, make sure to

perform the necessary preparations in the

managed service. Find further information

in the SAP Cloud ALM Expert Portal

▪ To create an endpoint, the following

information is required:

− Root URL (usually from SLIS)

− Authentication information

• Depending on the service, you can choose

between BASIC and OAuth authentication




Step 3 – monitoring configuration

▪ The monitoring configuration is performed

within the respective monitoring application

▪ Click the icon to access the configuration

panel

− The specific setup steps depend on the

application to be set up



Data collection strategies: PUSH data collection – initial setup

Managed Service or System

Use-Case

Runtime Client

SAP Cloud ALM

LMS Registration

ServiceLMS

SLIS

Use-Case

Configuration

Use-Case

Runtime

Service

Monitoring

Data

Use-Case Configuration Service

HTTP

R

Heartbeat

and Event

Notification

Service

Heartbeat and

Event Notification

Client

Use-Case

Configuration

Client

LMS Registration

Client

Connectivity Configuration

Trigger Registration (M)Registration UI

Transfer Use-Case

Monitoring Data (A)

Transactional

Data

Use-Case

Configuration

Current

ConfigurationCurrent

Configuration

12

3

4HTTP

R

HTTP

R

▪ Step 1 – Cloud Service Registration:

− Managed service or system is imported

from SLIS to the landscape management

service in SAP Cloud ALM

▪ Step 2 – Cloud Service Connectivity:

− Technical connectivity between managed

service or system and SAP Cloud ALM is

established

− If not already existing in LMS, service or

system is created. Existing services or

systems are updated

▪ Step 3 – Initial Monitoring

Configuration

− Initial configuration contains suitable

filters and is auto-discovered during the

registration


− Based on the initial configuration-specific

runtime, data will be transferred to

SAP Cloud ALM

− The monitoring PUSH is scheduled

periodically or event-based



Step 2 – cloud service connectivity

SAP SuccessFactors

SAP Business Suite

▪ The registration for the PUSH connectivity is

performed in the managed service or system

▪ The specific steps depend on the connected

managed service or system. Find more

information in the SAP Cloud ALM Expert Portal

▪ After registration, the service or system will be

updated in LMS or created, if it didn’t already

exist

▪ The following information is required for

registration:

− User with authorizations for the PUSH

monitoring setup

− The SAP Cloud ALM service key with the

OAuth authentication information




Data collection strategies: PUSH data collection – monitoring configuration

Managed Service

R

SAP Cloud ALM

LMS Registration

ServiceLMS

Use-Case

Configuration

Use-Case

Runtime

Service

Monitoring

Data

Use-Case

Configuration UI

Use-Case Configuration Service

Heartbeat

and Event

Notification

Service

Use-Case

Configuration

Client

LMS Registration

Client

Connectivity Configuration

Trigger Registration (M)Registration UI

Retrieve and Store

Current Configuration (A)

Transfer Use-Case

Monitoring Data (A)

Transactional

Data

Use-Case

Configuration

Current

ConfigurationCurrent

Configuration

HTTP

R

HTTP

7

6

5

8Use-Case

Runtime Client

Heartbeat and

Event Notification

Client

HTTP

R

▪ Step 5 – Monitoring Adjustments:

− Based on the auto-discovered

configuration attributes, users can

reconfigure monitoring


Notification:

− New configuration will be transported

via the configuration notification


Trigger

− The configuration notification is the

trigger for the monitoring configuration

service to pick up the latest version of

the monitoring configuration


− Based on the adapted configuration-

specific runtime, data will be transferred

to SAP Cloud ALM



Summary


▪ How SAP Cloud ALM for operations retrieves data

from the managed services and systems

In the next week you will learn:

▪ How to set up and use the applications for SAP

Cloud ALM for operations

Thank you.


[email protected]










warranty.














Follow all of SAP








week 1: introduction unit 1: sap cloud alm for operations

Documents