Add explainations and improve exercise questions

Author: Marius Obert

exercises/03/readme.md

@@ -144,7 +144,7 @@ To prepare the app for a multiple databases, change the content to:
 }
 ```
 
-:point_right: As we want to use a local SQLite database, we need to install a client to communicate with this DH. Install the `sqlite3` package for this job.
+:point_right: As we want to use a local SQLite database, we need to install a client to communicate with this DB. Install the `sqlite3` package for this job.
 ```
 npm install -D sqlite3
 ```

exercises/04/readme.md

@@ -40,13 +40,16 @@ During deployment this time you should see an extra message:
 
 
 ### 3. Add config files for HANA
-Update HANA version db/src/.hdiconfig
+The `.hdiconfig` file specifies the configuration of the used HDI container. .
 
+:point_right: Change the following property of the `db/src/.hdiconfig` file to adapt the version to the HANA version used in the SAP Cloud Platform Cloud Foundry trial.
 ```
 "plugin_version": "12.1.0",
 ```
 
-`db/csv/Data.hdbtabledata`
+While SQLite automatically imports the CSV files, we need to provide more information for HANA to import those files. These import instructions are encoded in a `.hdbtabledata` file and will be read during the deployment process to the Cloud Foundry environment.
+
+ :point_right: Create a new `db/csv/Data.hdbtabledata` file with the following content to specify which data should be imported into the HANA tables.
 ```
 {
  "format_version": 1,

exercises/05/readme.md

@@ -125,7 +125,6 @@ entity Orders : cuid, managed {
  country : Country;
 }
 ```
-@DJ do you think we should compress these steps into one? I'd feel fooled to you were telling me to change the same 4 lines in 3 consequitive steps.
 
 Note the difference in capitalization here. The property name is `country` which is described by the type `Country`.
 

exercises/08/readme.md

@@ -137,7 +137,9 @@ At this point we're confident enough to start adding custom logic, by [registeri
 
 
 ### 6. Add a independent project descriptor
-`svr/package.json:`
+You might have noticed that there is no module descriptor for the server module defined. For the local development, such a descriptor is not needed as CDS knows how to parse those files. For the deployment to Cloud Foundry, on the other hand, such a file is required to define the module dependencies and start commands.
+
+:point_right: Add a new `package.json` file with the following content to the `svr` module to make it cloud-ready.
 ```json
 {
  "name": "project-srv",

exercises/09/readme.md

@@ -86,8 +86,7 @@ Reloading the browser tab should now show the beginnings of something recognizab
 
 
 ### 3. Add a new module to the project descriptor
-
-mta.yaml:
+:point_right: Add this new module to the project descriptor file `mta.yaml` next to the other modules as follows:
 ```
 - name: bookshop-ui
  type: nodejs
@@ -105,6 +104,7 @@ mta.yaml:
  url: ~{url}
 ```
 
+This snippet does not only describe the runtime environment of the new module, it also injects the URL of the deployed `svr` module during deploy time.
 
 
 ### 4. Introduce a basic UI app to the Fiori launchpad
@@ -256,7 +256,7 @@ This is a modern UI5 component definition that points to a JSON configuration fi
 
 This is the point where you can introduce an `index.cds` file, at the same level as the `index.html` file. This CDS index controls which services are exposed.
 
-:point_right: Create a file `index.cds` in the `srv/`(! @DJ, please note this change) directory, and add the following single line as the initial content:
+:point_right: Create a file `index.cds` in the `srv/` directory, and add the following single line as the initial content:
 
 ```cds
 using from '../srv/cat-service';
@@ -341,7 +341,10 @@ Books=Books
 
 
 ### 10. Add the app router configuration
-`package.json`
+Similar to the `svr` module, Cloud Foundry needs us to add a module descriptor for here as well.
+
+
+:point_right: Add a `package.json` file in the `app` module to start this module as a independent app router application within Cloud Foundry.
 ```
 {
  "name": "bookshop-ui",
@@ -357,6 +360,8 @@ Books=Books
 }
 ```
 
+:point_right: Add the following file to configure the app router. This file does not only define the welcome page, but also defines which request are forwarded to which Cloud Foundry application.
+
 `xs-app.json`
 ```
 {
@@ -386,3 +391,7 @@ While this was a little intense as far as creation of artefacts was concerned, w
 1. Where might further apps be defined live in this logical structure?
 
 1. What other features can you imagine being useful to users and supported by Fiori Elements and annotations?
+
+1. Which variable have you accessed in the `mta.yaml` descriptor and were has it been defined?
+
+1. Where has this variable been used?

exercises/10/readme.md

@@ -1,25 +1,60 @@
 # Exercise 10
 
 
-#Check if your signed in to a Cloud Foundry organization
+## 1. Sign in to Cloud Foundry
+
+:point_right: Run the following command from your command line to log in to the referenced Cloud Foundry endpoint. When prompted use your SAP Cloud Platform credentials
+```
+cf login -a https://api.cf.eu10.hana.ondemand.com
+```
+
+## 2. Explore the artefacts in Cloud Foundry
+:point_right: Run the following commands to see all deployed apps and provisioned backing services.
 ```
 cf apps
+cf services
 ```
 
-## 1. Add npm scripts
-@DJ do you think we should introduce these scripts easier (and use `npm run` commands over `cds` commands)
+## 3. Add npm scripts
+So far, the `package.json` file in your project root only defines scripts to test the project locally.
+
+
+:point_right: Add the following script to control to build and deploy steps as well.
+```
 "deploy:cds": "cds deploy",
 "build:mta": "cds build/all && shx cp db/csv/Data.hdbtabledata db/src/gen/csv/ && mbt build -p=cf",
 "deploy:cf": "npm run build:mta && cf deploy mta_archives/${npm_package_name}_${npm_package_version}.mtar"
+```
 
- npx i shx
+You might have noticed, that the `shx` command isn't a typical shell command. This is actually a command from another node module.
 
-## 2. Build the app
+:point_right: Install this module in your project via the command line to allow its usage in the npm scripts.
+```
+npx install shx
+```
+
+## 4. Build the app
+:point_right: Trigger the build process with the following command.
 ```
 npm run build:mta
 ```
-## 3. Deploy the archive
+## 5. Deploy the archive
+
+:point_right: One command is all it takes to deploy your project to the cloud. Execute the following command to trigger the deployment process.
 ```
 cf deploy mta_archives/bookshop_1.0.0.mtar
 ```
-Note: `npm run deploy:cf` would do the same
+
+> Note: You can also use `npm run deploy:cf` to trigger both, the build and deploy steps
+
+## Summary
+
+You have learned the basic commands to interact with the Cloud Foundry Command Line Interface to check the state of the deployed applications. You also added the necessary scripts to your project to automate the build and deploy steps via the command line.
+
+## Questions
+
+1. Can you guess what the script `deploy:cf` does? Is there anything special to this script (compared to the other scripts)?
+
+1. When you run the commands from step 2 again, what do you see now?
+
+1. Check the SAP Cloud Platform Cockpit to see the same information. Are all apps in the `running` state now?