---
title: Use a Local Launch Page
description: This tutorial shows you how to add a launch page for local testing.
keywords: cap
parser: v2
auto_validation: true
time: 10
tags: [ tutorial>beginner, software-product-function>sap-cloud-application-programming-model, programming-tool>node-js, programming-tool>java, software-product>sap-business-technology-platform, software-product>sap-fiori]
primary_tag: software-product-function>sap-cloud-application-programming-model
author_name: Svetoslav Pandeliev
author_profile: https://github.com/slavipande
slug: use-local-launch-page
canonical_url: https://developers.sap.com/tutorials/use-local-launch-page
---
## You will learn
- How to add a launch page for local testing.
## Prerequisites
You've added business logic to your application. Follow the steps in the [Add Custom Logic](add-custom-logic) tutorial that is part of the [Develop a Full-Stack CAP Application Following SAP BTP Developer’s Guide](https://developers.sap.com/group.cap-application-full-stack.html) tutorial group.
> **OUT OF MAINTENANCE**
>
> This tutorial is no longer maintained. For an up-to-date version and support with any issues, refer to the [Develop a Full-Stack CAP Application Following the SAP BTP Developer's Guide](https://discovery-center.cloud.sap/missiondetail/4327/4608/) mission in the [SAP Discovery Center](https://discovery-center.cloud.sap/).
### Overview
You have already generated the **Incident Management** application and can start it in the browser from SAP Business Application Studio. However, you can also add a launch page for local testing. This page looks like a real site, but is just a local copy of the otherwise centrally managed SAP Build Work Zone, standard edition site and comes with a limited version of its functionality. There's no option to add or remove applications via configuration, user roles aren't considered, and user personalization is also not included. If you want these and other SAP Build Work Zone, standard edition functionalities included, you have to set them up for your project. Find out how to set these funtionalities in [Integrate Your Application with SAP Build Work Zone, Standard Edition](integrate-with-work-zone). You stick to the launch page for this tutorial though.
In the current implementation, you can open the **Incident Management** application via the `app/incidents/webapp/index.html` file and there's no launch page. If you now create a second application using the SAP Fiori application generator within your project, it's generated in the same way, again with its own `index.html` file. Instead, you can use a launch page for all the applications. You can add a launch page by creating an HTML file that uses the built-in SAPUI5 shell in the **app** folder.
### Implement a local launch page
1. In SAP Business Application Studio, go to your **IncidentManagement** dev space.
> Make sure the **IncidentManagement** dev space is in status **RUNNING**.
2. Navigate to the **app** folder of the **INCIDENT-MANAGEMENT** application and create a new **launchpage.html** file.
> Make sure to place the new **launchpage.html** file in the **app** folder and not in any subfolders.
3. Copy the following content to the **launchpage.html** file:
```html
```
3. Make sure that the SAP Fiori application is running.
3. Go to the tab of the opened SAP Fiori application in your browser and replace **/ns.incidents/index.html?sap-ui-xx-viewCache=false** with **/launchpage.html#Shell-home** in the URL.
> You now see a tile of the **Incident Management** application on the launch page.
### Check the launchpage.html file
Let's have a look at the **launchpage.html** file and the configuration inside. In the first script, you see:
```html
```
There's a single application in the launch page with a URL that points to it. There are other properties configured here like the title and description. Similarly, another application can be added to the launch page by adding an entry in this file.
> Why is the file named **launchpage.html** instead of **index.html**?
You're using the name **launchpage.html** because the CAP server by default looks for an **index.html** file in the **app** folder. If the CAP server finds such a file, it replaces the default page that also contains the links to the services with the **index.html** in the folder. While this approach makes sense in many cases, for development purposes we recommend keeping the default page generated by CDS and using a different name for the index file of the launch page.