# B

## Basis Releases Supported for SAP Systems

## Supported SAP Basis Releases

The Avantra Agent monitors the following SAP Basis Releases:

- Releases 4.6C, 4.6D

- Release 6.40

- Releases 7.0x, 7.1x, 7.2x, 7.3x, 7.4x, 7.5x, 7.7.x

Unicode Kernels are supported as well.

## SAP BusinessObjects System

The BusinessObjects system type in Avantra lists systems which are SAP BusinessObjects Business Intelligence systems. We support BOBJ systems from version 4.2 onwards. These systems include checks to manage system uptime, performance, and job execution. A stand-alone database system type must be defined before adding a BusinessObjects system.

| The Business Object system type does not include SAP BusinessObjects Data Services (BODS). These systems are quite different as their underlying technology does not allow the same methods for monitoring.

## Business Service

A Business Service is a cross-system (and even a cross-customer) Composite Check. In other words, while input checks of a Composite Check must be executed on a system for which the Composite Check is defined, a Business Service can have arbitrary input checks.

And although every Business Service is “owned” by a customer, it may have input checks from other customers as well. Input checks for a Business Service can be a Built-in Check, a Custom Check, a Composite Check, a System Status, or another Business Service. Business Services also record Availability Data.

An example for a Business Service would be to correlate all SystemAlive Checks of all productive SAP Systems. A Business Service is a Managed Object as well as a Check, so you can apply Maintenance Windows to it, for example. And, of course, a Business Service has a Check Status.

## BTP Global Account

A SAP BTP (Business Technology Platform) Global Account serves as the highest organizational unit within the SAP BTP environment, acting as a central entry point for managing resources, subscriptions, and services across regions.

Avantra can integrate with a SAP BTP Global Account via a managed object. Creating a Global Account managed object will discover and populate any BTP Subaccounts that exist with the Global Account.

## BTP Subaccount

A SAP BTP (Business Technology Platform) Subaccount managed object is created by the discovery phase of a SAP BTP Global Account, and will be linked to it.

During detection, the Subaccount will display the SAP BTP CF Applications tab, where the SAP BTP Cloud Foundry Application applications will be listed. The tab Cloud Services lists any cloud services that are discovered. Both the Cloud Foundry Applications and Cloud Services will be grouped by the Subaccount they are associated with.

## Cloud Foundry Credentials

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.

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.

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

| The following is not recommended for setting up Cloud Foundry Credentials. However, if no Cloud Identity Service is present, it is 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 https://accounts.sap.com/ui/protected/profilemanagement. 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`.