orkungedik/SAP-basis-dataset huggingface dataset:
## 2.3.3.3 Kyma Functionalities
SAP BTP, Kyma runtime and open source project "Kyma" offer slightly different functionalities and install a different set of components.
For all functionalities that the Kyma environment offers, see the official project "Kyma" documentation .
Functionality Comparison
| Functionality                                                    | open source project "Kyma"   | SAP BTP, Kyma runtime                                                                                                       |
|------------------------------------------------------------------|------------------------------|-----------------------------------------------------------------------------------------------------------------------------|
| Service Level Agreements                                         |                             |                                                                                                                            |
| Managed Kubernetes                                               |                             |                                                                                                                            |
| Managed Kyma                                                     |                             |                                                                                                                            |
| Kyma CLI                                                         |                             | limited (SAP BTP, Kyma runtime sup- ports commands for serverless Func- tions, not the commands related to in- stallation.) |
| Centrally hosted Kyma dashboard                                  |                             |                                                                                                                            |
| System landscape management in SAP BTP cockpit                   |                             |                                                                                                                            |
| In-cluster system landscape manage- ment (Application Connector) |                             |                                                                                                                            |
## 2.3.3.4 Kyma Dashboard
Use Kyma dashboard to access various features and functionalities of SAP BTP, Kyma runtime.
Kyma dashboard is a web-based UI utilizing the React library and the SAP Fiori Horizon design system. Kyma uses Kyma dashboard as a central administration dashboard, which provides a graphical overview of your cluster and all its resources.
To access Kyma dashboard, enable Kyma in your subaccount. The link to the dashboard will be visible in the Kyma Environment section.
## Features
You can use Kyma dashboard to perform the following actions:
- Add, manage, and delete Kyma modules.
- Manage your namespaces.
- Manage your Kubernetes and Kyma resources.
- Generate access tokens based on service accounts and Kubernetes RoleBindings and ClusterRoleBindings, which regulate access using Role-based access control (RBAC).
- Have a quick look at the basic cluster condition.
<!-- image -->
## Related Information
Creating a Kyma Instance [page 3125]
Adding and Deleting a Kyma Module [page 3157]
Setting Your Module to the Unmanaged and Managed State [page 3159]
Using RBAC Authorization
## 2.3.3.4.1 Kyma Dashboard Command Palette
With the Kyma dashboard command palette feature, you can easily navigate through all your dashboard resources, such as workloads, deployments, and more. You can perform actions such as listing or accessing your namespaces, or preferences, or uploading YAML files.
## Features
You can use the command palette to perform the following actions:
- To access the command palette, press cmd+k on your keyboard or choose Quick Navigation .
- To see all navigation options and the resources' aliases, enter the question mark sign (?) . For example, if you want to see your namespaces, it's enough to type ns .
- To see the history of your resources, use the up or down arrow.
- To see the list of all resources available in the given namespace, enter the resource name and press the tab key.
<!-- image -->
<!-- image -->
<!-- image -->
- Switch contexts between your resources. For example, if you're viewing your available Pods in the default namespace, and you want to check the Pods in a different one, type ns/{NAME\_OF\_YOUR\_NAMESPACE} and choose the Switch Context option. It takes you to the list of Pods in the selected namespace.
<!-- image -->
## 2.3.3.5 Kyma CLI
Kyma CLI is an essential tool for application developers who want to get started quickly and efficiently with SAP BTP, Kyma runtime. Designed to streamline workflows, it simplifies complex tasks, enabling developers to deploy and manage applications easily.
##  Caution
The alpha group commands are still in development, which means their functions and API may be modified over time. We encourage you to explore them, but keep in mind that changes may occur.
## What is Kyma CLI
With a single command, you can push a simple application to a Kyma cluster. Kyma CLI builds the container image from source code or Dockerfile, pushes it to the in-cluster registry, and applies the necessary Kubernetes resources, eliminating the manual setup process and accelerating your development.
Kyma CLI provides a hands-on experience when interacting with Kyma's extensions to Kubernetes API, making it easier to explore, test, and fine-tune Kyma's custom resources directly from the command line.
Kyma CLI also provides a set of commands to manage Kyma modules efficiently. You can manage, deploy, and configure modules seamlessly. With the Kyma CLI module commands, you can list available and installed modules, and add or delete them. Modules can be deployed with the default or custom configuration.
## Features
Kyma CLI provides the following features:
- Simplified module management.
- Automated deployments.
- Simplified SAP BTP service instance bindings.
- Commands providing useful automation.
## Install Kyma CLI
- Using Homebrew:
- Using GitHub releases:
```
brew install kyma-cli
```
```
curl -sL "https://raw.githubusercontent.com/kyma-project/cli/refs/heads/main/ hack/install_cli_stable.sh" | sh kyma
```
## Related Information
Adding and Deleting a Kyma Module [page 3157]
Setting Your Module to the Unmanaged and Managed State [page 3159]
## 2.3.4  Neo Environment
The Neo environment lets you develop HTML5, Java, and SAP HANA extended application services (SAP HANA XS) applications. You can also use the UI Development Toolkit for HTML5 (SAPUI5) to develop rich user interfaces for modern web-based business applications.
See also:
- What Is SAP BTP, Neo Environment
- Development, Neo Environment
- Extensions, Neo Environment
- Administration and Operations, Neo Environment
- Security, Neo Environment
- Getting Support, Neo Environment
## Migration from the Neo to the Multi-Cloud Foundation
To learn more about why and how to migrate your scenarios on SAP BTP, see Migrating from the SAP BTP Neo Environment to the Multi-Cloud Foundation.
## 2.5.1  Commercial Models
SAP BTP offers two different commercial models for enterprise accounts.
- Consumption-based commercial model: Y our organization receives access to all current and future services that are eligible for this model. You have complete flexibility to turn services on and off and to switch between services as your business requires throughout the duration of your contract. This commercial model is available in the following flavors: SAP BTP Enterprise Agreement (SAP BTPEA), Cloud Platform Enterprise Agreement (CPEA), and Pay-As-You-Go for SAP BTP.
For more information, see What Is the Consumption-Based Commercial Model? [page 104]
- •
- Subscription-based commercial model: Y our organization subscribes only to the services that you plan to use. You can then use these services at a fixed cost, irrespective of consumption. For more information, see What Is the Subscription-Based Commercial Model? [page 107]
##  Note
You can use both commercial models, either in separate global accounts or in the same global account depending on your business needs. Contact your SAP account executive or sales representative for more information. Note however that you cannot mix more than one flavor of the consumption-based commercial model in the same global account.
For information about service availability, prices, and estimators, see https:/ /www.sap.com/products/ technology-platform/solutions.html and https:/ /www.sap.com/products/technology-platform/integrationsuite/pricing.html . Y ou can also view the service catalog via the SAP Discovery Center .
<!-- image -->
## 2.5.1.2 What Is the Subscription-Based Commercial Model?
Your organization receives a fixed price and period (typically a 1 to 3-year period) for access to your subscribed SAP BTP services.
Under this commercial agreement:
- You are entitled to use only the subscribed services.
- To access additional services, at an extra cost, you can modify your contract via your sales representative or account executive.
- You pay at a fixed cost, regardless of consumption of subscribed services.
- You pay in advance when the contract period starts.
- Your organization can renew the subscription at the end of the contract period.
For information about available services and pricing, see SAP Store .
You can also access the SAP BTP service catalog via the SAP Discovery Center to identify the availability of services by data center, and also to determine licensing model compatibility per service plan.
Note that some services can be subscribed based on a user metric or a resource metric. For example, a Portal service can be based on the number of site visits or user metrics. A resource-based metric is more common when dealing with a large number of users; for example, suppliers accessing a portal to interact with your organization. Since it isn't always possible to predict how many resources would be required upfront for a three-year period, you can increase your original order if resource usage exceeds your subscribed quota. Using SAP BTP cockpit, you can view resource consumption within your global account on a monthly basis.
In the subscription-based model, you also get access to bundles or packages that comprise several related services and apps. Most of the time, this works out to be more cost effective when compared to subscribing to individual SAP BTP services.
## Can an existing global account under a consumption-based contract be transformed to the subscription-based model?
You can change your existing contract from the consumption-based commercial model to a subscription license. Keep in mind that not all services that are eligible for the consumption-based model are compatible with the subscription-based model. We recommend that you contact your SAP account executive or sales representative to discuss feasibility and terms of transforming your contract.
Note that you can use both consumption and subscription-based commercial models either in separate global accounts or in the same global acccount depending on your business needs. Contact your SAP account executive or sales representative for more information.
## Related Information
What Is the Consumption-Based Commercial Model? [page 104]
Monitoring Usage and Consumption Costs in Your Global Account [page 2216]
View Subaccount Usage Analytics [page 2258]
Managing Global Accounts Using the Cockpit [page 2208]
Managing Directories Using the Cockpit [page 2241]
Managing Subaccounts Using the Cockpit [page 2249]
Managing Entitlements and Quotas Using the Cockpit [page 2261]
## 2.6 Account Model
Learn more about the different types of accounts on SAP BTP and how they relate to each other.
Accounts are structured according to global accounts, subaccounts, and directories.
To learn more about managing your account model, see Account Administration [page 2204].
## 2.6.1  Global Accounts
A global account is the realization of a contract you or your company has made with SAP.
A global account is used to manage subaccounts, members, entitlements and quotas. You receive entitlements and quotas to use platform resources per global account and then distribute the entitlements and quotas
to the subaccount for actual consumption. There are two types of commercial models for global accounts: consumption-based model and subscription-based model. See Commercial Models [page 103] .
Global accounts are region- and environment-independent. Within a global account, you manage all of your subaccounts, which in turn are specific to one region.
<!-- image -->
## 2.6.2  Subaccounts
In subaccounts , you deploy applications, use services, and manage your subscriptions. You can use them to manage members, authorizations, and entitlements.
A global account can contain one or more subaccounts in which you deploy applications, use services, and manage your subscriptions. Subaccounts in a global account are independent from each other. This is important to consider with respect to security, member management, data management, data migration, integration, and so on, when you plan your landscape and overall architecture.
<!-- image -->
Each subaccount is associated with a region, which is the physical location where applications, data, or services are hosted. The specific region is relevant when you deploy applications and access the SAP BTP cockpit using the corresponding cockpit URL. 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.
The entitlements and quotas that have been purchased for a global account have to be assigned to the individual subaccounts.
Global accounts and subaccounts are completely independent of user accounts. For more information, see User and Member Management [page 121].
Subaccounts, Cloud Foundry Orgs and Kyma Clusters
- When you enable the Cloud Foundry environment in one of your subaccounts, the system automatically creates a Cloud Foundry org for you. The subaccount and the org have a 1:1 relationship and the same navigation level in the cockpit (even though they may have different names). You can create spaces within that Cloud Foundry org. Spaces let you further break down your account model and use services and functions in the Cloud Foundry environment.
<!-- image -->
For more information about Cloud Foundry orgs and spaces, see the Cloud Foundry documentation at https:/ /docs.cloudfoundry.org/concepts/roles.html .
- When you enable the Kyma environment in one of your subaccounts, the system automatically creates a Kubernetes cluster equipped with the latest version of the open-source project "Kyma" for you. The subaccount and the Kyma cluster have a 1:1 relationship. You can create namespaces within that Kyma cluster. Namespaces let you further break down your account model and use services and functions in the Kyma environment. For more information, see the Kubernetes documentation at https:/ /kubernetes.io/ docs/concepts/overview/working-with-objects/namespaces/ .
<!-- image -->
## 2.6.3  Directories
With directories , you can organize and manage your subaccounts according to your technical and business needs.
A directory can contain directories and subaccounts to create a hierarchy. Using directories to group other directories and subaccounts is optional - you can still create subaccounts directly under your global account.
You can create a hierarchical structure that is up to 7 levels deep. The highest level of a given path is always the global account and the lowest is a subaccount, which means that you can have up to 5 levels of directories between the global account and the lowest level subaccount.
<!-- image -->
Directories enable you to:
- Group and filter directories and subaccounts
- Monitor usage and costs for contracts that use the consumption-based commercial model
Optionally, you can also enable the following features in your directories:
- Manage Entitlements: Enables the assignment of a quota for services and applications to the directory
- from the global account quota, for distribution to the directory's subaccounts. When you assign entitlements to a directory, you express the entitlements and maximum quota that can be distributed across its children subaccounts. You also have the option to choose the auto-assignment of a set amount of quota to all subaccounts created or moved to that directory. Subaccounts that are already in the directory when you select that option will not be auto-assigned quota.
##  Note
If you've enabled the Manage Entitlements feature for a given directory, you must first assign the necessary entitlements and maximum allowed quota from the global account to that directory. Then you can distribute this "reserved" quota to any of the directory's child subaccounts.
- Manage Authorizations: Enables authorization management for the directory. For example, it allows certain users to manage directory entitlements. You can only use this feature in combination with the Manage Entitlements feature.
## Related Information
Getting a Global Account [page 147]
Setting Up Your Account Model Managing Global Accounts Using the Cockpit [page 2208] Managing Directories Using the Cockpit [page 2241] Managing Subaccounts Using the Cockpit [page 2249] Working with Global Accounts, Directories, and Subaccounts Using the btp CLI [page 2434] Account Administration Using APIs of the SAP Cloud Management Service [page 2457] Manage the Account Explorer Hierarchy [page 2244]
## 2.6.4  Relationship Between Global Accounts, Subaccounts, and Directories
A global account can group together different directories and subaccounts that an administrator makes available to users. Administrators can assign the available entitlements and quotas of a global account to its different subaccounts and move it between subaccounts that belong to the same global account.
The hierarchical structure of global accounts, directories, and subaccounts lets you define an account model that accurately fits your business and development needs. For example, if you want to separate development, testing, and productive usage for different departments in your organization, you can create a directory for each department, and within each directory, you group subaccounts for development, testing, and production.
## 2.8 User and Member Management
On SAP BTP, user management takes place at all levels from global account to environment. There are different types of users, such as depending on their roles in the company.
## User Accounts
A user account corresponds to a particular user in an identity provider. The user is always stored in an external identity provider, such as a custom tenant of SAP Cloud Identity Services - Identity Authentication or the default identity provider.
##  Recommendation
We strongly recommend that you configure your custom tenant of SAP Cloud Identity Services as the identity provider and connect SAP Cloud Identity Services to your own corporate identity provider.
For more information, see Trust and Federation with Identity Providers [page 2280].
User accounts enable users to log on to SAP BTP, access subaccounts, and to use applications according to the permissions granted to them.
##  Note
A user name alone doesn't determine a concrete user account with associated authorizations, as you can have users with the same user name in different identity providers. Accessible data and allowed operations also depend on the identity provider. The concrete user is identified by the combination of user name and identity provider.
<!-- image -->
## Example
There are two users with the same user name, which is the email address here. The two users with different identity providers have different authorizations and can access different applications.
- julia.moore@acme.com from the custom identity provider has authorizations to access her favorite industrial applications. She needs the logon with the custom identity provider for her actual work.
- julia.moore@acme.com from the default identity provider has no authorizations.
Before diving into the different user and member management concepts, it's important to understand the difference between the two types of users we're referring to: platform users and business users .
<!-- image -->
For more information, see Platform Users [page 122] and Business Users [page 135].
## Related Information
Working with Users [page 2342]
Roles and Role Collections [page 2362]
Attributes [page 2365]
Trust and Federation with Identity Providers [page 2280]
## 2.8.2  Business Users
Business users use the applications that are deployed to SAP BTP. For example, the end users of SaaS apps or services, such as SAP Build Work Zone, or end users of your custom applications are business users.
Application developers (platform users) create and deploy application-specific security artifacts for business users, such as scopes. Administrators use these artifacts to assign roles, build role collections, and assign these role collections to business users or user groups. In this way, they control the users' permissions in the application.
For business users, there's a default identity provider [page 2335], too. We expect that you have your own identity provider.
##  Recommendation
We strongly recommend that you configure your custom tenant of SAP Cloud Identity Services as the identity provider and connect SAP Cloud Identity Services to your own corporate identity provider.
For more information, see Trust and Federation with Identity Providers [page 2280].
## User Management
User management refers to managing authentication and authorization for your business users.
To manage your business users:
1. Configure trust to an application identity provider in your subaccount.
2. Create shadow users in your subaccount for your business users in your identity provider. When a user accesses a resource, SAP BTP redirects the user to the identity provider for authentication.
3. You assign authorizations to shadow users in SAP BTP.
3. Assign role collections either directly to users or map them to user groups. The role collections were either delivered from the applications to which you subscribed or custom developed by your team.
To learn more about user management, see Security Administration: Managing Authentication and Authorization [page 2278].
## 2.9 Tools, Programming Models, Programming Languages, and APIs
SAP BTP provides various programming languages and tools for your development project.
## Tools [page 136]
SAP BTP includes many tools to help you develop and manage applications, and connect them to your on-premise systems.
## Programming Languages [page 139]
SAP BTP supports many different programming languages; the availability of each depends on the development environment you're using.
## Programming Models [page 139]
## Continuous Integration and Delivery (CI/CD) [page 140]
Configure and run predefined continuous integration and delivery (CI/CD) pipelines that automatically build, test, and deploy your code changes to speed up your development and delivery cycles.
## APIs [page 143]
Discover and consume APIs to manage, build, and extend the core capabilities of SAP BTP.
## Cloud Management Tools [page 144]
Cloud management tools represent the group of technologies designed for managing SAP BTP.
## Prerequisites and Restrictions [page 144]
Find a list of the product prerequisites and restrictions for SAP BTP.
## 2.9.2  Programming Languages
SAP BTP supports many different programming languages; the availability of each depends on the development environment you're using.
The following programming languages are available in the environments:
Supported Environments and Programming Languages
| Environment               | Programming Language                                                                                        |
|---------------------------|-------------------------------------------------------------------------------------------------------------|
| Cloud Foundry environment | Java [page 265] Node.js [page 365]                                                                          |
| ABAP environment          | ABAP [page 745]                                                                                             |
| Kyma environment          | Serverless Functions: Node.js and Python [page 2022] Microservices: Any cross-platform programming language |
## 2.9.3  Programming Models
## ABAP Cloud
ABAP Cloud reflects the modern way to develop ABAP. It allows you to build lifecycle-stable and cloud-ready business applications, services, and extensions.
ABAP Cloud provides tools and techniques that ensure cloud qualities, promotes new technologies, contains a cloud-optimized subset of the ABAP language, and makes upgrade cycles easier by a clear separation between custom code and SAP code by only using released APIs and objects. See ABAP Cloud in SAP BTP Developer's Guide.
## SAP Cloud Application Programming Model (CAP)
The SAP Cloud Application Programming Model (CAP) is a framework of languages, libraries, and tools for building enterprise-grade services and applications. It supports Java (with Spring Boot), JavaScript, and TypeScript (with Node.js), which are some of the most widely adopted languages. CAP guides developers along a path of proven best practices and a great wealth of out-of-the-box solutions to recurring tasks.
CAP-based projects benefit from a primary focus on the domain. Instead of delving into overly technical disciplines, CAP focuses on accelerated development and safeguarding investments in a world of rapidly changing cloud technologies.
Here are some of the benefits that come with the SAP Cloud Application Programming Model (CAP):
- Built-in best practices
- Support for Visual Studio Code and SAP Business Application Studio tools
- Safeguarded application development investments
- No runtimes lock-in
- Reuse and integration of SAP BTP application services
- Latest UX and themes
See SAP Cloud Application Programming Model (CAP) in SAP BTP Developer's Guide.
## 2.9.5  APIs
Discover and consume APIs to manage, build, and extend the core capabilities of SAP BTP.
An Application Programming Interface or API is an interface provided by an application for interacting with other applications . APIs specify how software programs are able to exchange information with each other, even if designed and run by different organizations. They facilitate interaction by selectively exposing certain functionality, allowing different apps, websites, and devices to communicate effectively with each other. More importantly, APIs enable businesses to reach beyond regular business channels and share data, content, and services directly to both B2B (business to business) and B2C (business to consumer) clients, making UI development easy.
## API Offerings on SAP BTP
SAP BTP enables you to consume APIs and publish your own ones through the following offerings:
<!-- image -->
| Offering                                | Description                                                                                                                                                                                                                                                                      |
|-----------------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| SAP BTP on SAP Business Accelerator Hub | The SAP Business Accelerator Hub provides you with one central repository for browsing and accessing APIs from SAP and selected partners. Test APIs and try out mock data in your systems. It is also the official place where REST and OData REST API references are published. |
| Offering                                                                                      | Description                                                                                                                                |
|-----------------------------------------------------------------------------------------------|--------------------------------------------------------------------------------------------------------------------------------------------|
| API Management Capability within SAP Integration Suite                                        | With the API Management capability, you can build, manage, publish, and monetize your own APIs within one secure and scalable environment. |
| Software Development Kits (SDKs) For an overview of the available SDKs, see Tools [page 136]. | The SDKs available for SAP BTP offer APIs to, for example, accelerate enterprise app development.                                          |
## Related Information
SAP API Style Guide
## 2.9.6  Cloud Management Tools
Cloud management tools represent the group of technologies designed for managing SAP BTP.
## Related Information
Tools [page 136]
## 2.9.7  Prerequisites and Restrictions
Find a list of the product prerequisites and restrictions for SAP BTP.
## General Constraints
- For information on constraints and default settings to consider when you deploy an application in the Cloud Foundry environment, see http:/ /docs.cloudfoundry.org/devguide/deploy-apps/large-appdeploy.html#limits\_table .
- SAP BTP exposes applications only via HTTPS. For security reasons, applications can't be accessed via HTTP.
## SAP BTP Tools
- SAP BTP Tools for Java and SDK have been tested with Java 7, and Java 8.
- SAP BTP Tools for Java and SDK run in many operating environments with Java 7, and Java 8 that are supported by Eclipse. However, SAP doesn't systematically test all platforms.
- SAP BTP Tools for Java must be installed on Eclipse IDE for Java EE developers.
For the platform development tools, SDK, Cloud connector, and SAP JVM, see https:/ / tools.hana.ondemand.com/#cloud .
## Browser Support
For a list of supported browsers for the SAP BTP cockpit, see Feature Scope Description.
For a list of supported browsers for developing SAPUI5 applications, see Browser and Platform Support.
To find out the browser support for a specific service, refer to the corresponding feature scope description.
For security reasons, SAP BTP doesn't support TLS1.1 and older, SSL 3.0 and older, and RC4-based cipher suites. Make sure that your browser supports at least TLS1.2 and modern ciphers (for example, AES).
## 3 Getting Started
Once you're familiar with the basic concepts of SAP BTP, you can start your first workflows or check out further resources that help you get started quickly.
## Onboarding Guides
The SAP BTP Administrator's Guide helps you plan your development projects on SAP BTP from onboarding to SAP Cloud Identity Services, through setting up the correct organizational structure, to creating an account and security model, to developing and operating applications.
The SAP BTP Developer's Guide helps you define the correct methodologies and tools for your development project.
## Getting Started Workflows
Learn how to get a global account and get started with a trial or an enterprise account on SAP BTP. A trial account lets you try out SAP BTP for free, and within an enterprise account, you can use so-called free tier service plans for free. See Trial Accounts and Free Tier [page 99].
Depending on your use case, follow the appropriate workflow:
- Getting a Global Account [page 147]
- Getting Started in the Cloud Foundry Environment [page 150]
- Getting Started in the ABAP Environment [page 168]
- Getting Started in the Kyma Environment [page 227]
## Additional Resources
The SAP Developer Center provides further resources to get you started:
- SAP Discovery Center
- SAP BTP in SAP Developer Center
- Start Developing on SAP BTP Tutorials
## Related Information
SAP BTP Administrator's Guide
## 3.1 Getting a Global Account
SAP BTP offers two types of global accounts: Trial accounts (completely free of charge) and enterprise accounts. Within an enterprise account, you can use both free and paid plans.
A global account is the realization of a contract you or your company has made with SAP. A global account is used to manage subaccounts, members, entitlements and quotas. You receive entitlements and quotas to use platform resources per global account and then distribute the entitlements and quotas to the subaccount for actual consumption. There are two types of commercial models for global accounts: consumption-based model and subscription-based model. See Commercial Models [page 103]
- Trial Accounts and Free Tier [page 99]
- Enterprise Accounts [page 101]
- Try Out SAP BTP for Free [page 147]
- Get an Enterprise Account [page 148]
## 3.1.1  Try Out SAP BTP for Free
There are two ways to try out SAP BTP services and applications for free.
## Context
A free trial account is intended for individuals, for example students, who want to explore SAP BTP for free. It is an isolated account and subaccount, with preallocated service entitlements that can be used for a limited number of days.
Free tier is not an account type, but it's a set of free services that can be used within an enterprise account.
To learn which is best for your needs, see the Set Up an SAP BTP Account for Tutorials group in the SAP Developer Center.
## 3.1.2  Get an Enterprise Account
To use an enterprise account, you can either purchase a customer account, join the partner program to purchase a partner account, or self-register for an enterprise account to try out free tier service plans.
For more information about the scope of our enterprise offering, see Enterprise Accounts [page 101]. For more information about free tier within an enterprise account, see Trial Accounts and Free Tier [page 99] and Using Free Service Plans [page 108].
## Related Information
Get an Account on SAP BTP to Try Out Free Tier Service Plans
## 3.1.2.1 Sign up for a Customer Account
A customer account is an enterprise account that allows you to host productive, business-critical applications with 24x7 support.
When you want to purchase a customer account, you can select from a set of predefined packages. For information about service availability, prices, and estimators, seehttps:/ /www.sap.com/products/technologyplatform/pricing.html . Y ou can also view the service catalog via the SAP Discovery Center . Contact us on SAP BTP or via an SAP sales representative.
## Free Tier
If you want to try out services for free, with the option of easily upgrading them later, you can get an enterprise account and use free tier service plans only. See Get an Account on SAP BTP to Try Out Free Tier Service Plans . When you sign up for a global account to try out free tier service plans, you need to select either an existing global account of your company, or create a new global account. If you choose an existing global account, make sure to contact the global account admin of this global account, as they'll receive the communication emails. In this case, we recommend to have them add you as Global Account Administrator. See Assign Users to Role Collections [page 2355] and SAP BTP Onboarding Resource Center .
You can upgrade and refine your resources later on. You can also contact your SAP sales representative and opt for a configuration, tailored to your needs.
## Onboarding
After you have purchased a new customer account, you will receive an email confirming the provisioning of resources from the platform services team and a second email with the URL and login ID to obtain access. Note, only the person who receives the access email has initial access to SAP BTP.
If you chose an add-on to an existing global account, the initial access email will not be sent to you. You will need to contact the Global Account Administrator from the initial BTP order. If you're unsure who this person is, please contact your SAP Sales representative. If you need to add a new global admin because the person with initial access is no longer available to grant you access, then you can contact the SAP Support Portal, by creating a ticket at component BC-NEO-CIS-OPS.
##  Tip
Check out the Live Onboarding Webinars .
## Getting a Customer Account in China
If you are located in China and want to buy a global account on SAP BTP, you need to contact an SAP sales representative: https:/ /www.sap.cn/registration/contact.html .
## Related Information
Commercial Models [page 103]
Using Free Service Plans [page 108] Access the Cockpit [page 2206]
## 3.1.2.2 Join the Partner Program
A partner account is an enterprise account that enables you to build applications and to sell them to your customers.
To become a partner, you need to fill in an application form and then sign your partner contract. You will be assigned to a partner account with the respective resources. To apply for the partner program, visit https:/ /partneredge.sap.com/content/partnerregistration/en\_us/registration.html? partnertype=BLD&amp;engagement=0002&amp;build=1 . Y ou will receive a welcome mail with further information afterwards.
General information about the partner program is available onhttps:/ /www.sap.com/partners/partnerprogram.html .
## Next Steps
- Getting Started in the Cloud Foundry Environment [page 150]
- Getting Started in the ABAP Environment [page 168]
- Getting Started in the Kyma Environment [page 227]
## 3.2 Getting Started in the Cloud Foundry Environment
Get onboarded in the Cloud Foundry environment of SAP BTP. Follow the workflows for trial or customer accounts or subscribe to business applications.
Getting Started with a Trial Account in the Cloud Foundry Environment [page 150]
Quickly get started with a trial account.
Getting Started with an Enterprise Account in the Cloud Foundry Environment [page 161]
Quickly get started with an enterprise account in the Cloud Foundry Environment.
## 3.2.1  Getting Started with a Trial Account in the Cloud Foundry Environment
Quickly get started with a trial account.
## 1. Getting a Global Account
<!-- image -->
- Try Out SAP BTP for Free [page 147]
- Trial Accounts and Free Tier [page 99]
Before you begin, sign up for a free trial account. See Get a Free Trial Account [page 147]. For more information about the scope of our trial offering, see Trial Accounts and Free Tier [page 99].
If you want to familiarize yourself with the Cloud Foundry environment, see Cloud Foundry Environment [page 57].
## 2. Setting Up Your Account Model
<!-- image -->
- Navigate to Orgs and Spaces [page 2512]
- Create a Subaccount [page 2249]
- Download and Install the Cloud Foundry Command Line Interface [page 2533]
- Log On to the Cloud Foundry Environment Using the Cloud Foundry Command Line Interface [page 2534]
- Create Spaces [page 2520]
- Account Model [page 111]
1. When you register for a trial account, a subaccount and a space are created for you. You can create additional subaccounts and spaces, thereby further breaking down your account model and structuring it according to your development scenario, but first it's important you understand how to navigate to your accounts and spaces using the SAP BTP cockpit. See Navigate to Orgs and Spaces [page 2512].
2. If you like, create further subaccounts. See Create a Subaccount [page 2249]. You can also download and use the CLI forSAP BTP to create new subaccounts. See Download and Start Using the btp CLI Client [page 2402] and Working with Global Accounts, Directories, and Subaccounts Using the btp CLI [page 2434].
3. If you haven't done so already, now is a good time to download and install the Cloud Foundry Command Line Interface (cf CLI). This tool allows you to administer and configure your environment,enable services, and deploy applications. See Download and Install the Cloud Foundry Command Line Interface [page 2533]. But don't worry, you can also perform all the necessary task using the SAP BTP cockpit, which you don't need to install.
4. If you'd like to use the cf CLI, log on to your environment. See Log On to the Cloud Foundry Environment Using the Cloud Foundry Command Line Interface [page 2534].
5. If you like, create further spaces. See Create Spaces [page 2520]. If you want to learn more about subaccounts, orgs, and spaces, and how they relate to each other, see Account Model [page 111].
## 3. Configuring Your Environment
<!-- image -->
- Add Org Members [page 2516]
- Add Space Members [page 2523]
- Configure Entitlements and Quotas for Subaccounts [page 2269]
- Create Space Quotas [page 2528]
- Create Space Quota Plans Using the Cloud Foundry Command Line Interface [page 2575]
- User and Member Management [page 121]
- Entitlements and Quotas [page 117]
1. Now that you've set up your account model, it's time to think about member management. You can add members at different levels. For example, you can add members at the org level. See Add Org Members [page 2516]. For more information about the roles that are available on the different levels, see User and Member Management [page 121].
2. You can also add members at the space level. See Add Space Members [page 2523].
3. In a trial account, quotas are automatically assigned to your subaccounts, but you can change that assignment. See Configure Entitlements and Quotas for Subaccounts [page 2269]. To learn more about entitlements and quotas, see Entitlements and Quotas [page 117].
4. You can also assign quotas to different spaces within a subaccount. To do so, first create a space quota plan. See Create Space Quotas [page 2528] or Create Space Quota Plans Using the Cloud Foundry Command Line Interface [page 2575].
5. Then assign the quota plan to your space. See Assign Space Quotas to Spaces [page 2530] or Assign Quota Plans to Spaces Using the Cloud Foundry Command Line Interface [page 2576].
## 4. Developing and Deploying Applications
<!-- image -->
- Development [page 235]
- Deploy Business Applications in the Cloud Foundry Environment [page 742]
- Creating Service Instances [page 254]
- Binding Service Instances to Applications [page 257]
- Creating Service Keys [page 259]
- About Services [page 253]
- Creating User-Provided Service Instances [page 256]
1. Develop your application. Check out the Developer Guide for tutorials and more information. See Development [page 235].
2. Deploy your application. See Deploy Business Applications in the Cloud Foundry Environment [page 742].
3. Integrate your application with a service. To do so, first create a service instance. See Creating Service Instances [page 254].
4. Bind the service instance to your application. See Binding Service Instances to Applications [page 257].
5. Alternatively, you can also create and use service keys. See Creating Service Keys [page 259]. For more information on using services and creating service keys, see About Services [page 253].
6. You can also create instances of user-provided services. See Creating User-Provided Service Instances [page 256].
##  Tip
Also check out the tutorial Create Your First App on Cloud Foundry to see how you can deploy a pre-bundled set of artifacts using the SAP BTP cockpit, access the app from your web browser, and create an instance of a service available on Cloud Foundry and bind it to your app.
## Related Information
Cloud Foundry Environment [page 57] Trial Accounts and Free Tier [page 99] Account Model [page 111] Entitlements and Quotas [page 117] User and Member Management [page 121] About Services [page 253]
## 3.2.1.1 Setting Up Your Trial Account
Your trial account is set up automatically, so that you can start using it right away. However, if one or more of the automatic steps fail, you can also finalize the setup manually, by following the steps below.
## 3.2.1.1.1 Create Your Trial Subaccount
The first thing that is needed in the setup of your trial account is the creation of a subaccount. If this step was successful in the SAP BTP cockpit, you can directly skip to the next section.
## Procedure
1. Navigate into your global account by choosing Enter Your Trial Account .
2. Choose New Subaccount .
3. Configure it as follows:
| Field                           | Input                                                                                                                                                                                                                      |
|---------------------------------|----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
| Display Name                    | trial                                                                                                                                                                                                                      |
| Description                     | (Optional) Any text that describes your subaccount                                                                                                                                                                         |
| Provider                        | Desired infrastructure provider                                                                                                                                                                                            |
| Region                          | Desired region                                                                                                                                                                                                             |
| Subdomain                       | <your_id>trial Example: P0123456789trial                                                                                                                                                                                   |
| [Advanced] Enable beta features | (Optional) Enables the use of beta services and applica- tions.                                                                                                                                                            |
| [Advanced] Labels               | (Optional) You can assign labels to help identify and or- ganize the subaccounts in your global account. For exam- ple, you can filter subaccounts by custom property in the Account Explorer page. See Labels [page 115]. |
## Results
You have successfully set up your trial subaccount.
## 3.2.1.1.2 Create Your Trial Org and Configure Entitlements
Once you have a subaccount (whether it was created automatically or you followed the steps described above), you need an org and entitlements.
## Procedure
1. Navigate to your subaccount by choosing its tile.
2. Choose Enable Cloud Foundry to create your org.
3. Once your org is created, choose Entitlements from the left hand-side navigation.
4. Choose Configure Entitlements to enter edit mode.
5. Choose Add Service Plans and select all the service plans available for your subaccount.
##  Note
To select a service plan, choose a service from the left and tick all the service plans that appear on the right. Do that for all services.
6. Once you've added all the service plans, you see them all in a table. Before you choose Save, for all the plans with numerical quota, choose  to increase the amount to the maximum (until the icon becomes disabled).
7. Finally, choose Save to save all your changes and exit edit mode.
## Results
You now have an org and all the entitlements for your subaccount. The last thing you need is a space where you can use the services you've configured entitlements for and deploy applications.
## 3.2.1.1.3 Create Your Trial Space
## Procedure
1. In your trial subaccount, navigate to Cloud Foundry Spaces using the left hand-side navigation.
2. Choose Create Space and name it dev .
3. Choose Create .
## Results
You now have your trial set up all done and ready to go.
To get some guidance on how you can get started, navigate back to your Trial Home by choosing the first item in your breadcrumbs at the top. There, you can find several guided tours to walk you through the basics of SAP Business Technology Platform and the cockpit, as well as some more complex starter scenarios.
## 3.2.2  Getting Started with an Enterprise Account in the Cloud Foundry Environment
Quickly get started with an enterprise account in the Cloud Foundry Environment.
This topic focuses on how to get started with a customer or partner account using the SAP BTP cockpit. However, you can also perform these tasks using the CLI. See Setting Up a Global Account via the Command Line [page 165].