sap-tutorials
diff --git a/‎tutorials/hana-cloud-cap-create-project/cap_project_details.png‎
73.9 KB b/‎tutorials/hana-cloud-cap-create-project/cap_project_details.png‎
73.9 KB
diff --git a/‎tutorials/hana-cloud-cap-create-project/hana-cloud-cap-create-project.md‎
Lines changed: 39 additions & 42 deletions b/‎tutorials/hana-cloud-cap-create-project/hana-cloud-cap-create-project.md‎
Lines changed: 39 additions & 42 deletions
@@ -9,12 +9,15 @@ primary_tag: products>sap-hana-cloud
 ---
 
 ## Prerequisites
+
 - This tutorial is designed for [SAP HANA Cloud](https://community.sap.com/topics/hana). It is not designed for SAP HANA on premise or SAP HANA, express edition.
 - You have created a BTP, SAP HANA Cloud instance. [Deploy SAP HANA Cloud](hana-cloud-deploying)
 - You have setup SAP Business Application Studio for development: [Set Up SAP Business Application Studio for Development](appstudio-onboarding)
 
 ## Details
+
 ### You will learn
+
 - How to create an application with the wizard for the [SAP Cloud Application Programming model](https://cap.cloud.sap/docs/)
 - How to use the local Git repository for development/testing purposes
 
@@ -28,40 +31,39 @@ Dev spaces are like isolated virtual machines in the cloud that can be quickly s
 
 In this step we will create a new Dev Space configured for SAP Cloud Application Programming Model (CAP) development. If you already have a dev space configured for CAP and HANA development, you can skip this step as each dev space can hold multiple projects.
 
-
 1. Go to your SAP Business Technology Platform subaccount and click the **Services -> Instances and Subscriptions** option.
 
     !![Subscriptions](BTP_Subscriptions.png)
 
-3. Locate the **SAP Business Application Studio** entry and click **Go to Application**
+1. Locate the **SAP Business Application Studio** entry and click **Go to Application**
 
     !![Go To Application](go_to_application.png)
 
-4. Choose **Create Dev Space**. Please NOTE: In the SAP BTP trial and free tier you are limited to only two Dev Spaces and only one can be active at a time. If you have performed other tutorials, you might already have reached your maximum. In that case you might have to delete one of the other dev spaces in order to continue with this tutorial.
+1. Choose **Create Dev Space**. Please NOTE: In the SAP BTP trial and free tier you are limited to only two Dev Spaces and only one can be active at a time. If you have performed other tutorials, you might already have reached your maximum. In that case you might have to delete one of the other dev spaces in order to continue with this tutorial.
 
     !![Create Dev Space](AppStudio Dev Space Manager_.png)
 
-3. Enter any name you wish for your dev space name and choose **Full Stack Cloud Application** as the kind of application you are creating.
+1. Enter any name you wish for your dev space name and choose **Full Stack Cloud Application** as the kind of application you are creating.
 
     !![Create Dev Space](create_cap_dev_space.png)
 
-4. The Dev space will automatically be configured with the most common tools you need for the type of application you choose. However you can also choose additional, optional extensions. Since you want to combine CAP and HANA artefacts in the same project, we would ask that you also choose SAP HANA Calculation View Editor and SAP HANA Tools at minimum.
+1. The Dev space will automatically be configured with the most common tools you need for the type of application you choose. However you can also choose additional, optional extensions. Since you want to combine CAP and HANA artefacts in the same project, we would ask that you also choose SAP HANA Calculation View Editor and SAP HANA Tools at minimum.
 
     !![Configure Dev Space](configure_cap_dev_space.png)
 
-5. Once all selections are completed, press **Create Dev Space**
+1. Once all selections are completed, press **Create Dev Space**
 
     !![Press Create Dev Space](create_dev_space.png)
 
-6. The Dev Space will then begin starting and the process will take a minute or so as your cloud environment is being created
+1. The Dev Space will then begin starting and the process will take a minute or so as your cloud environment is being created
 
     !![Staring Dev Space](dev_space_starting.png)
 
-7. Once the Dev Space reaches the green status of **RUNNING**, you can click on the name of the Dev Space and it will load into the editor within your browser
+1. Once the Dev Space reaches the green status of **RUNNING**, you can click on the name of the Dev Space and it will load into the editor within your browser
 
     !![Dev Space is Running](dev_space_running.png)
 
-8. You'll be redirected to your newly created SAP Business Application Studio Dev Space. We recommend you bookmark this URL so it's easier for you to access this dev space of your SAP Business Application Studio in the future
+1. You'll be redirected to your newly created SAP Business Application Studio Dev Space. We recommend you bookmark this URL so it's easier for you to access this dev space of your SAP Business Application Studio in the future
 
     !![Business Application Studio is running](fully_running.png)
 
@@ -76,71 +78,69 @@ Before we create our SAP HANA project, we want to do a few more one-time configu
 
     !![CF Not Set](cf_not_set.png)
 
-2. Now in the Cloud Foundry Targets window you can expand either Service or Applications and then click on the Logon icon to continue the configuration process
+1. Now in the Cloud Foundry Targets window you can expand either Service or Applications and then click on the Logon icon to continue the configuration process
 
     !![Login Required](cf_login_required.png)
 
-3. The command window will then open at the top of the SAP Business Application Studio. The first input will prompt you for the API endpoint
+1. The command window will then open at the top of the SAP Business Application Studio. The first input will prompt you for the API endpoint
 
     !![API Endpoint](api_endpoint.png)
 
-4. The default value proposed is likely the correct value, but if you need to confirm; the value can be found in the SAP BTP cockpit at the Subaccount level
+1. The default value proposed is likely the correct value, but if you need to confirm; the value can be found in the SAP BTP cockpit at the Subaccount level
 
     !![Finding the API Endpoint](api_endpoint_from_subaccount.png)
 
-5. Press **Enter** to confirm your input of the API endpoint. The next input field will ask you for the email address you used to create your SAP BTP trial account
+1. Press **Enter** to confirm your input of the API endpoint. The next input field will ask you for the email address you used to create your SAP BTP trial account
 
     !![Email](email.png)
 
-6. The next input will ask you for your SAP BTP trial account password
+1. The next input will ask you for your SAP BTP trial account password
 
     !![Password](password.png)
 
-7. The next input will ask you for your Organization. In most situations you will have a single choice. But like the API endpoint earlier, if you need to confirm the correct value it will be displayed in the top navigation of the SAP BTP cockpit
+1. The next input will ask you for your Organization. In most situations you will have a single choice. But like the API endpoint earlier, if you need to confirm the correct value it will be displayed in the top navigation of the SAP BTP cockpit
 
     !![Organization](organization.png)
 
-8. The final input will ask you for your Space. If you choose the endpoint API and Organization correctly, then you should have a single option of **dev**
+1. The final input will ask you for your Space. If you choose the endpoint API and Organization correctly, then you should have a single option of **dev**
 
     !![Space](space.png)
 
-9. Upon completion of all the inputs, you should see that the Organization and Space have been set and you will see any service instances or application instances from the target space.
+1. Upon completion of all the inputs, you should see that the Organization and Space have been set and you will see any service instances or application instances from the target space.
 
     !![Org and Space Set Correctly](org_space_set_correctly.png)
 
 [DONE]
 [ACCORDION-END]
 
-
 [ACCORDION-BEGIN [Step 3: ](Create a new project)]
 
 1. Return to the **Explorer** view. From the SAP Business Application Studio Welcome tab, click **Start from template Create a new project**.
 
     !![New project from template](start_from_template.png)
 
-2. Choose **CAP Project** and click Start    
+1. Choose **CAP Project** and click Start
 
     !![Choose CAP Project](cap_project.png)
 
-3. Use the following name for your project and click **Next**
+1. Use the following name for your project and click **Next**
 
     ```Name
     MyHANAApp
     ```
 
-    > **This name will be used in different steps**. It is recommended that you do not change it unless you remember to replace it in future tasks.    
+    > **This name will be used in different steps**. It is recommended that you do not change it unless you remember to replace it in future tasks.
 
     !![New CAP Project Name](cap_project_name.png)
 
-    Choose `Node.js` as the runtime. Select `CI/CD Pipeline Integration`, `Configuration for SAP HANA Deployment`, and `MTA based SAP Cloud Platform Deployment` as the additional features for your project.  Press **Finish**
+    Choose `Node.js` as the runtime. Select `CI/CD Pipeline Integration`, `Configuration for SAP HANA Deployment`, and `MTA based SAP Business Technology Platform Deployment` as the additional features for your project.  Press **Finish**
 
     !![New CAP Project Details](cap_project_details.png)
 
-4. The new project should be added to your workspace automatically.
+1. The new project should be added to your workspace automatically.
 
     !![Open in New Workspace](new_workspace.png)
 
-
 [DONE]
 [ACCORDION-END]
 
@@ -150,15 +150,14 @@ Before we create our SAP HANA project, we want to do a few more one-time configu
 
     !![New CAP model project structure](new_project_structure.png)
 
-2. The wizard has also populated the `mta.yaml` configuration file with the necessary dependencies and parameters for each module. Open it in the code editor to explore it.
+1. The wizard has also populated the `mta.yaml` configuration file with the necessary dependencies and parameters for each module. Open it in the code editor to explore it.
 
     !![New CAP model project mta.yaml explained](mta_explained.png)
 
     This file is the deployment descriptor and it is the glue that keeps all the micro-services together as a single application throughout its lifecycle. It declares the modules (applications or micro-services) and their dependencies with other micro-services or backing services. You can also use this file to inject variables into the environment variable `VCAP_SERVICES` of your application.
 
     > This file is very sensitive to indentation and does not allow for tabs.
 
-
 [DONE]
 [ACCORDION-END]
 
@@ -170,17 +169,17 @@ The Cloud Application Programming Model wizard generates a project that supports
 
     !![Adjust db module path](db_path.png)
 
-2. Save these changes
+1. Save these changes
 
-3. In the root of the project there is another important configuration file - the package.json. We are going to need to make several changes to this file as well.
+1. In the root of the project there is another important configuration file - the package.json. We are going to need to make several changes to this file as well.
 
     !![Open package.json for editing](package_json.png)
 
     > No need to worry about the yellow underlining below the name of the package. This is just a hint and doesn't have any impact on the tutorial.
 
-4. You can completely delete the `devDependencies` section of the `package.json`
+1. You can completely delete the `devDependencies` section of the `package.json`
 
-5. The rest of the changes will be in the `cds` section of the file. Replace this entire section of `package.json` with the following content
+1. The rest of the changes will be in the `cds` section of the file. Replace this entire section of `package.json` with the following content
 
     ```json
     "cds": {
@@ -208,7 +207,7 @@ The Cloud Application Programming Model wizard generates a project that supports
 
     > These changes will alter the generated folder structure of the cds build operation. Content will no longer be placed into the gen folder for the db module but back into the source folders. This also will tell CAP to generate hdbtable artifacts instead of hdbcds. This is a critical change for SAP HANA Cloud compatibility. Finally the db.kind change to HANA tells CAP to use HANA at development time instead of SQLite.
 
-6. Save the file
+1. Save the file
 
 [DONE]
 [ACCORDION-END]
@@ -217,29 +216,29 @@ The Cloud Application Programming Model wizard generates a project that supports
 
 We are using several dependent Node.js modules in our project. They are referenced in the `dependencies` section of the package.json file we were just editing. These dependencies need to be installed into your project before we can do any testing.
 
-1.  Open a new terminal
+1. Open a new terminal
 
     !![New Terminal](new_terminal.png)
 
-2. The terminal will open in the bottom right of the Business Application studio
+1. The terminal will open in the bottom right of the Business Application studio
 
     !![Terminal in BAS](terminal_in_BAS.png)
 
-3. From the terminal run the command `npm install`
+1. From the terminal run the command `npm install`
 
     ```shell
     npm install
     ```
 
     !![npm install](npm_install.png)
 
-4. For one last change we need to adjust the content generated by the wizard for the **db** folder. The CAP wizard expects that you will use the `cds deploy` command to send content into HANA. However to use the HANA Projects view to deploy to HANA we need some additional files in the **db** folder. Mainly we need a package.json file that will run the `@sap-hdi-deploy` module. Rather than create this file manually, we will use an open source sample utility called hana-cli.  From this same terminal window run the command ```npm install -g hana-cli```
+1. For one last change we need to adjust the content generated by the wizard for the **db** folder. The CAP wizard expects that you will use the `cds deploy` command to send content into HANA. However to use the HANA Projects view to deploy to HANA we need some additional files in the **db** folder. Mainly we need a package.json file that will run the `@sap-hdi-deploy` module. Rather than create this file manually, we will use an open source sample utility called hana-cli.  From this same terminal window run the command ```npm install -g hana-cli```
 
     ```shell
     npm install -g hana-cli
     ```
 
-5. After installation run the command ```hana-cli createModule```
+1. After installation run the command ```hana-cli createModule```
 
     ```shell
     hana-cli createModule
@@ -252,17 +251,17 @@ We are using several dependent Node.js modules in our project. They are referenc
 
 You will use the local Git repository for basic version management.
 
-2. Click on the **Source Control** icon
+1. Click on the **Source Control** icon
 
     !![Source Control](source_control.png)
 
-3. Click on the **Initialize Repository** icon
+1. Click on the **Initialize Repository** icon
 
     !![Initialize Repository](initialize_repository.png)
 
-4. The Source Control panel now shows that it is being managed by Git and changes are being tracked
+1. The Source Control panel now shows that it is being managed by Git and changes are being tracked
 
-    !![Source Control: GIT](source_control_git.png)        
+    !![Source Control: GIT](source_control_git.png)
 
 [DONE]
 [ACCORDION-END]
@@ -285,6 +284,4 @@ Each time you commit to the local or remote repository, you create a version. Th
 [DONE]
 [ACCORDION-END]
 
-
-
 ---