Skip to main content
Version: 26

Adding a BTP Global Account

To monitor an SAP BTP Global Account in Avantra, it's necessary to set up API access to one Cloud Management Service (central plan) with a service binding inside a single Subaccount. Avantra subsequently discovers the associated global account, all directories and other Subaccounts, the activated environments, applications and services. For more information on Cloud Management Service (central plan), see SAP Documentation - SAP Cloud Management Service for SAP BTP for information.

note

Avantra creates the service instances and service bindings required to monitor all discovered Subaccounts.

Configuring a BTP Global Account in Avantra​

Prerequisites​

You require the following:

  • A Global Account in Feature Set B.
  • A user with the role Global Account Administrator.

Set up in the BTP Cockpit​

Before you can configure a Global Account in Avantra, you need to set up the account in the BTP Cockpit.

  1. Log into the BTP Cockpit and access your Global Account. For additional information see SAP Documentation - Log On to Your Global Account.
  2. A Subaccount is required to enable monitoring. Either select an existing one, where a user is a member with the role Subaccount Administrator, or create a Subaccount. For information on how to create a Subaccount, see SAP Documentation - Create a Subaccount.
  3. Create a new service instance of the Cloud Management Service. For information, see SAP Documentation - Creating Instances in Other Environments.
    1. Specify Service as Cloud Management Service.
    2. Specify Plan as Central.
    3. Specify Runtime Environment as Other.
    4. Instance Name can be named as per requirements.
  4. Click Next.
    1. Specify the parameter Authorization Type as Client Credentials.
  5. Click Create.
  6. Create a Service Binding in the Service Instance. For information, see SAP Documentation - Creating Service Binding in Other Environments.
    1. Specify a Binding Name.
    2. There is no requirement to upload a JSON file.
  7. Open the Service Binding and make a note of the following values, as they are required for the remaining setup. The most efficient way is to copy the JSON file:
    1. endpoints
      1. accounts_service_url
    2. uaa
      1. clientid
      2. clientsecret
      3. url

Set up in Avantra​

  1. Navigate to Systems > SAP BTP.
  2. Click New > New SAP BTP Global Account.
    1. Define the account with a Name.
    2. Select a Customer.
    3. Select a System Role.
    4. Click New.
  3. Double-click the newly created account to open it.
  4. In the Credentials tab, add the OAuth credentials. Using the values noted from the Service Binding:
    1. Add a Name for the credentials.
    2. Add the clientid, from the Service Binding, into the Client ID field.
    3. Add the clientsecret, from the Service Binding, into the Client Secret field.
    4. Add the url, from the Service Binding, into the Access Token URI field, and add /oauth/token to the end.
    5. Click OK.
  5. Click Apply.
  6. Click Yes.
  7. In the Properties tab:
    1. Assign a Monitoring Server for the global account.
    2. Define the accounts_service_url in the Accounts Service URL of Cloud Management Service, central plan field.
    3. Check the Self Deployment checkbox.
    4. The Add new Subaccount as operational (consumes license) checkbox is checked by default. Unchecking this checkbox creates any found Subaccounts as NonOperational, without consuming a license and without monitoring or automation capabilities enabled until manually made Operational.
    5. The Assign missing entitlements automatically checkbox is unchecked by default. When checked, Avantra automatically assigns missing entitlements, needed for Avantra monitoring, to the Subaccount.
  8. Click Apply.
  9. Click Send to Agent.
  10. Click Send.

The Global Account monitoring can now be enabled. To do so, click Monitoring Switch. The Edit Monitoring Switch dialog displays the Global Account and all associated Subaccounts.

Properties​

In Properties > SAP BTP Global Account Info, three properties control how the discovery process behaves:

  • Self Deployment: Gives Avantra permission to deploy the services required to run discovery. When enabled, the discovered Subaccounts are deployed by Avantra. When disabled, these services must be created using the manual set up process.
  • Assign missing entitlements automatically: When enabled, the entitlements required to deploy the services are also assigned to the Subaccount by Avantra. When both Self Deployment and this option are enabled, the discovery process is fully automated.
  • Add new Subaccount as operational (consumes license): When enabled, any newly detected Subaccount is made operational in Avantra and consumes a license. The discovery process actively listens to your BTP environment, so when a new Subaccount is added in BTP, it is detected by Avantra. If this option is enabled, the new Subaccount is made operational automatically. A non-operational Subaccount is one Avantra does not interact with, meaning no service deployment or entitlement assignment is performed against them.

Inventory​

The Inventory tab of the Global Account displays the discovered inventory of the Global Account, including all directories and Subaccounts, the activated environments, applications and services. You can drill down and open each item to view more details.