Setup Steps in SAP BTP ABAP Environment

Enable Monitoring Data PUSH to SAP Cloud ALM

To enable SAP BTP ABAP Environment to send monitoring data to SAP Cloud ALM.

Prerequisites:

  • You need an user with administrator authorizations
  • You need to obtain the SAP Cloud ALM Service Key to connect to the SAP Cloud ALM system
  • You need to create in BTP cockpit a destination to your SAP Cloud ALM tenant.
    • URL: e.g. https://eu10.alm.cloud.sap
    • Client ID: Service key parameter "clientid"
    • Client secret: Service key parameter "clientsecret"
    • Token Service URL: Service Key parameter "url" + /oauth/token, e.g. https://calm-tenant.authentication.eu10.hana.ondemand.com/oauth/token

Create Communication System

  1. Log on to SAP BTP ABAP Environment
  2. Navigate to the 'Communication Management' view and select 'Communication Systems'
  3. Create a new communication system
    1. Enter a System ID (e.g. CALM) and description and click the Create button
    2. Under Destination Service select Use Default Instance and choose from the value help of Name the destination you have created in the BTP cockpit.

 

Save the communication system.

Create Communication Arrangement

The Communications Arrangement is necessary to schedule the collectors.

  1. Navigate to the 'Communication Management' view on the launchpad
  2. Select 'Communication Arrangements'
  3. Check first if a Communication Arrangement exists already for your Cloud ALM.
    1. Enter 0527 in the Search field. If you find something check if it uses the same Communication System from step before and you can skip the next steps until step 6.
  4. Create a new Communication Arrangement
    1. Scenario: Enter SAP_COM_0527
    2. Arrangement Name: you can keep the default.
  5. Common Data: Select the communication system you have created before.
  6. Additional Properties
    1. Select the data you want to collect.
      Example: If you want to collect performance data set the value to for the property Collect Performance Data.
  7. Outbound Services
    1. Job Execution Details
      Ensure the job runs every minute:
      Run Every 1 Minute(s)
  8. Save
    It can take some time until the first data collection is started.