SAP NetWeaver Application Server for ABAP (7.40 or higher)

Configure the PUSH Data Provider

Monitoring for SAP NetWeaver Application Server for ABAP (7.40 or higher) uses a PUSH mechanism to push monitoring data to SAP Cloud ALM.

Use of Cloud Connector

Please note that it is not possible to use the Cloud Connector from SAP to establish the connection between your SAP ABAP on-premise system and SAP Cloud ALM.

The Cloud Connector acts as a reverse invoke proxy between the on-premise network and SAP BTP. This means after connecting the subaccount to the Cloud Connector the tunnel between SAP BTP and the on-premise landscape is triggered by the BTP destination service in the connected subaccount. The Cloud Connector is not designed to act in the opposite direction.

The connectivity from On-premise to Cloud is only possible for ABAP cloud systems, HANA Cloud databases, and specific SAP BTP services like K8s clusters. It cannot used for SAP BTP services like SAP Cloud ALM.

For more information see Cloud Connector FAQ > Features > "Can I use the Cloud Connector from on-premise to cloud for any protocol?"

It is possible to use other proxy solutions between your ABAP on-premise system and SAP Cloud ALM. If you do this please make sure to add the relevant URLs to the allow list for the proxy as described under Prerequisites > Network Prerequisites.

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.
Call transaction /n/SDF/ALM_SETUP
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.
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
  8. Root URL: Enter the SAP Cloud ALM service key parameter "Api" without /api, e.g. https://eu10.alm.cloud.sap
- Click "Ok" to close the pop-up.
- To delete a destination click on "Delete destination"
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 LMS ID is retrieved and is displayed.
- To unregister a system, click the "Unregister" button. Caution: This stops all data collection and heartbeat measurements
Select the use cases you want to collect and push data for

After the successful setup the SAP NetWeaver Application Server for ABAP (7.40 or higher) system 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. In general it is recommended to use the standard collection interval. Only for specific requirements, you are able to change the “Collection interval” for the different use cases. Please be aware that Business Process Monitoring is using a separate scheduler, therefore, this specific value cannot be changed.

System Refresh

After you connected your SAP ABAP system to SAP Cloud ALM, the ABAP system will keep sending data to the monitoring applications. To which ABAP system in LMS the monitoring data is assigned, will be determined by the LMS Id. If you perform a system refresh of your ABAP system, by overwriting it with a copy from another ABAP system, this assignment will be broken.

To avoid that the metrics will be assigned to the source of the copy rather than the actual ABAP system, you need to save and restore the tables containing monitoring setup information for SAP Cloud ALM.

SAP Cloud ALM configuration is integrated in post-copy automation (PCA) Introduction | SAP Help Portal.

Requirements are ST-PI 7.40 SP 27 (and correction note) and note 3501074 (System Copy: ST-PI CALM configuration)

If PCA is not used then two reports will support your system copy and system refresh:

/SDF/CALM_SYS_COPY

After a system has been copied to create a new system based on an already configured system the report /SDF/CALM_SYS_COPY can be used to delete the SAP Cloud ALM configuration. Connection to SAP Cloud ALM must be executed with /SDF/ALM_SETUP.

/SDF/CALM_SYS_REFRESH

As a preparation of a system refresh you can execute this report. It will create a Transport of Copies(ToC) with table content of SAP ALM configuration. You need to export this request and save it. After the system refresh you can import this transport request again.