SAP Marketing Cloud
This page explains how to connect SAP Marketing Cloud to SAP Focused Run. For the setup of the supported monitoring applications, please click on the monitoring application below.
Currently the following monitoring application are supported for SAP Marketing Cloud:
Choose Your SAP Focused Run Release
This page describes the monitoring setup for SAP Marketing Cloud with SAP Focused Run 3.0 FP 02 or newer.
Please select the documentation appropriate for your SAP Focused Run release from the table below.
| SAP Focused Run Release | Monitoring Setup Documentation |
|---|---|
| SAP Focused Run 3.0 FP02 | Stay on this page |
| SAP Focused Run 3.0 FP01 and lower | SAP Marketing Cloud - up to SAP Focused Run 3.0 FP01 |
Prerequisites
The following technical prerequisites have to be met in order to monitor this scenario:
- SAP Focused Run 3.0 FP02
- SAP Cloud ALM subscription
- To enable this monitoring please ensure that you configured the SAP Focused Run reverse proxy
- You need to obtain the SAP Cloud ALM Service Key
PUSH vs. PULL Data Collection
With SAP Focused Run 3.0 FP02 we enabled PUSH data collection for monitoring data for Integration & Exception Monitoring and Real User Monitoring. Further use-cases will follow in the future.
With PUSH data collection the managed cloud service now actively pushes monitoring data to SAP Focused Run via SAP Cloud ALM which is used as a reverse proxy.
PUSH data collection has the following advantages over PULL data collection:
- PUSH data collection uses OAuth 2.0 to connect from the managed cloud service to SAP Cloud ALM (PULL uses BASIC authentication)
- Data is only transferred if new monitoring data exists (no unnecessary connections)
While it is still possible to use PULL data collection for SAP Marketing Cloud with SAP Focused Run 3.0 FP02, PULL data collection will be disabled in a future SAP Focused Run release, to avoid the use of BASIC authentication in connections. If you already monitor your cloud service using PULL data collection, we recommend that you switch to PUSH data collection.
Activation of PUSH data collection for cloud services already monitored using PULL data collection
If you already monitor SAP Marketing Cloud using the PULL data collection, please note the following:
- With the activation of PUSH data collection a new cloud service will be created in LMDB by the registration process
- It will not update or overwrite the existing cloud service created manually during the PULL data collection setup
- Historical monitoring data collected with the "old" PULL based mechanism will remain attached to the "old" cloud service for reporting
To deactivate the PULL data collection for the existing monitoring setup:
- Deactivate the monitoring data collection in Integration & Exception Monitoring and Real User Monitoring
- Delete the endpoints in the cloud service in LMDB
- Do not delete the cloud service from LMDB yet, to avoid losing historical monitoring data
Setup Steps in SAP Marketing Cloud
Enable Monitoring Data PUSH to SAP Focused Run via reverse proxy
Perform the following steps to enable SAP Marketing Cloud to send monitoring data to SAP Cloud ALM.
Prerequisites:
- You need an user with administrator authorizations in SAP Marketing Cloud
- You need to obtain the SAP Cloud ALM Service Key to connect to the SAP Cloud ALM system
- Endpoint: The host part of the service key parameter "Api", 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"
- Log on to SAP Marketing Cloud
- Navigate back to the 'Communication Management' view and select 'Communication Arrangements'
- Click the New button to create a new Communication Arrangement
- Scenario: Select SAP_COM_0527 'Application Monitoring Push Integration'
- Click the New button next to 'Communication System' to create a new communication system
- Enter a System ID and description and click the Create button
- Enter the Cloud ALM endpoint URL in the 'Host Name' field
- Make sure the 'Port' is set to 443
- Under 'OAuth 2.0 Settings' enter the Cloud ALM OAuth URL in the field 'Token Endpoint'
- Under 'Users for Outbound Communication' click the + button to create a new user
- Authentication Method: Choose OAuth 2.0
- OAuth 2.0 Client ID: Enter Cloud ALM client ID
- Client Secret: Enter Cloud ALM client secret
- Save the communication system. The UI will take you back to the communication arrangement
- Enter an 'X' in 'Collect Integration Monitoring' if the field is empty. Do not change any of the other fields.
- The 'Outbound Communication' fields are automatically propagated from the communication system
- The "Path" field under 'Outbound Services' is where you have to maintain the path to SAP Focused Run, enter:
- 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 total string should be: /api/frunrevproxy/v1/my_customer_network/sap/frun/
- Press the "Enter" key. This will trigger the propagation of the fields below when you save the communication arrangement
- Adjust the Job Execution Details to schedule the job to Run Every 01 Minute(s)
- Save
After the successful setup in your SAP Marketing Cloud tenant, the managed cloud service will automatically be created in the Cloud Service Management of SAP Focused Run.
Setup Steps in SAP Focused Run
No further steps are necessary to connect SAP Marketing Cloud to SAP Focused Run.
You can now perform the setup steps for the supported scenarios.