This page explains how to connect SAP S/4HANA and SAP Business Suite on-premise systems and SAP S/4HANA and SAP Business Suite systems located in a private cloud infrastructure to SAP Cloud ALM.

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

• Business Process Monitoring
• Integration & Exception Monitoring
• Job & Automation Monitoring
• Real User Monitoring

The following video demonstrates the setup steps to set up Integration & Exception Monitoring for SAP S/4HANA and SAP Business Suite.

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

• Technical Prerequisites for the ABAP system
  • SAP_BASIS 7.40 SP20 or higher (accordingly 7.50 SP04)
    
  • Install ST-PI 7.40 SP14 or higher
    
  • Implement the latest version of the collective correction note:
    • SAP Note 2985521 -Collective corrections as of ST-PI 7.40 SP14 for Cloud ALM
    • SAP Note 3054258 -Collective corrections as of ST-PI 7.40 SP15 for Cloud ALM
  • 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
  • To run  transaction /SDF/ALM_SETUP you need the PFCG role SAP_SDF_ALM_SETUP
  • The user you specify as Background User, requires the PFCG role SAP_SDF_ALM_COLLECTORS_JOBS
  • If you want to use Business Process Monitoring also assign the SAP_SDF_ALM_METRIC_PUSH_BPMON, attached to SAP note 3054258
    
• You need to obtain the SAP Cloud ALM Service Key to connect to the SAP Cloud ALM system
  • Endpoints: e.g. eu10.alm.cloud.sap
  • OAuth URL: Service Key parameter "url" + /oauth/token, e.g. calm-tenant.authentication.eu10.hana.ondemand.com/oauth/token
  • Client ID: Service key parameter "clientid"
  • Client secret: Service key parameter "clientsecret"

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

Call transaction /n/SDF/ALM_SETUP and perform the following steps:

1. 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.
2. 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: Enter the CALM OAuth URL 
     2. Client ID: Enter Cloud ALM client ID
     3. Client Secret: Enter Cloud ALM client secret
     4. Proxy User (if required)
     5. Proxy Password (if required)
     6. Proxy Host (if required by your network infrastructure. For S/4HANA private cloud edition enter value: proxy)
     7. Proxy Port (if required by your network infrastructure. For S/4HANA private cloud edition enter value: 3128)
   • Click 'Ok' to close the pop-up.
   • To delete a destination click on 'Delete destination'
3. Enter registration target
   • Enter the target ALM root url depending on your region e.g. https://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
4. Select the use cases you want to collect and push data for