Technology Blog Posts by Members
Explore a vibrant mix of technical expertise, industry insights, and tech buzz in member blogs covering SAP products, technology, and events. Get in the mix!
cancel
Showing results for 
Search instead for 
Did you mean: 
Venuobbireddy816
Explorer
5,972

As you may all be aware, SAP Solution Manager is scheduled to be deprecated around 2027 and will be replaced by SAP Cloud ALM. In this blog, our objective is to provide a comprehensive, end-to-end guide on configuring SAP Cloud ALM. The following steps outlined in this blog are specifically focused on integrating SAP S/4HANA as a connected system (backend on-premise) with Cloud ALM.

Technical Prerequisites

  1. SAP_BASIS Release

Required: Either 7.40 SP16 or higher (accordingly 7.50 SP05)

  1. SAP_UI Version:

Required: Either SAP_UI 740 SP15 or higher

  1. ST-PI 7.40 

Required: ST-PI 7.40 Support Packages and keep them up-to-date,ST-PI 7.40 SP26 

  1. Check that profile parameter

 icm/HTTPS/client_sni_enabled is set to TRUE

SAP Note 510007 - Additional considerations for setting up SSL on Application Server ABAP

Check that profile parameter

ssl/client_ciphersuites  =  150:PFS:HIGH::EC_X25519:EC_P256:EC_HIGH

 

  1. Below certificates Imported in STRUST under SSL Client (Anonymous) and SSL Client (Standard).

DigiCert Global Root CA

DigiCert Global Root G2

DigiCert RSA4096 Root G5

Network Prerequisites:

  • You need to obtain the SAP Cloud ALM Service Key to connect to the SAP Cloud ALM system
  • You need to make sure that the following URLs can be reached:
    • The Cloud ALM API URL (service key "endpoints":"Api" without /api)
    • The Cloud ALM OAuth URL (service key "uaa":"url" extended by /oauth/token)
  • In case you use a proxy in your network, please make sure that it is configured to allow calls to these URLs

 

  • If your SAP ABAP system is hosted with SAP Enterprise Cloud Services (ECS), please open a service request with SAP ECS to add the following URLs to the "Allow-List" for your environment
  • Root URL: SAP Cloud ALM service key parameter "endpoints":"Api" without /api
  • OAuth URL: SAP Cloud ALM service key parameter "uaa":"url"

Required authorization:

  • The user performing the setup: To run transaction /SDF/ALM_SETUP your personal user needs the PFCG role SAP_SDF_ALM_SETUP. 

Please note: In this role you need to maintain the authorization field S_BTCH_NAM > BTCUNAME either with '*' or with the user name of the user you plan to use as data collection background job user

 

ST-PI 7.40 SP25 and higher

In addition to the authorizations for ST-PI 7.40 SP24, you need:
SAP_SDF_ALM_METRIC_PUSH_CSA
This role contains authorization objects delivered by SAP with no authorization. To use the SAP Cloud ALM scenario Configuration & Security Analysis (CSA), please maintain make sure the following authorization objects are maintained:
S_RFC_ADM: ICF_VALUE = '*'
S_DATASET: FILENAME = '*', PROGRAM = '*'
S_LOG_COM: HOST = '*', OPSYSTEM = '*'
SAP_SDF_ALM_METRIC_PUSH_CSA_S
This role allows the detection of special users (such as SAP*) using default passwords
Before ST-PI 7.40 SP25 you can either use the existing SAP Focused Run roles for Configuration & Security Analysis or the ones delivered by the SAP Note 3372078 (recommended).

Procedure:

Log on to the relevant client

Transport Management: The setup must always be performed in client 000

All other use-cases: The setup must be performed in the client, for which you want to collect monitoring data (e.g. the production client). You can perform the setup in more than one client.

  1. Transaction /n/SDF/ALM_SETUP
  2. Enter "Target ALM Description"

1.jpg

  1. Maintain HTTP Destination
  • Click "Update destination"

2.jpg

  1. You can copy & paste the content from the JSON file created during the enablement of the SAP Cloud ALM APIs by clicking "Paste Service Keys

3.jpg

How to get Cloud ALM service key

Logon SAP Cloud ALM > Landscape Management > click on Configuration >Open SAP Cloud ALM Service Key.

4.jpg

 

5.jpg

6.jpg

7.jpg

Created the HTTP destination

8.jpg

9.jpg

  1. Enter background user and register system 

Enter the background user you created to perform the data collection

  • Make sure that it has the authorizations as described on tab "Required Authorizations" under "Prerequisites"

10.jpg

  • Click on "Register" to call SAP Cloud ALM and register the system. If it is successful, a LMS ID is retrieved and is displayed.

Scheduled the SAP CLOUDALM JOB

11.jpg

12.jpg

a LMS ID is retrieved and is displayed

13.jpg

  1. Select the use cases you want to collect and push data for

14.jpg

15.jpg

16.jpg

  1. Registration in SAP Support Backbone connection

17.jpg

Enter the Technical S- user ID .

18.jpg

If backbone is setup already exist show the already setup screen.

19.jpg

 After the successful setup the SAP S/4HANA or SAP Business Suite system will show up as "Registered" service in the Landscape Management application of your SAP Cloud ALM tenant.

Go to administration > click Landscape Management

20.jpg

System will displayed .

21.jpg

22.jpg

Configure the Health monitoring.

Open Operations > Health Monitoring

Click on SID

23.jpg

Here showing the system details

24.jpg 

 

Alert & Notification configuration

Cleck on configuration

25.jpg

 

26.jpg

Please turn on the create alert.

27.jpg

 

Before Notification configuration Add the mail ids in Notification Management

28.jpg

 

29.jpg

Once the email id is added in notification management you will get email to verify.

Please click on here.

30.jpg

 

Once click here subscribed to SAP Cloud ALM

31.jpg

 

Once done the notification Management

Go to Health monitoring

32.jpg

Add the mail ids

33.jpg

Click on save

34.jpg

 

Active the notification

35.jpg

 

With this the SAP Cloud ALM setup is completed.

 

 

 

2 Comments
HemantVaswani
Participant
0 Kudos

Hi @Venuobbireddy816 

very well articulated post. thanks.

on following the above steps, when i reach on step of click "Register" , i am getting following error

"Connect to proxy:3128 failed: NIEHOST_UNKNOWN(-2)"

even if i remove the values of proxy host "proxy" and proxy port "3128" as mentioned in the SAP portal (inside maintain destination), i get following error :

SSL handshake with spotless-services-ltd-cloudalm.authentication.ap10.hana.ondemand.com:443 failed: SSSLERR_PEER_CERT_UNTRUSTED (-102)#Peer's X.509 certificate (chain) validation failed (missin...

this is for my on-prem NW 7.5 based SAP BW system. BASIS patch 30  and all patch pre-requisites met.

kindly suggest for the way forward

 

Thanks

Hemant

Venuobbireddy816
Explorer
0 Kudos

Hi Hemant,

Please check the CALM RFC connection, is it working or not?

Thanks

Venu Gopala Reddy O

Labels in this area