SAP NetWeaver Application Server for ABAP (7.40 or higher)

How you can contact us:

Technical Assistance

Request product support from SAP
Non-Technical Assistance

Request non-product support or provide feedback on SAP Support Portal site

SAP NetWeaver Application Server for ABAP (7.40 or higher)

This page explains how to connect SAP NetWeaver Application Server for ABAP (7.40 or higher) on-premise systems 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 and SAP Business Suite. However the same steps have to be performed for SAP ABAP Application Server (7.40 or higher).

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

Set Up Monitoring for SAP NetWeaver Application Server for ABAP (7.40 or higher)

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

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.

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.

Next Steps

After setting up the monitoring PUSH to SAP Cloud ALM in the managed service, the data collection for the use-cases selected in the communication scenarios will be activated automatically with default monitoring configurations.

You can adjust the monitoring setup within the monitoring application. Find more information on the configuration on the "Setup & Configuration" pages for the application.

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.

Troubleshooting

To troubleshoot any issues with the setup or the data collection for SAP ABAP Application Server (7.40 or higher), please follow the documentation on page Troubleshooting for Managed ABAP Systems.