SAP Cloud Platform, the in-memory Platform-as-a-Service offering from SAP, enables customers and developers to build, extend, and run applications on SAP HANA in the cloud. It provides access to a development environment in the cloud. The platform includes a comprehensive set of services for integration, enterprise mobility, collaboration, and analytics.
For most cloud services, SAP Solution Manager is able to collect and monitor exceptions happening in the cloud service. But to fully monitor a cloud service scenario it is also important to monitor the integration between the cloud service and the on-premise backend system. This integration consists of different point-to-point interfaces of different usually more traditional types.
The following section describes the different integration options for the cloud service. Please choose the integration option you are using and consider also setting up the monitoring for the relevant interface types that are part of the integration scenario for the cloud service.
On this page we describe the monitoring setup this specific cloud service type. For information on how to set up the monitoring for the interface types supporting the integration, please refer to the setup documentation of the respective interface type which you can here.
For SAP Cloud Platform the following integration scenarios are possible:
The different scenarios contain the following exceptions and point-to-point connections:
Scenario Components | Monitored Content | Interface Channel Type | Since SP | |
---|---|---|---|---|
1 | Cloud Services: SAP Cloud Platform | Application errors and alert notifications from SAP CP | Cloud: Cloud (SAP Cloud Platform) | 7.2 SP03 |
2 | Cloud Services: SAP Cloud Platform Integration for data services | Exceptions in tasks in SAP CPI for data services | Cloud: Cloud (SAP HCI DS) | 7.2 SP03 |
3 | Cloud Services: SAP Cloud Platform Integration | Exceptions in integration flows (iFlow) in SAP CPI | Cloud: Cloud (SAP Cloud Platform Integration) | 7.1 SP12* |
4 | On-premise: SAP Cloud Connector | Availability and Performance for SAP Cloud Connector | Available monitoring content in System Monitoring | 7.2 SP06 |
*) Monitoring content was extended with later support packages (see monitoring template page for details)
The following technical prerequisites have to be met in order to monitor this scenario:
The following SAP Cloud Platform scenarios are currently covered in public cloud operations with SAP Solution Manager:
The collection of exceptions and alert notifications is performed using Exception Management. The metrics to monitor if there were any exceptions or alert notifications are available in a template in Interface and Connection Monitoring.
Metric Name | Description | MAI Category | Since SP |
---|---|---|---|
Number of exceptions in SAP CP Java Applications (Neo) |
Number of Java application errors collected from the SAP Cloud Platform. These statistics is retrieved from central Exception Management in Solution Manager. Data Collection is executed in delta mode. The statistics are based on single exceptions which are retrieved via an API from SAP CP into central Exception Management in Solution Manager |
Exceptions |
7.2 SP03 |
Single exceptions in SAP CP Java Applications (Neo) |
Single exceptions detected in SAP CP. Exceptions are retrieved via an API from SAP CP into central Exception Management in Solution Manager. Data Collection is executed in delta mode. |
Exceptions |
7.2 SP03 |
Alert Notifications received from SAP CP | Alert Notifications received from SAP Cloud Platform | Exceptions | 7.2 SP08 |
Trace Analysis, also allows you to trace end-user requests having excessive execution times, showing performance metrics, like application response time, interactions between UI and SAP Cloud Platform, and outbound communications.
The trace is collected from the backend system(s) as well as from the application running in SAP Cloud Platform. The SAP passport allows SAP Solution Manager to correlate the related steps over all components and display the complete end-to-end in the End-to-End Trace Analysis application in Root Cause Analysis.
Please note that the SAP backend system and all other systems that are part of the trace must be capable to handle SAP passport. You can find information which system types are supported by E2E Trace Analysis in SAP note 2248724 - Root Cause Analysis in SAP Solution Manager 7.2
For SAP Cloud Platform currently the following services are enabled for Trace Analysis.
SAP Cloud Platform Service | Description | Since SP |
---|---|---|
J2EE Web Profile 6 | Support SAP passport forwarding and performance statics | 7.2 SP06 |
SAPUI5 Runtime | Support SAP passport forwarding and performance statics | 7.2 SP06 |
Web Tomcat 7 & 8 (with limitations*) | Support SAP passport forwarding (with manual tasks) and performance statics | 7.2 SP06 |
(*) Due some technical/feature decisions in Cloud Platform for Runtime based on Tomcat8, the application developer need to take care for the SAP-PASSPORT update/forwarding by using a specific SapPassportHeaderProvider. You can find more information in the SAP Help documentation.
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 SAP Solution Manager does not apply to cloud services.
However, to be able to monitor exceptions and performance in cloud services they need to be connected to SAP Solution Manager. This connection is created using the customer and cloud service specific root URL and an end-point definition.
The first step is to import the SSL certificate into SAP Solution Manager. This is valid for all cloud services.
Import Cloud SSL certificate into STRUST
Export Certificate from Browser:
Import Certificate into SAP Solution Manager:
For a successful SSL handshake, please make sure the following parameter are set in the SAP Solution Manager system:
Additionally you have to perform certain preparations in the cloud service to enable SAP Solution Manager to connect to the cloud service.
The following section described the preparation steps that have to be performed if you run SAP Cloud Platform in the Neo environment. If you run SAP Cloud Platform in the Cloud Foundry environment please go to the next section.
Preparations for Java Application Error Monitoring
Determine Root URL
The API Root URL for SAP Cloud Platform depends on the host on which your account is hosted on. The host depends on the region as described here:
Create User for Java Log Monitoring
To connect to SAP Cloud Platform to collect Java application exceptions you need to provide SAP Solution Manager with a user that is allowed to read the default trace.
Write Java Errors into Default Trace
This last preparation step starts already during the development of the SAP Cloud Platform application. To be able to collect application errors, these errors must exist in the default trace for the SAP Cloud Platform java application. Hence developers must write meaningful errors in this trace. The quality of the monitored exceptions completely depends on the quality of the exceptions written by the developer.
Preparations for Alert Notifications
Enable SAP Cloud Platform Alert Notifications
Receiving alert notifications is done via the Alert Notification Service which can be enabled for your SAP Cloud Platform account.
Important: Please be aware that the use of this service is quota based (billable)!
To enable the service please follow the documentation:
Gather Connection Information
To authenticate towards the service you have to create an OAuth client in SAP Cloud Platform. Information how to do this you find here:
Please make sure to note down or copy the client secret, as it cannot be retrieved later on.
You will need the following connection information to connect SAP Solution Manager.
Import the SSL certificate for Cloud Foundry
Even if used in the SAP Cloud Platform (Neo) the alert notification service technically runs in SAP Cloud Platform (Cloud Foundry). To make sure that SAP Solution Manager can receive alert notifications successfully, you have to import the SSL certificate for Cloud Foundry additionally to the SSL certificate for Neo.
Preparations for E2E Application Tracing
Enable Automatic Trace Upload for SAPUI5 applications
You can enable the automatic upload of the client side trace data, which starts in the background when a trace is ended. Therefore, perform the following steps in your WebIDE or development platform for the SAPUI5 applications in focus.
Note: This operation has to be repeated for each relevant SAPUI5 application.
The following section described the preparation steps that have to be performed if you run SAP Cloud Platform in the Cloud Foundry environment.
Preparations for Alert Notifications
Enable SAP Cloud Platform Alert Notifications
Receiving alert notifications is done via the Alert Notification Service which can be enabled for your SAP Cloud Platform account.
Important: Please be aware that the use of this service is quota based (billable)!
To enable the service please follow the documentation:
Gather Connection Information
To authenticate towards the service you have to create an OAuth client in SAP Cloud Platform. Information how to do this you find here:
Please make sure to note down or copy the client secret, as it cannot be retrieved later on.
You will need the following connection information to connect SAP Solution Manager.
Create Custom Alerts
SAP Cloud Foundry doesn't have any available event that come out of the box. Hence to actually receive alerts from application in SAP Cloud Foundry you have to implement the alert creation in your application.
Find more information here:
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 (Neo):
Please not that you have to create two end-points if you want to monitor Java errors as well as receive alert notifications.
Create the End-Point (Cloud Foundry):
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 Platform Java Applications
This exception store will only exist if SAP Cloud Platform runs in the Neo environment!
To access the Exception Management setup please go to transaction SOLMAN_SETUP → Application Operations → Exception Management
To find out which Java application errors are written for the Java application you want to monitor, you can either ask the developer of the application or check if errors are available in your SAP CP subaccount under:
Applications → Java Applications → Click on the application name → Logging → Default Trace
Configuration for SAP Cloud Platform Alert Notifications
To access the Exception Management setup please go to transaction SOLMAN_SETUP → Application Operations → Exception Management
The following alerts are available in the different environments:
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 Platform)
To access the Integration Monitoring setup please go to SAP Solution Manager Configuration (SOLMAN_SETUP) → Application Operations → Integration Monitoring → Interfaces and Connections.
Navigate to the step 'Define Scope'. You can create a new scenario for the SAP CP monitoring or use an existing one. Make sure the on premise system for the SAP CP scenario and the Cloud Service created for SAP CP is part of the Interface and Connection Monitoring scenario.
Create the Interface Channel:
Maintain the Interface:
Select Metrics:
If you activate a metric please make sure:
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!
You can maintain attributes as described in the Interface and Connection Monitoring Setup on the tab 'Attributes'.
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:
To collect also the Java application part of a trace you need to activate the statistics for the Java application that you want to trace in SAP Cloud Platform.
Note: You need the role 'Developer' to start the statistics collection
For more information on the E2E Trace functionality and further prerequisites in SAP Solution Manager please refer to Using Trace Analysis.
You can start Trace Analysis for any SAPUI5 application, using the Diagnostics functionality, as described in the help portal (<Alt>+<Shift>+<Ctrl>+S key combination). Note: For mobile devices, refer to Mobile Diagnostics.
Important: Make the end-user starting a trace aware that his provided user-id is recorded in involved systems, as part of the trace data.