SAP Cloud Integration for data services allows you to efficiently and securely use ETL (extract, transform, load) tasks to move data between on premise systems and the cloud. With SAP Cloud Integration for data services you can replicate the data and define how the data is mapped to your database schema.
SAP public cloud application like SAP Integrated Business Planning for Supply Chain use SAP Cloud Integration for data services to integrate with the on premise SAP system.
The following technical prerequisites have to be met in order to monitor this scenario:
SAP Cloud Integration for data services represents the integration layer of a hybrid scenario. Monitoring it is relevant for all hybrid scenarios using this integration form. For SAP Cloud Integration for data services we can collect exceptions in the tasks running in the service.
Which tasks are relevant depends on the integrated solution and the data that is integrated.
|Metric Name||Description||MAI Category||Since SP|
Number of erroneous tasks in SAP Cloud Integration DS (Delta)
Number of erroneous tasks detected in SAP Cloud Integration for data services since the last data collection. The exceptions are retrieved from SAP Cloud Integration for data services via the central Exception Management in SAP Solution Manager.
Number of erroneous tasks in SAP Cloud Integration DS (last 24h)
Number of erroneous tasks detected in SAP Cloud Integration for data services during the last 24h. The exceptions are retrieved from SAP Cloud Integration for data services via the central Exception Management in SAP Solution Manager.
Create Connection User
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 Integration for data services security guide: https://help.sap.com/viewer/f9f202d1c5924753833b487ac9306384/latest/en-US/d627c9c23a1c4311bd0f88a611ac2aa6.html
The Cloud Services configuration is now accessible from the SAP Solution Manager Configuration (SOLMAN_SETUP) → Managed Systems Configuration → Tab 'Cloud Services'.
Create Cloud Service:
The second step is to create the end-point for the cloud service.
Create the End-Point:
After the basic configuration you now have to configure Exception Management, as the exceptions collected via Exception Management and stored in the central exception store are the basis for the Integration Monitoring data collection.
Configuration for SAP Cloud Integration for data services
To access the Exception Management setup please go to transaction SOLMAN_SETUP → Application Operations → Exception Management
The last step is the configuration of Interface and Connection Monitoring. The Interface and Connection Monitoring setup can be accessed via SAP Solution Manager Configuration (SOLMAN_SETUP).
Configuration for Monitoring Template: Cloud (SAP Cloud Integration DS)
To access the Integration Monitoring setup please go to SAP Solution Manager Configuration (SOLMAN_SETUP) → Application Operations → Integration Monitoring → Interface and Connections.
Navigate to the step 'Define Scope'. You can create a new scenario for the SAP Cloud Integration for DS monitoring or use an existing one. Make sure the on premise system for the SAP Cloud Integration for DS scenario and the Cloud Service created for SAP Cloud Integration for DS is part of the Interface and Connection Monitoring scenario.
Create the Interface Channel:
Maintain the Interface:
Since the data collection is based on the content of the global exceptions store, you can always check the collected exceptions in Exception Management. All filter parameters are part of the collection context of the exceptions. The filters applied in Interface and Connection Monitoring allow you to filter the exceptions collected by the Exception Management further. However if the filters in Exception Management do not collect an exception, it is not available in the central exception store and you will not be able to find it in Interface and Connection Monitoring!
Thresholds and the collection schedule are maintained in the next step of the guided procedure. Once you have maintained all your channels, click 'Next' in the main guided procedure to move to the step 'Activation'.
Maintain Thresholds and Schedule:
If not active you can also activate the reporting for the channels by checking the box in the column 'Reporting'. This way you can see a history of the number of exceptions that happened and also place the metric on the OCC Dashboard in Focused Insights.