SAP S/4HANA private cloud edition

This page explains how to connect SAP S/4HANA private cloud edition to SAP Focused Run. For the setup of the supported monitoring applications, please click on the monitoring application below.

Currently, the following monitoring applications are supported for SAP S/4HANA private cloud edition:

Prerequisites

Prerequisites in SAP Focused Run

The following technical prerequisites have to be met in order to monitor this scenario:

  • To use Real User Monitoring you need SAP Focused Run 3.0 FP02
  • For Integration & Exception Monitoring and Job & Automation Monitoring, you need SAP Focused Run 3.0 FP03
  • SAP Cloud ALM subscription
  • To enable this monitoring please ensure that you configured the SAP Focused Run reverse proxy in SAP Cloud ALM
  • You need to obtain the SAP Cloud ALM Service Key
  • If your SAP S/4HANA private cloud edition 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 "Api" without /api
    • OAuth URL: SAP Cloud ALM service key parameter "uaa":"url"

Technical Prerequisites in SAP S/4HANA private cloud edition

  • Technical Prerequisites for the ABAP system
    • SAP_BASIS 7.40 SP20 or higher (accordingly 7.50 SP04)
    • Install the latest available support package for ST-PI 7.40 and the SAP notes mentioned below (the minimum required support package is ST-PI 7.40 SP16) 
    • 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 profile parameter ssl/client_ciphersuites is set as described in section 7 of 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)

  • 3196078 - Collective corrections as of ST-PI 7.40 SP18 for SAP Cloud ALM
  • 3133333 - Collective corrections as of ST-PI 7.40 SP17 for SAP Cloud ALM
  • 3104662 - Collective corrections as of ST-PI 7.40 SP16 for Cloud ALM
  • 3102288 - Job & Automation Monitoring: ST-PI fixes for on-premise jobs (ABAP jobs and BW process chains)

 

Requires Users & Authorizations in SAP S/4HANA private cloud edition

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 SP16 and higher
  • 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

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

Setup Steps in SAP S/4HANA private cloud edition

  1. Log on to the production client
  2. Call transaction /n/SDF/ALM_SETUP
  3. Enter "Target ALM Description"
    • 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 User (if required by your network infrastructure)
      5. Proxy Password (if required by your network infrastructure)
      6. Proxy Host (if required by your network infrastructure)
        • if your system is hosted by SAP please enter the value proxy
      7. Proxy Port (if required by your network infrastructure) 
        • if your system is hosted by SAP please enter the value 3128
    • Adjust the "Root URL" field to use the reverse proxy: 
      • Enter the SAP Cloud ALM service key parameter "Api" without /api, e.g. https://eu10.alm.cloud.sap
      • Add the suffix from the Reverse Proxy URL from the endpoint in SAP Cloud ALM, e.g. /api/frunrevproxy/v1/my_customer_network/
      • Add sap/frun/ (including the / in the end) to the suffix
      • The entire string should be e.g. https://eu10.alm.cloud.sap/api/frunrevproxy/v1/my_customer_network/sap/frun/
    • Click "Ok" to close the pop-up.
    • To delete a destination click on "Delete destination"
  5. 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"
    • Click on "Register" to call SAP Cloud ALM and register the system. If it is successful, a SAP Cloud ALM 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. Activate the following available use cases via the button "Activate usecases":
    • Exception Monitoring
    • Integration Monitoring
    • Job & Automation Monitoring
    • Performance Monitoring

Setup Steps in SAP Focused Run

After the successful setup, the SAP S/4HANA private cloud edition tenant will be created as a cloud service in the Cloud Service Management application of your SAP Focused Run system.
 
No further setup steps are necessary for SAP Focused Run. The data collection for the selected use-cases will be activated automatically.

Troubleshooting

To troubleshoot any issues with the setup or the data collection for SAP S/4HANA private cloud edition, please follow the documentation on page Troubleshooting for Managed ABAP Systems.