Setup for SAP S/4HANA private cloud edition

This page explains how to connect SAP S/4HANA private cloud edition to SAP Cloud ALM.

Currently the following monitoring application are supported for SAP ABAP systems:

Setup Video

The following video demonstrates the setup steps to set up Integration & Exception Monitoring for SAP S/4HANA private cloud edition.

A textual step by step description for all setup steps is provided in the sections below the videos.

 

Set Up Monitoring for SAP S/4HANA private cloud edition

  • Prerequisites for this video:
    • Download SAP Cloud ALM service key
    • Ensure prerequisites for the ABAP system are met as described in the section "Prerequisites"

Prerequisites

Technical Prerequisites

  • Technical Prerequisites for the ABAP system
    • SAP_BASIS 7.40 SP20 or higher (accordingly 7.50 SP04)
    • Install ST-PI 7.40 SP15 or higher
    • To enable Health Monitoring you need at least ST-PI 7.40 SP16
    • Implement the latest version of the collective correction note:
    • Check that profile parameter icm/HTTPS/client_sni_enabled is set to TRUE (see also note 510007 - Additional considerations for setting up SSL on Application Server ABAP)
    • Check that DigiCert Global Root CA is imported in STRUST under SSL Client (Anonymous) and SSL Client (Standard)

Required Authorizations

You need to consider two users in the managed ABAP system for the setup. 

  • 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
  • User to run the data collection background job: Please assign the roles as per the table below.

ST-PI ReleaseRequired Authorizations
ST-PI 7.40 SP15
  • SAP_SDF_ALM_METRIC_PUSH_FND*
  • SAP_SDF_ALM_METRIC_PUSH_BPMON*
  • SAP_SDF_ALM_METRIC_PUSH_EXMON*

* Please download the latest version of the roles from SAP note 3054258

ST-PI 7.40 SP16
  • SAP_SDF_ALM_METRIC_PUSH_FND*
Assign the following authorizations depending on the use-cases you plan to activate:
  • SAP_SDF_ALM_METRIC_PUSH_BPMON
  • SAP_SDF_ALM_METRIC_PUSH_EXMON*
  • SAP_SDF_ALM_METRIC_PUSH_HEALTH*
  • SAP_SDF_ALM_METRIC_PUSH_INTMON
  • SAP_SDF_ALM_METRIC_PUSH_JOBMON
  • SAP_SDF_ALM_METRIC_PUSH_PERF
  • SAP_BC_TRANSPORT_ADMINISTRATOR (only in client 000)

* Please download the latest version of the roles from SAP note 3104662

Required Information

Configure the PUSH Data Provider

Monitoring for SAP S/4HANA and SAP Business Suite uses a PUSH mechanism to push monitoring data to SAP Cloud ALM. 

  1. 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.
  2. Call transaction /n/SDF/ALM_SETUP
  3. Enter "Target ALM Destination"
    • To create a new ALM Destination, enter a name (e.g. CALM) and press the "Enter" key
    • To change an existing ALM destination, select one from the F4 input help and press the "Enter" key
    • After pressing the "Enter" key the subsequent fields will be filled.
  4. Maintain HTTP Destination
    • Click "Update destination"
    • 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"
    • Or you can enter the required fields for connecting Cloud ALM manually:
      1. Token Endpoint: SAP Cloud ALM service key parameter "url" + /oauth/token
      2. Client ID: SAP Cloud ALM service key parameter "clientid"
      3. Client Secret: SAP Cloud ALM service key parameter "clientsecret"
      4. Proxy Host: for system hosted by SAP enter value: proxy
      5. Proxy Port: for system hosted by SAP enter value: 3128
    • Click "Ok" to close the pop-up.
    • To delete a destination click on "Delete destination"
  5. Enter registration target
    • Enter the SAP Cloud ALM service key parameter "Api" without /api, e.g. eu10.alm.cloud.sap
    • Enter the background user you created to perform the data collection
    • Click on "Register" to call Cloud ALM and register the system. If it is successful, a LMS ID is retrieved and is displayed.
    • To unregister a system, click the "Unregister" button. Caution: This stops all data collection and heartbeat measurements
  6. Select the use cases you want to collect and push data for
After the successful setup the SAP S/4HANA Private Cloud Edition tenant will show up as "Registered" service in the Landscape Management application of your SAP Cloud ALM tenant. 
The data collection for the selected use-cases will be activated automatically.