Show TOC

Procedure documentationIntegrating Cloud Services for Exception Monitoring

 

You can monitor exceptions that occur in supported cloud services, in the context of an SAP-based hybrid monitoring scenario. To configure the connection between SAP Solution Manager and the cloud service, use the Basic Setup for Monitoring SAP Based Hybrid Solutions (transaction S2C_SETUP), which provides templates for integrating various types of cloud services.

SAP Solution Manager can collect data from cloud services in different ways, depending on the cloud service type. For each cloud service, you define one or more endpoints for the data collection. There are three types of endpoints:

  • HTTP endpoints allow data collection through a direct connection between the SAP Solution Manager ABAP system and the cloud service URL. You can create HTTP endpoints for any supported cloud service.

  • E-mail endpoints allow collection of data from automated e-mails sent by the cloud service to a dedicated SAP Solution Manager inbox user. You might choose to create e-mail endpoints rather than HTTP endpoints, for example, if your Dell Boomi bandwidth cap has been exceeded and exceptions are no longer generated through direct monitoring, or if the cloud service URL cannot be accessed from your SAP Solution Manager system for some reason. You can create e-mail endpoints for Dell Boomi and SAP SuccessFactors cloud services.

  • (S)FTP endpoints allow collection of data from a remote SFTP server by a diagnostics agent running on the SAP Solution Manager host. You can create (S)FTP endpoints for SAP SuccessFactors cloud services.

When you integrate a cloud service, the system automatically creates an LMDB object for the service, which allows it to be addressed as a technical system in SAP Solution Manager.

Prerequisites

  • The cloud service provider has set up your test and production cloud services.

  • For e-mail endpoints, SAP Solution Manager must be set up to send and receive e-mail via SMTP. For more information, see SAP Note 455140Information published on SAP site.

  • For remote file monitoring via SFTP, the diagnostics agent must be connected to SAP Solution Manager and running. The network ports (firewall) must be open so that the agent can access the SFTP server located in the cloud.

  • You have SAP Solution Manager administrator authorizations, including authorization for the S2C_SETUP transaction.

Procedure

Overview of Steps

  1. Create a monitoring concept and collect the technical information required to connect SAP Solution Manager to the cloud service.

  2. If you plan to create HTTP endpoints, import the SSL certificates into the SAP Solution Manager trust store.

  3. If you plan to create e-mail endpoints, create a dedicated SAP Solution Manager inbox user for the cloud service.

  4. In S2C_SETUP, create the connection and define the required endpoints, according to your concept.

  5. For HTTP and e-mail endpoints, navigate to Exception Management and configure the data collection.

  6. Configure an Interface and Connection Monitoring scenario that includes the cloud service.

Note Note

If you want to delete an SAP Solution Manager-to-cloud service connection, be sure to deactivate monitoring in Exception Management first. The procedure is described in the section Deleting a Connection below.

End of the note.
Collecting Technical Information for the Connection

Collect technical information about the cloud service from the responsible people in your organization. Make sure that you collect data for both the test and production cloud services.

Determine which endpoints you have to create depending on your use case. Use the following check list to collect the required information to set up the connection:

Endpoint Type

Required Information

HTTP endpoint

User

Password

Access URL

  • Dell Boomi: Request the test and production account IDs to create the URLs.

    Schema: http://platform.boomi.com:443/api/rest/v1/<account ID>

    Example: http://platform.boomi.com:443/api/rest/v1/successfactors-ET1234G

  • SAP Cloud for Customer (C4C): Request the main URL.

    Schema: https://<Main URL>

    Example: https://qxp-cust123.dev.sapbydesign.com

    Note Note

    If you cannot connect to the service using the generated logical port URL (an error is displayed in the extractor logs, or you cannot ping the service in SOA Manager), you can use the full access URL instead.

    Example: https://ldai01qxl.wdf.sap.corp:50001/sap/bc/srt/scs/sap/codquerywebservicemonitorforso?sap-vhost=qxl-cust233.dev.sapbydesign.com.

    End of the note.

  • SAP HANA Cloud Integration (HCI): Request the tenant ID to create the URL.

    Schema: https://<tenant ID>.neo.ondemand.com/api/v1/

    Example: https://tmpmtpw2avtprsm-pw2.neo.ondemand.com/api/v1/

  • SAP SuccessFactors (access via OData API): Request the full OData URL or the main host URL. If you enter the main URL, the OData extension will be appended automatically.

    Example: https://qacand.sflab.ondemand.com/odata/v2/restricted/EMEvent

    Example: https://qacand.sflab.ondemand.com/

  • SAP Sales and Operations Planning: Request the full URL or the main host URL.

    Example: https://lvpal404.pal.sap.corp:4300/sap/sop/sopfnd/services/solman/api.xsjs

If applicable: proxy server URL, user and password

E-Mail endpoint

If you plan to use a single SAP Solution Manager inbox for multiple cloud services, then you need to know the cloud service provider's e-mail address.

If you plan to create a dedicated SAP Solution Manager inbox for each cloud service (recommended), the sender's e-mail address is not required.

(S)FTP endpoint

User

Password

Protocol (FTP or SFTP)

Host name and port of the cloud service's (S)FTP data exchange server

Time zone of the SFTP server. The person responsible for the cloud service can check a timestamp to identify the time zone.
Importing SSL Certificates into the SAP Solution Manager Trust Store

Perform this activity if you plan to create HTTP endpoints.

  1. Enter the access URL for the service in your browser and log in.

  2. Export the SSL certificate.

    Example Example

    In Google Chrome, do the following:

    1. Right-click on the page and choose View page info.

    2. On the Connection tab page, choose the Certificate information link.

    3. On the Details tab page, choose Copy to File to start the export wizard.

    4. Choose Base-64 encoded x.509 (.CER) and export the certificate to a file.

    End of the example.

  3. Start transaction STRUST.

  4. Double-click SSL client SSL Client (Anonymous) and import the certificate.

Creating Dedicated SAP Solution Manager Inbox Users for Cloud Service E-Mail

Perform this activity if you plan to create e-mail endpoints instead of HTTP endpoints for SAP SuccessFactors or Dell Boomi services. You will enter this inbox user ID when defining the endpoint in S2C_SETUP.

The inbox will be assigned automatically to the extractor framework user (default: SM_EFWK), which allows SAP Solution Manager to parse the content of the e-mails and generate exceptions.

  1. In transaction SU01, create a dialog or system user.

    Example Example

    For SuccessFactors BizX, enter the user name BIZX. In the Last Name and First Name fields, enter BIZX and Cloud Product Integration to identify the user later.

    End of the example.

  2. Enter the e-mail address to which the cloud service error messages are to be sent. Use the domain of the SAP system client if possible. For more information, see SAP Note 455140Information published on SAP site.

    To receive e-mails, no authorizations are required.

  3. Tell the person responsible for the cloud service to dispatch error message e-mails from the cloud service to the SAP Solution Manager inboxes.

Recommendation Recommendation

Create separate inbox users to differentiate between the test and production cloud services. If you create just one inbox, make sure you know the sender's e-mail addresses for both the test and production cloud servers.

End of the recommendation.
Creating the Connection and Defining the Endpoint

For each cloud service, perform this activity for both the test and production cloud services.

  1. Start transaction S2C_SETUP.

  2. Select the cloud service type, and then chose Add.

  3. Enter a name and a meaningful description of the cloud service, and save.

  4. To define an endpoint, select the connection, and then select the tab page for the type of endpoint you want to create.

  5. Add a new end point.

  6. Enter the technical information you collected, and save.

The system automatically creates a system ID (HCI~UNSPAPP, for example), which is displayed in the Cloud Service ID column. When you set up monitoring, this system ID will allow you to address the cloud service as a technical system in the SAP Solution Manager system landscape.

Note Note

When you configure an e-mail endpoint, the extractor framework user (default: SM_EFWK) is assigned automatically to the cloud service inbox user as a substitute.

If you receive an error message saying that the extractor framework user could not access the cloud service user inbox, it means that this automatic process failed. The following steps describe how to define the substitution manually.

  1. Log on to the SAP Solution Manager system using the credentials of the cloud service inbox user.

  2. Start the Business Workplace (transaction SBWP).

  3. In the Settings menu, choose Office Settings.

  4. On the Substitute tab page, choose the Create icon on the left side.

  5. In the Create Substitute dialog box, enter SM_EFWK as the substitute. Define a substitution period and choose the Inbox and Outbox substitution authorizations. Confirm your entries.

  6. Log on to the SAP Solution Manager system using the credentials of the extractor framework user SM_EFWK.

  7. Start the Business Workplace (transaction SBWP).

  8. In the Settings menu, choose Start of the navigation path Workflow Settings Next navigation step Maintain Substitute End of the navigation path.

  9. Select the extractor framework user SM_EFWK and choose the Create substitute icon.

  10. Search for the cloud service inbox user you created (BIZX, for example), and confirm.

  11. Enter a validity period, choose the Substitution active check box, and confirm.

E-mails in the cloud service inbox will now be dispatched to the extractor framework user (SM_EFWK) inbox.

End of the note.
Configuring Monitoring in Exception Management

For HTTP and E-mail endpoints, perform this activity to configure and activate exception monitoring. This activity is not relevant for (S)FTP endpoints.

  1. In the Basic Setup for Monitoring of SAP-Based Hybrid Solutions (transaction S2C_SETUP), select the connection, and then navigate to the Exception Management setup.

  2. On the Exceptions Sources tab page, choose Configure Log Store.

    The available log stores for the service type are displayed.

  3. Choose a log store and select the corresponding endpoint.

  4. Save your entries.

    Recommendation Recommendation

    For HTTP endpoints, specify selection filters for each log store in order to limit data extraction to business-critical exceptions, to improve performance and avoid exceeding cloud service bandwidth caps.

    End of the recommendation.

  5. Add and configure additional log stores if desired.

  6. Save your entries.

  7. To verify that exceptions are being collected, check the Exception Management cockpit in the Root Cause Analysis work center. The cloud system is represented as a technical system of type UNSPAPP (unspecific standalone application system).

Configuring an Interface and Connection Monitoring Scenario

In the Basic Setup for Monitoring of SAP-Based Hybrid Solutions (transaction S2C_SETUP), select the connection, and then navigate to the Interface and Connection Monitoring setup.

Follow the instructions under Configuring an Interface and Connection Monitoring Scenario.

Deleting a Connection

Before you delete a connection to a cloud service, ensure that the monitoring is deactivated.

  1. In the Basic Setup for Monitoring of SAP-Based Hybrid Solutions (transaction S2C_SETUP), select the connection and choose Where Used.

  2. If a message informs you the that the cloud service is used in Exception Management, navigate to the Exception Management setup. Remove the log stores associated with the cloud service, and save.

  3. Go back to the basic setup and choose Where Used again.

  4. If the cloud service is not used, you can safely delete it.