SAP Fieldglass is a Software-as-a-Service solution that offers services for external workforce management and services procurement. SAP Fieldglass integrates seamlessly with SAP on-premise solutions via webservices, SAP PI or SAP Cloud Platform Integration.
Unlike the classic point-to-point interfaces like e.g. IDocs, Web Services or RFCs, when talking about monitoring for cloud services, you always also have to consider the integration component of the scenario. For most cloud services, Advanced Integration Monitoring for the cloud service itself concentrates on monitoring 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 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 categories that are available for this specific cloud service type. For information on how to set up the monitoring categories for the other technical system and cloud service types, please refer to the setup documentation of the respective interface type.
After setting up the monitoring for the single components and interface types, you can use the scenario configuration to group all relevant messages and exceptions of the cloud integration scenario in one Advanced Integration Monitoring scenario. Information how to create scenarios can be found here.
For SAP Fieldglass the following integration scenarios are possible:
The different scenarios contain the following exceptions and point-to-point connections:
|Scenario Component||Monitored Content||Monitoring Category|
|1||Systems: ABAP on-premise system||Web Service errors and exceptions||Web Service Messages (ABAP), Web Service (Performance)|
|2||Systems: ABAP on-premise system||Messages in the ABAP proxy framework||ABAP: PI Messages|
|3||Cloud Services: SAP Cloud Platform Integration||Integration flows (iFlow) in SAP CPI||SAP Cloud Platform Integration|
|4||Systems: PI on-premise system||PI messages send via SAP PI||
Java: PI Communication Channels, PI Messages
|5||Cloud Services: SAP Fieldglass||Exceptions that occur in the SAP Fieldglass||SAP Fieldglass Integration, SAP Fieldglass Subscription|
When you set up the exception collection and monitoring you first need to know or identify with PI services, Web Services or SAP CPI iFlows are relevant for each scenario. You can find the setup information and also the relevant web service proxies here: https://api.sap.com/package/SAPS4HANAintegrationwithSAPFieldglass?section=Overview
SAP Fieldglass scenarios covered by Focused Run
SAP Fieldglass integration happens via two major areas, batch integration and real-time integration. Batch integration is mainly used for master data like user data, organizational data and so on. Real-time Event-driven integration is used for data that needs to be exchanged based on workflows and in real-time like work orders, invoiced etc.
The following SAP Fieldglass scenarios are currently covered Focused Run:
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 Fieldglass
Maintain Fieldglass Partner
To connect to Fieldglass via any API you need to have a Fieldglass Partner Key. Usually, you get this partner key as soon as you integrate with Fieldglass via any web service API. This is usually already done during the Fieldglass Implementation. You can use this same partner key for the Focused Run integration.
If you didn't integrate via a web service API with Fieldglass but instead e.g. use file integration, you might not have a Fieldglass partner key yet.
To request a partner key for the Focused Run Integration you can either create a ticket with the SAP Fieldglass Service Desk or contact your Account Service Representative.
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 Fieldglass
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 Fieldglass
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 Fieldglass different monitoring categories are 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
For both categories, you can either collect all exceptions happening in SAP Fieldglass for your customer ID or you can filter them using the following criteria:
SAP Fieldglass Integration
SAP Fieldglass Subscription
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.
For SAP Fieldglass the following metrics are collected:
SAP Fieldglass Integration
SAP Fieldglass Subscription