Managed BTP systems
The SAP BTP managed system displays all of the SAP BTP objects that are in Avantra. By adding a BTP Global Account, Avantra will discover and populate any BTP Subaccounts, Cloud Foundry applications and managed systems that exist with the Global Account. Each Subaccount is added as a child object of the Global Account, and any services or subscriptions within the Subaccount are added as child objects of the Subaccount. Each object can be opened to view more details, and the relevant monitoring and automation capabilities can be enabled.
BTP system types
Avantra identifies the type of each BTP Managed System from the properties of the discovered service or subscription. The following system types are currently supported:
| BTP system type | Description |
|---|---|
| SAP Build Work Zone, standard edition | Subscription-based managed system for the SAP Build Work Zone launchpad service, standard edition. |
| Automation Pilot | Subscription-based managed system for SAP Automation Pilot. |
| Integration Suite - API Management | Subscription-based managed system for the API Management capability of SAP Integration Suite. |
| Continuous Integration & Delivery | Subscription-based managed system for the SAP Continuous Integration & Delivery service. |
| Destination | Instance-based managed system for the SAP BTP Destination service. |
| Job Scheduling Service | Instance-based managed system for the SAP BTP Job Scheduling Service. |
| Print Service | Instance-based managed system for the SAP BTP Print Service. |
| Event Mesh | Instance-based managed system for SAP Event Mesh, default edition. |
| Cloud Transport Management | Instance-based managed system for SAP Cloud Transport Management. |
Credentials
Some BTP Managed System types require credentials to enable monitoring. Where required, credentials are detected automatically from the BTP mapping configuration. Avantra retrieves a service key associated with the managed system and uses it to authenticate against the service API.
If credentials are provided manually, Avantra uses them directly without performing service key validation.
If no credentials are configured, Avantra treats the system as not requiring authentication and continues monitoring without credential validation.