Skip to content

Commit b47b5bc

Browse files
authored
minor edits in readme (#29)
1 parent 35084c9 commit b47b5bc

1 file changed

Lines changed: 20 additions & 20 deletions

File tree

README.md

Lines changed: 20 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,7 @@ A Fiori UI is added using predefined SAP Fiori elements templates. **[Fiori anno
3838

3939
## Demonstrated Features
4040

41-
Framework and Infrastructure-related Features:
41+
Framework and Infrastructure related Features:
4242

4343
- [Application configuration](https://cap.cloud.sap/docs/java/development#application-configuration) for Spring and CDS using [application.yaml](srv/src/main/resources/application.yaml)
4444
- [Mocking users](/srv/src/main/resources/application.yaml) for local development
@@ -72,11 +72,11 @@ User Interface related Features:
7272

7373
CDS Maven Plugin Features:
7474

75-
- Install [Node.js](srv/pom.xml#L87) in the specified version
76-
- Install the latest version of [@sap/cds-dk](srv/pom.xml#L97)
77-
- Execute arbitrary [CDS](srv/pom.xml#L107) commands
78-
- [Generate](srv/pom.xml#L122) Java POJOs for type-safe access to the CDS model
79-
- [Clean](srv/pom.xml#L80) project from artifacts of the previous build
75+
- Install [Node.js](srv/pom.xml#L87) in the specified version.
76+
- Install the latest version of [@sap/cds-dk](srv/pom.xml#L97).
77+
- Execute arbitrary [CDS](srv/pom.xml#L107) commands.
78+
- [Generate](srv/pom.xml#L122) Java POJOs for type-safe access to the CDS model.
79+
- [Clean](srv/pom.xml#L80) project from artifacts of the previous build.
8080

8181
# Getting Started
8282

@@ -133,9 +133,9 @@ Optionally, use the following steps to import the project to Eclipse:
133133
4. Use the following links in the browser to check if everything works fine:
134134

135135
<http://localhost:8080/>: This should show the automatically generated index page of served paths.
136-
<http://localhost:8080/fiori.html>: This is the actual bookshop application UI
136+
<http://localhost:8080/fiori.html>: This is the actual bookshop application UI.
137137

138-
You'll start with an empty stock of books as this procedure starts the bookshop application with an empty in-memory sqlite database.
138+
You'll start with an empty stock of books as this procedure starts the bookshop application with an empty in-memory SQLite database.
139139

140140
Two mock users are defined for local development:
141141
- User: `user`, password: `user` to browse books
@@ -153,14 +153,14 @@ The application comes with three predefined profiles: `default`, `sqlite`, and `
153153
This database needs to be created first, to ensure it’s initialized with the correct schema and with the CSV-based example data.
154154
To initialize the database, simply run `cds deploy --to sql:sqlite.db --no-save` from the project's root directory. Repeat this step, once you make changes to the CDS model.
155155

156-
- When deploying the application to the CloudFoundry, the CF Java Buildpack automatically configures the `cloud` Spring profile.
157-
This profile doesn’t specify any datasource location. In that case CAP Java can automatically detect HANA service bindings available in the environment.
156+
- When deploying the application to Cloud Foundry, the CF Java Buildpack automatically configures the `cloud` Spring profile.
157+
This profile doesn’t specify any datasource location. In that case CAP Java can automatically detect SAP HANA service bindings available in the environment.
158158

159159
## Using a File-Based SQLite Database
160160

161-
To switch from the default in-memory SQLite database to a file-based SQLite database in this sample application perform the following steps:
161+
To switch from the default in-memory SQLite database to a file-based SQLite database in this sample application, perform the following steps:
162162

163-
1. Deploy the example data stored in .csv files in the folder ``db/data`` to a file-based SQLite database by executing the command-line utility
163+
1. Deploy the example data stored in .csv files in the folder `db/data` to a file-based SQLite database by executing the command-line utility
164164

165165
```cds deploy --to sql:sqlite.db --no-save```
166166

@@ -170,27 +170,27 @@ To switch from the default in-memory SQLite database to a file-based SQLite data
170170

171171
## Deploy to SAP Cloud Platform
172172

173-
CAP Java applications can be deployed to the SAP Cloud Platform either in single tenant or in multitenancy mode (see [Multitenancy in CAP Java](https://cap.cloud.sap/docs/java/multitenancy) for more information.
173+
CAP Java applications can be deployed to the SAP Cloud Platform either in single tenant or in multitenancy mode. See [Multitenancy in CAP Java](https://cap.cloud.sap/docs/java/multitenancy) for more information.
174174

175175
Prerequisites:
176-
- Install the [Cloud MTA Build Tool](https://sap.github.io/cloud-mta-build-tool/): `npm install -g mbt
177-
- Install the [Cloud Foundry Command Line Interface](https://docs.cloudfoundry.org/cf-cli/install-go-cli.html)
178-
- Get a SAP Cloud Platform account to deploy the services and applications
176+
- Install the [Cloud MTA Build Tool](https://sap.github.io/cloud-mta-build-tool/): `npm install -g mbt`.
177+
- Install the [Cloud Foundry Command Line Interface](https://docs.cloudfoundry.org/cf-cli/install-go-cli.html).
178+
- Get an SAP Cloud Platform account to deploy the services and applications.
179179

180-
Deploy as Single Tenant Application
180+
Deploy as Single Tenant Application:
181181
- Rename `mta-single-tenant.yaml` to `mta.yaml`
182182
- Run `mbt build`
183183
- Run `cf login`
184184
- Run `cf deploy mta_archives/bookshop-java-public_1.0.0.mtar`
185185

186186
Deploy as Multitenant Application:
187-
- Create a SAP HANA Cloud Instance in your SAP Cloud Platform space
187+
- Create an SAP HANA Cloud Instance in your SAP Cloud Platform space.
188188
- Rename `mta-multi-tenant.yaml` to `mta.yaml`
189189
- Run `mbt build`
190190
- Run `cf login`
191191
- Run `cf deploy mta_archives/bookshop-java-public_1.0.0.mtar`
192-
- Go to another subaccount in your global account, under subscriptions and subscribe to the application you deployed
193-
- Run `cf map-route bookshop-java-public-approuter <YOUR DOMAIN> --hostname <SUBSCRIBER TENANT>-<ORG>-<SPACE>-bookshop-java-public-approuter` or create and bind the route manually
192+
- Go to another subaccount in your global account, under subscriptions and subscribe to the application you deployed.
193+
- Run `cf map-route bookshop-java-public-approuter <YOUR DOMAIN> --hostname <SUBSCRIBER TENANT>-<ORG>-<SPACE>-bookshop-java-public-approuter` or create and bind the route manually.
194194

195195
# Get Support
196196

0 commit comments

Comments
 (0)