SAP Cloud Platform Backend service: Tutorial [0.4]: Configuration of BETA-Subaccount
This blog is part of a series of tutorials explaining the usage of SAP Cloud Platform Backend service in detail.
The following description is only required as long as the SAP Cloud Platform Backend service is in BETA mode.
Because during this period, you need to create a separate subaccount, in order to enable it to use the BETA features.
Creating a BETA-enabled subaccount is described here. But the description of enabling Cloud Foundry is missing there.
If you wish to call your Backend service APIs from external application, you need Cloud Foundry, a space and service instances.
If you run 2 subaccounts in your Trial account, you might run into problems, due to lack of quota.
However, there’s one solution: follow my description below;-)
Below description is divided into 2 steps:
BTW, this description is meant for users of the free Trial account, where some limited free quota is available
Step 1: Enable Cloud Foundry
When you created a new subaccount for enabling and using BETA features, as described in this blog, it wasn’t required to enable Cloud Foundry.
So, if you haven’t done already, now it is the right moment to go to your BETA-subaccount and click on “Enable Cloud Foundry”:
A little popup is displayed, asking for a name of the organization, which will be created for Cloud Foundry.
You can leave the proposed default name and click “Create”
Then wait short time while processing
After successful creation, click on “Spaces” in the left navigation pane.
Then click on “New Space”
In the popup, enter a name of your choice, then press “Save”
A tile with the new Space is displayed in the “Spaces” screen.
First you’ll be happy – it looks so green – but after having a closer look….
You realize that the nice new space is (almost) useless, because it doesn’t have any quota for memory, so you cannot deploy an application.
The sceenshot above shows that there is no memory and no routing allowed, but is it possible to create 10 service instances.
If you only need e.g. an xsuaa instance, then you can skip the following description of quota assignment
Step 2: Assign quota
What do we have to do?
In fact, there is not much, but enough quota in a public Trial account. But initially it was all assigned to the one trial subaccount.
When we created a second subaccount, it was not automatically provided with quota, this has to be done by admin, after careful consideration etc
OK, we’re admins and have considered enough.
Go to your global account.
If it is a Trial account, it usually starts with P and ends with trial
Once you’ve found it, click on “Entitlements” on the left navigation pane
Here in the “Entitlements” screen, you can distribute the available quota among the existing subaccounts
Press “Edit” on the top of the page
Scroll down to “Application Runtime”.
Here you can assign memory for applications to your new subaccount.
First, click on the little “minus” next to the trial subaccount account, to reduce the assigned memory
Afterwards, you want to increase the memory assignment of your new beta-enabled subaccount, but there seems to be a bug, such that the little “plus” doesn’t get enabled
To workaround it, scroll up to the top of the page and press “Save” to save the memory reduction.
Then press “Edit” again and scroll down to “Application Runtime”.
Now the little “+” of your second subaccount is enabled and you can increase the memory of your second subaccount.
Now, if required, you may continue distributing the quota of other assets.
At the end, scroll up and press “Save”
Now you can go to your Beta-Subaccount.
If you have more than one Space, then you need to do an additional step:
Create “Quota plans” and distribute the quota among the spaces.
If you have only one space, then you don’t need to do anything: it anyways gets all the available quota.
Finally, you can check your space, which looks different now:
The screenshot shows that memory and routes are available.
So we’re done.
In the previous preparation blog, we had created a new subaccount in our global Trial account.
And we started using SAP Cloud Platform Backend service.
In this blog, we’ve enabled Cloud Foundry for this new subaccount.
Furthermore,we’ve assigned quota to this new subaccount.
Now it is possible to properly use that new subaccount.