The number of runtime units required for a full-stack application depends on various factors, such as the performance, scalability, and availability of your application. Some of the factors that help you determine the number of runtime units are12:

• Number of users involved: This factor indicates how many concurrent users are expected to access your application at any given time. The more users you have, the more load your application will generate, and the more runtime units you will need to handle the requests and responses.
• Volume of data handled by your application: This factor indicates how much data your application needs to store, process, and transfer. The more data you have, the more memory and disk space your application will consume, and the more runtime units you will need to support the data operations.

You do not need to consider the following factors to determine the number of runtime units:

• Number of UI applications deployed: This factor indicates how many UI modules you have in your full-stack application. The number of UI applications does not directly affect the number of runtime units, as the UI applications are served by a web server that is independent of the runtime units. However, the number of UI applications may affect the complexity and size of your application, which may in turn affect the performance and scalability of your application.
• Number of services deployed: This factor indicates how many service modules you have in your full-stack application. The number of services does not directly affect the number of runtime units, as the services are deployed as separate applications that can be scaled independently. However, the number of services may affect the communication and integration between your application components, which may in turn affect the performance and availability of your application.

References:

• 1: SAP Business Application Studio - Trial Account Restrictions
• 2: Cloud Foundry Environment - SAP Help Portal

The file explorer in SAP Business Application Studio is a tool that allows you to view and edit files and folders in your workspace. A workspace is an entity that contains your project’s settings, debug configurations, and task configurations. You can use the file explorer to create, rename, delete, copy, paste, or move files and folders. You can also open files in the editor, preview them in the browser, or compare them with other files. The file explorer shows the files and folders of your current workspace, which can be either a multi-root workspace or a stand-alone folder. You can switch between different workspaces or open new ones from the file explorer. The file explorer does not allow you to view and edit APIs of a project, deploy a project, or share project files with other team members. These tasks require different tools or services in SAP Business Application Studio. References:

• File Explorer
• Working in SAP Business Application Studio

To run your application with live data, you need to do the following steps:

• In the target run configuration to run with, configure the data source as “Live Data”. This will enable your application to consume external OData services from their original sources, instead of using mock data from the sample data folder1.
• In the target run configuration to run with, configure the destination of OData service properly. For each OData service, you must specify the target configuration that refers to the external OData service: BTP destination name and an optional path to the service endpoint2.

You do not need to delete any existing run configurations that do not have “Live Data” chosen as data source, as they can be useful for testing your application with different scenarios. You also do not need to rename the target run configuration to run with, to make sure it contains “Run with Live Data” text, as the name of the run configuration does not affect its functionality.

References:

• 1: Previewing Your Application - SAP Learning
• 2: The fastest and easiest way to run full-stack applications in SAP Business Application Studio | SAP Blogs