SAP Fieldglass

Available Monitoring Content

SAP Fieldglass MessagesMessagesMessages send from and to SAP Fieldglass which are recorded in the Subscription Audit Trail, the Integration Audit Trail and the Event Driven Audit Trail

Setup Steps in SAP Fieldglass

Collect OAuth Connection Information

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 WebService API. In most cases this is already done during the Fieldglass Implementation. You can use this same partner key for the SAP Cloud ALM integration.

If you didn't integrate via an WebService 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 SAP Cloud ALM Integration you can either create a ticket with the SAP Fieldglass Service Desk or contact your Account Service Representative. 

Fieldglass will provide you with user credentials and a client-specific application key.

Find more information here.


Setup Steps in SAP Cloud ALM

Create HTTP End-Point

  1. Open the Landscape Management application from the launchpad
  2. Select your SAP Fieldglass service
  3. Press the > button at the end of the line
  4. On the tab "Endpoints" press the Add button to create a new end-point
  5. Enter a description
  6. Choose the use-case "Integration Monitoring"
  7. Enter the Connection Test Path:
    • /api/vc/IntegrationMonitoringPullAPI
  8. Choose OAUTH authentication enter the OAuth credentials retrieved from SAP Fieldglass:
    • Client ID: The ID part of your partner key (the part before '/')
    • Client Secret: The password part of your partner key (the part after '/')
    • Token Service URL: Extend your  Fieldglass  URL with '/api/oauth2/v2.0/token?grant_type=client_credentials&response_type=token'
    • API Key: X-APP key provided by SAP Fieldglass

Connection Error with Cloud ALM 2011

Please note that with SAP Cloud ALM Release 2011 there might be an error if you perform a connection test. This doesn't influence the Interface Monitoring data collection and this error can be ignored.

Error message when clicking 'Ping Connection'

  • [401] Connection to <FG Cloud Service> cannot be established. Ensure that the URL and the login credentials, which are maintained for the endpoint, are correct.

When clicking 'Check Connection' during the end-point creation you will see the following error message

  • Connection to <FG Cloud Service> cannot be established - [Failed to obtain OAuth access token]. Ensure that the URL and the login credentials, which are maintained for the endpoint, are correct. - return code 401

Activate Monitoring (Standard)

In SAP Cloud ALM you can easily activate the standard monitoring content without any additional setup effort. 

  1. Open the Integration & Exception Monitoring application from the launchpad
  2. The scope selection will appear automatically
  3. Change the drop-down for Display Service to "All"
  4. Make sure to select your cloud service in the scope
  5. Click the Configuration button in the upper right corner to access the configuration
  6. Expand the Configuration panel
  7. Change the toggle button next to the cloud service from OFF to ON

Adjust Monitoring and Alerting (Expert)

You can change which parts of the standard content are activated for each cloud service, activate and deactivate alerts or create own alerts with specific filters. 

  1. In the configuration panel, click on the name of the cloud service
  2. The "Configuration of Services" screen opens
  3. In the "Configuration for Services" screen, click the > button at the end of the line for the cloud service you want to change

Adjust Monitoring Categories

  1. Use the toggle button in the column Active to turn a monitoring category ON or OFF

Adjust Alerting

  1. Use the toggle button in the column Active to turn a standard alert ON or OFF
  2. Press the > button at the end of the line to access the detail setup for an existing alert or use the + button to create a new alert
  3. Adjust the display name if desired
  4. Expand the Filter Configuration tray
  5. Enter a filter name
  6. Select the filter category
  7. Maintain the available filter fields (see details below)

Available Alerts for SAP Fieldglass

  • Erroneous Fieldglass Message Detected: Creates an alert for each failed message in SAP Fieldglass
  • Erroneous Fieldglass Messages Detected: Creates an alert if one or more failed messages on SAP Fieldglass were detected since the last data collection

Available Filter Fields for SAP Fieldglass

The filter fields depend on the monitoring category the alert is created for and additional on the filter category, if there is more than one available.

Fieldglass Messages

  • Direction: Inbound or Outbound
  • Category Type: Subscription Audit trail, Integration Audit trail or Event Driven Audit trail
  • Name: Message name (see Application Data tab for collected messages)

  • Status: Status of the message
  • Status Group: Successful, Warning, Error, In Process, Canceled, Others
  • Status Details: Filter on the Status Text