cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

When deploying an app in Build Apps with Cloud Foundry, do I use the Cloud Foundry runtime?

Amy_Astudillo
Explorer
0 Likes
1,316

We developed a web application using Build Apps. When deploying the application, we chose the Cloud Foundry environment and one Space, but we don't see the application in the SAP BTP Cockpit -> Cloud Foundry -> click on the chosen space -> Applications section. However, we see the application in the HTML5 Applications section.

My questions are:

  1. If I don't see the application in the SAP BTP Cockpit -> Cloud Foundry -> click on the chosen space -> Applications section, does this mean the app doesn't use the Cloud Foundry Runtime?

  2. If my application doesn't use the Cloud Foundry Runtime, is there any cost or limit for using the Cloud Foundry environment enabled with the Standard plan?

#BuildApps #CloudFoundry 

Accepted Solutions (1)

Accepted Solutions (1)

Jakub_Roguski
Product and Topic Expert
Product and Topic Expert

Hi Amy,

Actually applications build in the SAP Build Apps use Cloud Foundry environment for deployment, but not the one you subscribe as a separate service under tha name of SAP BTP Cloud Foundry Runtime. These apps are deployed in the Cloud Foundry runtime included in the SAP Build Apps subscription - this is the reason why you don't see these applications in your CF space.

SAP Build Apps is licensed as the base package, advanced users, standard users and capacity units.

When you subscribe to the base package, you get licensed for 25 advanced users, who are developers, admins and ordinary users AND for the capacity units. The capacity units are in fact translating to the network traffic, storage and projects. When you deploy your app, it consumes the capacity units of your base package of SAP Build Apps. When your apps grow, you have to add the capacity units to your SAP Build Apps subscription.

In the BTP Cockpit you see your applications as service instances - the ones with strange names, like buildapps-12345-html and buildapps-12345-dest.

Answering your questions:

1 - your apps consume CF runtime, but not the one you can subscribe to as SAP BTP CF Runtime - you don't need to subscribe SAP BTP CF Runtme to use SAP Build Apps.

2 - there is no cost associated with the SAP BTP Cloud Foundry Runtime service, but there is a cost of the SAP Build Apps capacity units - if you build more projects or big applications, consuming a lot of storage, network traffic or runtime space.

Amy_Astudillo
Explorer
0 Likes

Hi Jakub_Roguski,
Thank you for your answers. I have one more question: What service is activated when you enable the Cloud Foundry environment in the subaccount overview? At the time of deployment, we need to enable the Cloud Foundry environment and create a space, in this process we need to choose a plan "free" or "standard". I understand for your answers that the service is the Cloud Foundry Runtime and in the case of Build Apps, this plan isn't relevant, because the cost is based on the capacity units of the Build Apps plan.

Answers (1)

Answers (1)

Jakub_Roguski
Product and Topic Expert
Product and Topic Expert

When you enable Cloud Foundry in your subaccount, you enable the Cloud Foundry environment. This does not mean any consumption of the Cloud Foundry Runtime yet. When you use your subaccount for Build Apps only and deploy your Build Apps applications there, you will not see Cloud Foundry Runtime consumption in the usage statistics of your global account nor your subaccount and you will not be charged with Cloud Foundry Runtime cost. Even if you assign some amount of the CF Runtime to your space, it will still show 0 use of the Cloud Foundry Runtime and all the assigned amount will be shown as available for this and other spaces.

But if you use SAP Business Application Studio to write, build and deploy your application, then you need to assign some Cloud Foundry Runtime capacity to the space where you deploy your Pro-Code application and it will be used and you will be charged for it.