お問い合わせ

Setup for SAP Integration Suite (Cloud Integration) on Neo

This page explains how to connect SAP Integration Suite (Cloud Integration) running in the Neo environment to SAP Cloud ALM to enable monitoring.

Currently, the following monitoring applications are supported for SAP Integration Suite (Cloud Integration):

Setup Video

The following video demonstrates the setup steps to set up Integration & Exception Monitoring for SAP Integration Suite (Cloud Integration).

A detailed textual description for all setup steps is provided in the sections below the video.

 

Set Up Application Monitoring for SAP Integration Suite (Cloud Integration) running in Neo

  • Prerequisites for this video: 
    • You need a sub-account member with "Administrator" access for the SAP Integration Suite (Cloud Integration) sub-account in SAP BTP Cockpit
    • You need a user with the role "Integration Monitoring Integration Architect" in SAP Cloud ALM

Setup Steps in SAP Integration Suite (Cloud Integration)

OAuth Authentication: Prepare and obtain OAuth Credentials

If you want to use OAuth authentication to connect to SAP Integration Suite - Cloud Integration in the Neo environment, you must create a client with the correct authorizations.

Create OAuth Client

  1. Go to the SAP Business Technology Platform Cockpit
  2. Navigate to Applications → Subscriptions
    • Note down the "Provider Subaccount" for the application ending in "tmn" 
  3. Navigate to Security → OAuth
  4. Go to tab "Clients"
    1. Click "Register New Client"
    2. Choose a name
    3. Set the subscription to the CPI tenant (ends with "tmn")
    4. Generate an ID (it is recommended to use the suggested unique ID)
    5. Select Authorization Grant as "Client Credentials"
    6. Choose a Secret
    7. Make sure the "Token Lifetime" is set to 60 minutes (or 1 hour)
    8. Click on Save
  5. Note down the client ID, and the client secret for later use in SAP Cloud ALM
  6. Go to tab "Branding"
    1. Note down the "Token Endpoint" URL to be used as the Token Endpoint URL

Assign Roles for SAP Cloud ALM Monitoring

You can use the same client ID for all supported use cases. Make sure to select the appropriate roles for the client ID.

  1. Navigate to Security → Authorizations
  2. As a user, enter "oauth_client_<client_ID>" (the Client ID generated in the previous step)
  3. Grant the user the roles: You will find the roles under the correct provider sub-account for the application ending in "tmn"
    1. To use Integration & Exception Monitoring: Assign the roles:
      • IntegrationOperationsServer.read
      • NodeManager.read
    2. To use Health Monitoring: Assign the role:
      • HealthCheckMonitoringData.Read
  4. Save your changes.

Create HTTP End-Point

Before starting the setup, ensure that your cloud service was successfully imported from the System landscape Information Service (SLIS).

  1. Open the Landscape Management application from the launchpad
  2. Select your SAP Integration Suite (Cloud Integration) service
    • Select the cloud service with the service type "SAP Integration Suite (Cloud Integration)". The cloud service name will be the tenant ID. 
    • Do not choose the service with the service type "SAP BTP Neo environment" even if the cloud service name contains "Cloud Platform Integration"
  3. Press the ">" button at the end of the line
  4. On the tab "Endpoints" press the "Add" button to create a new endpoint
  5. Enter a description
  6. Choose the use-case.
  7. Ensure that the Root URL does not contain the path "/itspaces". 
  8. Choose OAuth2ClientCredentials (all fields are mandatory): 
    1. Client ID: oauth client ID
    2. Client Secret: client secret
    3. Token Service URL: Token Endpoint URL
    4. Token Service User*: oauth client ID
    5. Token Service Password*: client secret
  9. Save your endpoint

* Please note that the API Client ID and password must be added also to the Token Service user and password for the Exception Management endpoint.

Next Steps

After creating the endpoint in SAP Cloud ALM, you have to perform the following steps to activate the monitoring use-cases: