Take a Tour of SAP BTP Trial

So, you’ve signed up for SAP BTP trial but are not quite sure where to start? This tutorial is here to help!

A trial account on SAP Business Technology Platform enables you to experience the platform for free for a limited amount of time, offering access to a comprehensive set of platform services, as well as early access to beta functionality. Trial accounts are intended for personal exploration, and not for production use or team development. They allow restricted use of the platform resources and services.

Note: You want to explore SAP Business Technology Platform without time constraints? See [btp-free-tier-account](Get an Account on SAP BTP to Try Out Free Tier Service Plans)

You can use your SAP BTP trial account for up to 365 days in total. However, your trial account is suspended after 30 days but don’t worry, you can easily extend that time by selecting Extend Trial in the popup window that appears once your trial account has been suspended. After 365 days total, you trial account is deleted but you can always create a new account. For more information, see Trial Accounts.

All trial accounts are already using cloud management tools feature set B. See: Cloud Management Tools — Feature Set Overview.

If you ever want to delete your trial account, you can navigate to the Subaccounts page in the global account scope and select Delete Trial.

SAP BTP currently offers these environments for trial accounts: Cloud Foundry, ABAP, and Kyma.

To become familiar with the specifics of the trial offerings, have a look at the following resources:

• Getting Started with a Trial Account in the Cloud Foundry Environment
• Getting Started with a Trial Account in the ABAP Environment
• Getting Started with a Trial Account in the Kyma Environment

Cloud Foundry

In addition to global accounts, directories, and subaccounts, the Cloud Foundry environment includes another hierarchical level represented by orgs and spaces.

Each Cloud Foundry subaccount contains exactly one Cloud Foundry org. They have a 1:1 relationship. When you create a Cloud Foundry trial account, you get a global account with one Cloud Foundry subaccount in it, where the org is created automatically. You have the option to create additional Cloud Foundry subaccounts within your trial global account, however, in those, you must create an org yourself by selecting Enable Cloud Foundry.

In your org, you can then create one or more spaces, where you deploy apps and use services. Similar to subaccounts, spaces enable you to once again structure and subdivide quota if you want to. When you create your Cloud Foundry trial global account in the cockpit, one space is also automatically created within your org. You also have the option to add additional ones if you like.

ABAP

Within the Cloud Foundry environment, you can create a new space for ABAP development. This is what we refer to as the ABAP environment. It allows you to create extensions for ABAP-based products, such as SAP S/4HANA Cloud, and develop new cloud applications. You can transform existing ABAP-based custom code or extensions to the cloud.

The ABAP environment is based on the latest ABAP platform cloud release that is also used for SAP S/4HANA Cloud. It leverages the innovations provided by SAP HANA. The software stack contains standard technology components that are familiar from the standalone Application Server ABAP. The ABAP environment supports the ABAP RESTful Application Programming Model including SAP Fiori and Core Data Services (CDS). SAP Services and APIs are offered according to a new allowlist approach. The ABAP environment provides technical access to SAP Business Technology Platform services, such as destination service, integration, machine learning, and IoT.

Kyma

Kyma environment is a runtime you can use to build cloud-native Kubernetes-based extensions by using microservices and serverless functions. The offered functionality ensures smooth consumption of SAP and non-SAP applications, running workloads in a highly scalable environment, and building event-based and API-based extensions. To enable Kyma trial, log in to your SAP BTP trial home, create a subaccount, add entitlements, and select Enable Kyma in the Overview section of your subaccount.

You should understand the difference between entitlements and quota, because you’ll encounter these two terms quite often.

• Entitlements are your right to provision and consume a resource. They refer to what you’re entitled to use (for example, which services and service plans).
• Quota is the numeric quantity that defines the maximum allowed consumption of that resource. In other words, how much of a service plan you’re entitled to use.

Entitlements and quotas are managed at the global account level, distributed to directories and subaccounts, and consumed by the subaccounts.

When you remove quotas or entitlements from one subaccount, they become available again at global account level and can be assigned to other subaccounts.

For more information on entitlements, you can always consult documentation on Entitlements.

If you run into problems regarding entitlements and quotas, you can check out the Guided Answers.

Now that you know what to expect from your trial account, let’s learn about how things are structured in SAP BTP.

Your global account, directories, and subaccounts in SAP BTP structure all your activities.

A global account is the realization of a contract you made with SAP (be it enterprise or trial). It’s region-independent, and it’s used to manage subaccounts, members, and quotas. You receive quotas to use platform resources per global account and then distribute the quotas to the subaccount for actual consumption. A global account can contain one or more subaccounts in which you deploy applications and use services.

Directories allow you to organize and manage your subaccounts according to your technical and business needs. A directory can contain one or more subaccounts. It can’t contain other directories. Using directories to group subaccounts is optional - you can still create subaccounts directly under your global account.

Subaccounts let you structure a global account according to your project’s requirements with regards to members, authorizations, and quotas. Subaccounts in a global account are independent from each other. Each subaccount is associated with a region, which is the physical location where applications, data, or services are hosted. The region assigned to your subaccount doesn’t have to be directly related to your location. You could be located in the United States, for example, but operate your subaccount in Europe.

In your trial global account, a Cloud Foundry subaccount with an org and a space called dev is automatically created for you.

If you want to get a deeper understanding of the account structure, have a look at the documentation on the Account Model.

You can access your trial account cockpit at https://cockpit.hanatrial.ondemand.com/trial/.

There are two ways of navigating in the cockpit:

• using the left hand-side navigation,
• or using the breadcrumbs at the top of the page.

There are certain actions you can perform at each hierarchical level (global account, subaccount, space etc.). We will refer to the sum of these actions as a scope. For example, when you are in a global account, you can add global account members, create subaccounts, and add entitlements to subaccounts. They represent the global account scope.

This scope is reflected in both the left hand-side navigation and the breadcrumbs. This step helps you understand how to use both of them together to navigate through the cockpit in the most efficient way possible.

Left hand-side navigation

The left hand-side navigation changes depending on where you are in the cockpit. It reflects the actions possible in that scope.

Breadcrumbs

You may ask yourself: “If the left hand-side navigation changes depending on where you are in the cockpit, then how can you navigate back?” Simple! You use the breadcrumbs at the top.

The breadcrumbs coincide with the hierarchical path you’ve travelled to reach your current scope in the cockpit. For example, to reach an application in the Cloud Foundry environment, you will have to go to your global account, then to the subaccount, then to the space, and then finally to the application.

The last item in your breadcrumbs always represents the scope you find yourself in at that moment. To go back, simply follow the breadcrumbs to retrace your steps.

Let’s have a look at the following screenshot, taken from an application deployed in the Cloud Foundry dev space:

1. Trial Home: Here you can find your trial homepage.

2. Global account: This contains all your subaccounts and entitlements.

3. The third item represents your subaccount.

4. Afterwards, you have your space as the fourth item.

5. Here, you have your deployed application, which is the current scope.

6. This would be the instance of the deployed application.

To get an overview of the navigation in the cockpit, have a look at our guided tour: Get Familiar with the Cockpit. To start the guided tour, navigate to your global account scope and open SAP Companion.

The SAP BTP command line interface (btp CLI) is an alternative to the cockpit, for users who prefer working on the command line rather than GUIs. It consists of a client and a server. The client needs to be installed on your computer (make sure you update it regularly!) and it interacts with SAP BTP through a server. You connect to this CLI server at login.

The base call to enter on the command line is btp.

Here are some of the tasks you can use the CLI for:

• Creating subaccounts
• Managing entitlements of global accounts and subaccounts
• Managing users and their authorizations in global accounts and subaccounts
• Subscribing to applications

To find out more about the btp CLI, you can have a look at this tutorial: Get Started with the SAP BTP command line interface (btp CLI).