Create a Cloud Foundry Subaccount manually

Creating a subaccount can be one of the easiest tasks. However, one has to keep in mind the Hosting region, Naming conventions, Account Model, Labels, Authorizations, etc.

Before you start creating your subaccounts, we recommend understanding the basic details in this blog - SAP BTP Cockpit – Global Account Technical Overview - section 3 and if you want to know about the account models and directories, you can read - How to Determine your Account Model.

Procedure

Now let us take a look at the details on creating the Subaccount manually.

1. From your global account home page, Click on the “Create” drop-down button and choose Subaccount.

2. Specify a display name.

3. (Optional) Specify a description.

4. Select the region, environment, and infrastructure provider of the new subaccount.

   Additional fields appear according to the selected environment. Select settings as required.

   Note: In a subaccount in the Cloud Foundry environment, the subdomain that you specify can be any string. The subdomain can contain only lowercase letters and digits, and hyphens (not allowed at the beginning or at the end) and must be unique within the Cloud Foundry environment of SAP BTP.

5. (Optional) To use beta features in the subaccount, select “Enable beta features”.

6. Save your changes.

Result

A new tile appears on the Global Account page with the subaccount details.

For more information see SAP Help Portal, Create a Subaccounts.

After you have created your subaccount, you need to enable its runtimes. Runtimes can be either Cloud Foundry, Kyma, or ABAP.

This tutorial enables Cloud Foundry runtime. Guides for the other runtimes can be found in dedicated tutorials or missions.

Procedure

1. Open your BTP Cockpit.

2. Select the subaccount, you just created.

3. Select Cloud Foundry Environment in the tab navigation.

4. Check the button “Enable Cloud Foundry”.

   

5. A form opens. Keep the preconfigured values or change the following entries:

   • Plan: One of the Service Plans you are entitled to (e.g. standard, or free)
   • Landscape: Some Regions have more than one Landscape.
   • Instance Name: Consider a CLI-friendly name
   • Org Name: Each Cloud Foundry environment has exactly one Organization.

   

6. Choose Create.

7. The Cloud Foundry Environment will be created.

   Note your API Endpoint. Copy and call it in a browser. You will need it in other tutorials.

   Note: You still have no Cloud Foundry “Spaces”. You will need at least one.

After you have enabled Cloud Foundry runtime, you can create a space. There is no limit to how many spaces you can have within one org.

Spaces can be used to separate a DEV from a TEST or PROD environment. A typical setup for a BTP environment is the Staged Development Environment with DEV, TEST, and PROD landscape for each project.

For more information, see SAP Help - Setting Up Your Account Model.

Procedure

1. In your subaccount overview page, choose “Cloud Foundry Environment” again.

2. Press the button Create Space.

3. A popup form opens.

4. Provide a name (choose “dev” if you have no name).

5. Keep the space roles as preconfigured and choose Create.

6. Congratulations you now have a configured Cloud Foundry Environment.

For more information, see Managing Spaces on the SAP Help Portal.

The default SAP BTP identity provider and application identity provider of SAP BTP is the SAP ID service. Trust that the SAP ID service in your subaccount is pre-configured by default, so you can start using it without further configuration.

For more information about SAP ID Service see SAP Help Portal.

For more information, or on how to establish trust with your custom identity provider, start the Discovery Center mission Establish single sign-on to your cloud solutions.

Users

If you want to grant authorizations to users from the SAP ID service in your subaccount, you must ensure that they have a user account in the SAP ID service.

For more information see Working with Users.

Roles and Role Collections

Roles determine which functions in the cockpit users can view and access, and which actions they can initiate.

SAP BTP offers predefined “Role Collections”, which are sufficient for this mission.

For more information see Working with Role Collections).

Procedure

1. Open the SAP BTP cockpit.

2. Choose the subaccount to which you’d like to add users.

3. In the navigation pane, choose “Security” and then “Users”.

4. All members currently assigned to the subaccount are shown in a list.

5. Choose Create.

6. Enter the user ID and e-mail address.

7. Choose the identity provider where the user is stored. The dropdown list displays the identity providers configured in your subaccount’s trust configuration.

8. Save your changes.

You can now proceed to assign role collections to the new user. Browse the list of available Role Collections by clicking on “Role Collections”.

If you want to delete your subaccount, e.g. because it was a test or sandbox subaccount, you can delete unused subaccounts.

Note: Only subaccount administrators can remove such content from a subaccount.

Procedure

1. Login to SAP BTP Cockpit.
2. Choose the subaccount that you want to delete.
3. The subaccount doesn’t contain any active subscriptions, service instances, brokers, or platforms.
4. Choose Delete Subaccount and confirm the operation.