Managed BTP systems

A Managed BTP System represents a combination of service instances and subscriptions under your subaccount.

By adding a BTP Global Account, Avantra discovers any BTP Subaccounts beneath it. Within each Subaccount Avantra discovers the Cloud Foundry Applications, service instances, and subscriptions. An instance or subscription is converted into a monitored Managed BTP System when it matches one of the supported BTP system types.

note

Managed BTP Systems require the btp-functions add-in to be installed as a prerequisite.

BTP system types

Avantra identifies the type of each BTP Managed System by matching the properties of the discovered service or subscription against a set of criteria. A discovered instance or subscription is mapped to a system type only when all of its criteria match. The following system types are currently supported:

BTP system type	Description	Matched when
SAP Build Work Zone, standard edition	Subscription-based managed system for the SAP Build Work Zone launchpad service, standard edition.	The subaccount has a subscription to SAP Build Work Zone, standard edition.
Automation Pilot	Subscription-based managed system for SAP Automation Pilot.	The subaccount has a subscription to SAP Automation Pilot.
Integration Suite - API Management	Subscription-based managed system for the API Management capability of SAP Integration Suite.	A service instance named AvantraAccessAPIIntegrationSuite exists, of service type apimanagement-apiportal with plan apiportal-apiaccess. This instance must be created manually with this exact name to be detected, as Avantra only detects the API Management system when an instance with this exact name exists.
Continuous Integration & Delivery	Subscription-based managed system for the SAP Continuous Integration & Delivery service.	The subaccount has a subscription to Continuous Integration & Delivery.
Destination	Instance-based managed system for the SAP BTP Destination service.	A service instance of the Destination service exists, using the lite plan, in the Cloud Foundry environment.
Job Scheduling Service	Instance-based managed system for the SAP BTP Job Scheduling Service.	A service instance of the Job Scheduling Service exists, using the standard plan.
Print Service	Instance-based managed system for the SAP BTP Print Service.	A service instance of the Print service exists, using the sender plan.
Event Mesh	Instance-based managed system for SAP Event Mesh, default edition.	A service instance of the Event Mesh (Enterprise Messaging) service exists, using the default plan.
Cloud Transport Management	Instance-based managed system for SAP Cloud Transport Management.	A service instance of the Cloud Transport Management service exists, using the standard plan.

Credentials

Some BTP Managed System types require credentials to enable monitoring, while others, for example, subscription-based systems such as SAP Build Work Zone or Automation Pilot, require none.

Automatically detected credentials

Where credentials are required, Avantra resolves them automatically from the BTP mapping configuration. Avantra retrieves an OAuth service key associated with the managed system and uses it to authenticate against the service API. Depending on the system type, the service key is sourced in one of two ways:

• From the system's own service instance: For most instance-based systems, for example, Destination, Job Scheduling Service, Print Service, Event Mesh, and Cloud Transport Management, Avantra retrieves the service key directly from the managed system's own service instance.
• From a dedicated dependency instance: For some systems, the credentials depend on a separate service instance that Avantra provisions specifically for access. For example, Continuous Integration and Delivery uses a dedicated cicd-service instance. Avantra creates the required service instance and key and uses it to authenticate.

The following table shows where the credentials for each system type are sourced from:

BTP system type	Credential source
SAP Build Work Zone, standard edition	No credentials detected. Provide manually if required.
Automation Pilot	No credentials detected. Provide manually if required.
Integration Suite - API Management	A service key AvantraAccess is created on the system's own service instance.
Continuous Integration & Delivery	A dedicated dependency instance AvantraAccessCID (offering cicd-service, plan default) is created, with a service key AvantraAccess.
Destination	A service key AvantraAccess is created on the system's own service instance.
Job Scheduling Service	A service key AvantraAccess is created on the system's own service instance.
Print Service	A service key AvantraAccess is created on the system's own service instance.
Event Mesh	A service key AvantraAccess is created on the system's own service instance.
Cloud Transport Management	A service key AvantraAccess is created on the system's own service instance.

Manually provided credentials

Any managed system can be given credentials manually. Manual credentials always take priority over automatically detected ones. When manual credentials are present, Avantra uses them directly and does not perform service key retrieval or validation.

If no credentials are configured and none are required, Avantra treats the system as not requiring authentication and continues monitoring without credential validation.

Self Deployment

When Self Deployment is enabled, Avantra automatically provisions the service configuration each managed system needs, creating the service instances and service keys described in the credentials table above.

When Self Deployment is disabled, Avantra does not create anything in your subaccount, and the required service configuration must be provisioned manually. Use the the tables above to reference what to create:

• From the BTP system types table: create the service instance or subscription with the offering and plan listed under Matched when for the system type you want monitored.
• From the credential source table: create the corresponding service key (and, where applicable, the dedicated dependency instance) so Avantra can authenticate against the service API.

Once the service configuration exists, Avantra detects it during discovery and begins monitoring the managed system.