Skip to main content
Version: 26

Subaccount discovery

After provisioning your Global Account, Avantra discovers the entire hierarchy of your BTP account.

For Avantra to successfully discover a subaccount, the following services must be deployed into that subaccount's environment:

  • AvantraAccessDestinationService — Destination service with plan lite.
  • AvantraAccessAccountServiceLocalPlan — Cloud Management Service with plan local.
  • ServiceManagementAccessInstance — Service Manager with plan subaccount-admin.

All subaccounts must have these services, and each subaccount must have the following entitlements assigned:

  • Cloud Management Service — plan local
  • Destination — plan lite
  • Service Manager — plan subaccount-admin

Main monitor subaccount​

This is an Avantra concept, that refers to the subaccount you select when completing the Adding a BTP Global Account procedure.

The main monitor subaccount requires one additional service:

  • AvantraAccessUsageService — Usage Data Management Service with plan reporting-ga-admin

Setting up a subaccount​

Subaccounts must be discovered by Avantra. To do this automatically:

  1. Open a Global account.
  2. In the Properties tab > SAP BTP Global Account Info* you can:
    1. Check the Self Deployment checkbox to automatically create the required services on your BTP subaccount.
    2. Check the Assign missing entitlements automatically check to assign the entitlements required to deploy the services.
note

You can enable either or both options.

Manually setting up subaccounts​

If you prefer to set up subaccounts manually:

  1. Log into the BTP Cockpit and access your Global Account.
  2. Navigate to Entity Assignments and choose your target subaccount.
  3. Click Edit > Add Service Plans.
  4. Add:
    1. Cloud Management Service — plan local
    2. Service Manager — plan subaccount-admin
    3. Destination — plan lite
    4. Usage Data Management Service — plan reporting-ga-admin (main monitor subaccount only)
  5. Navigate to your subaccount and open Instances and Subscriptions.
  6. Create the following service instances:
    1. AvantraAccessDestinationService — create a service instance of type Destination with plan lite.
    2. AvantraAccessAccountServiceLocalPlan — create a service instance of type Cloud Management Service with plan local.
    3. ServiceManagementAccessInstance — create a service instance of type Service Manager with plan subaccount-admin.
    4. AvantraAccessUsageService — create a service instance of type Usage Data Management Service with plan reporting-ga-admin. (main monitor subaccount only)

After provisioning the services manually, Avantra detects the services and uses them to monitor the subaccount.

"In order for Cloud Foundry to be detected, an account is needed with access to the Cloud Foundry APIs. This account must be an Org Member with the Org Manager role."

Cloud Foundry Credentials​

For Cloud Foundry to be detected, an account with access to the Cloud Foundry APIs is needed. This account must be part of your subaccount's Cloud Foundry organization. To validate that the account is correctly configured, go to the Org Members tab under Cloud Foundry. The account must be listed there with the Org Manager role, and Space Developer must be assigned to the respective spaces under the organization.

The recommended method for this is to use a user from your SAP Cloud Identity Service.

If you have added a Custom Identity Provider for Platform Users under Security > Trust Configuration in the BTP Cockpit, you can select users from origins.

The password is set in SAP Cloud Identity Services. Log in as the user and set it at https://<unique>.accounts.ondemand.com/ui/protected/profilemanagement.

If not already done, for information on adding your SAP Cloud Identity Services instance, see SAP Documentation - Establish Trust and Federation of Custom Identity Providers for Platform Users . With that completed, you will need to provide the credentials in Avantra. To do this:

  1. In Avantra, open the SAP BTP Subaccount managed object.
  2. Click the Credentials tab.
  3. Enter a Name - the email address of the Org Member.
  4. Enter a Password.
  5. Enter the Origin associated with the Org Member.
note

Origins left blank will use the default origin sap.ids.

warning

The following is not recommended for setting up Cloud Foundry Credentials. However, if no Cloud Identity Service is present, it's possible to use an SAP S-number user from the SAP Identity Service. This is one that may be used to log into the SAP BTP Cockpit or SAP for Me. It is not recommended to use an S-user for Cloud Foundry observability in Avantra, as SAP intend S-users to be single named humans and the credentials should not be shared. This method has been tested and known to work.

To use an S-user, their password must be set at SAP Profile Management. This password must not be the same as any Universal ID password associated with the account. Store the username (email address) and password into the avantra.btp.cloudFoundry credential and leave the Origin field blank. If the SAP Identity Service is not the default origin, set the origin to sap.ids.