SAP Cloud Platform Integration for data services (SAP CPI for DS) allows you to efficiently and securely use ETL (extract, transform, load) tasks to move data between on-premise systems and the cloud. With SAP CPI for DS you can replicate the data and define how the data is mapped to your database schema.
SAP public cloud applications such as SAP Integrated Business Planning use SAP CPI for DS to integrate with the on-premise SAP system. We can monitor SAP CPI for DS using a SOAP API to extract exceptions.
Public cloud service offerings are usually Software-as-a-Service (SaaS) solutions. This means that customers only have access to the service but not to the underlying infrastructure. Hence, the usual way to connect on-premise managed systems to Focused Run does not apply to cloud services.
However, to be able to monitor exceptions and performance in cloud services they need to be connected to Focused Run. This connection is created using the customer and cloud service specific root URL and an end-point definition, which allows Focused Run to receive information from the cloud service.
The first step is to import the SSL certificate into Focused Run. This is valid for all cloud services.
Import Cloud SSL certificate into STRUST
Export Certificate from Browser:
Import Certificate into Focused Run:
For a successful SSL handshake, please make sure the following parameter are set in the SAP Focused Run system:
Additionally you have to perform certain preparations in the cloud service to enable Focused Run to connect to the cloud service.
Preparations for SAP Cloud Platform Integration for Data Services
Create a user for the connection to SAP CPI-DS.
The user will be maintained in the HTTP endpoint and must be must have the role Production Operator to be able to monitor running and finished tasks and processes.
For more information about default role assignments, please refer to SAP Cloud Platform Integration for data services security guide https://help.sap.com/viewer/f9f202d1c5924753833b487ac9306384/latest/en-US/d627c9c23a1c4311bd0f88a611ac2aa6.html
After gathering all necessary information and creating the necessary connection point or users in the cloud service, you can now create the cloud service in Focused Run.
Input Values for SAP Cloud Platform Integration for Data Services
The second step is to create the end-point for the cloud service. The end-point is used to actually connect to the cloud service with user and password. Most cloud services use HTTP end-points.
Input Values for SAP Cloud Platform Integration for Data Services
To be able to monitor interfaces of a cloud service you first have to add it to Interface & Cloud Monitoring and select the monitoring categories you want to monitor for the system.
In the next step, you see all monitoring categories which are available for the system, depending on the system type and the installed software components. Some recommended standard monitoring categories are preselected.
Select the monitoring categories in scope.
Available Monitoring Categories
For SAP Cloud Platform Integration for data services, the following category is available.
After selecting your monitoring categories you have to maintain filters to define what exactly you want to monitor. Some monitoring categories come with standard filters that usually just select all items of this monitoring category. SAP Focused Run can handle this high amount of monitoring data, so you can stick to this standard filters. Or you can set up filters of your own.
Please note that the filters you set in the 'Monitoring' step filter the data which is collected from the managed system or cloud service. You can also set up filters later in the 'Alerting' step, which will filter the data already in Focused Run.
You can create more than one filter for a monitoring category.
Available Filter Options
SAP Cloud Platform Integration for data services
You can collect all errors or you can use a filter to restrict the data collection:
The setup of the filters for the monitoring categories only makes sure that the data is collected, however, alerts are not created automatically. To create alerts and notifications you have to create an alert individually.
In the next sub-step, you have to maintain the filter. For most monitoring categories the available filter fields will be the same as for the 'Monitoring' configuration described above.
For some metrics, you have additional filter fields or you have to maintain metric parameters. You can check the collected data in Focused Run to determine which filter values to use for alerting. Most of the fields can be found in the Collection Context of the collected data.
Please note that the filters on 'Alerting' level filter the data that is already available in Focused Run. They do not influence the data collection itself. You can only filter for data that is collected. Be aware of this if you created strict filters in the 'Monitoring' step.
In the last sub-step you have to activate the alert:
For single exceptions, the threshold type is always 'Already Rated'. This means depending on the calculation frequency the number of exceptions is checked and an alert is created if this number is bigger than 0. If you want to reduce the number of alert for these metrics, you could increase the value for the calculation frequency to increase the time between checks.
Available Metrics
For SAP Cloud Platform Integration for data services the following metrics are collected:
SAP Cloud Platform Integration for data services