From 84b54f93d989636567009f0c32adf2b968f988ef Mon Sep 17 00:00:00 2001 From: D056267 Date: Mon, 4 Dec 2023 12:33:03 +0100 Subject: [PATCH 1/4] text optimization --- documentation/meter/discover-metering-usecase/README.md | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/documentation/meter/discover-metering-usecase/README.md b/documentation/meter/discover-metering-usecase/README.md index 6889ef0..cb57e22 100644 --- a/documentation/meter/discover-metering-usecase/README.md +++ b/documentation/meter/discover-metering-usecase/README.md @@ -1,10 +1,6 @@ # Discover the Metering Use Case -Measuring usage of a business service or application is useful for commercial purposes such as billing, license compliance and cost assessments. - -Which measurable values could be used for commercial purposes depends on the business logic of your application. This value should be comprehensible for tenants (City Scooter or Bicycle Sharing). - -The number of active users seems like a good example of metering, lets have a deeper look at it. Here is the user story: +Measuring the usage of a business service or an application is useful for commercial purposes such as billing, license compliance and cost assessments. The measurable values that could be used for commercial purposes depends often on the business logic of your application. As the number of active users seems to be a good example of metering, let's have a closer look at it. Here is the user story: * As an SAP partner, I would like to know the number of active users per month and per tenant, so that I can check those numbers against the sold licenses and use those metrics as basis for billing. * As an SAP partner, I want to have a dashboard, where I can see the number of active users and eventually other metrics, so that I can quickly get a good overview of application usage. From c8c2f9f83afcb022a0596c89b4c0dd045a2bc7c2 Mon Sep 17 00:00:00 2001 From: D056267 Date: Mon, 4 Dec 2023 12:38:27 +0100 Subject: [PATCH 2/4] text optimization --- documentation/meter/discover-metering-usecase/README.md | 2 +- documentation/meter/understand-day2-app/README.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/documentation/meter/discover-metering-usecase/README.md b/documentation/meter/discover-metering-usecase/README.md index cb57e22..083db90 100644 --- a/documentation/meter/discover-metering-usecase/README.md +++ b/documentation/meter/discover-metering-usecase/README.md @@ -1,6 +1,6 @@ # Discover the Metering Use Case -Measuring the usage of a business service or an application is useful for commercial purposes such as billing, license compliance and cost assessments. The measurable values that could be used for commercial purposes depends often on the business logic of your application. As the number of active users seems to be a good example of metering, let's have a closer look at it. Here is the user story: +Measuring the usage of a business service or an application is useful for commercial purposes such as billing, license compliance and cost assessments. The measurable values that could be used for commercial purposes depends often on the business logic of your application. As the number of active users seems to be a good example of metering, let us have a closer look at it. Here is the user story: * As an SAP partner, I would like to know the number of active users per month and per tenant, so that I can check those numbers against the sold licenses and use those metrics as basis for billing. * As an SAP partner, I want to have a dashboard, where I can see the number of active users and eventually other metrics, so that I can quickly get a good overview of application usage. diff --git a/documentation/meter/understand-day2-app/README.md b/documentation/meter/understand-day2-app/README.md index fc24e93..7d5a70a 100644 --- a/documentation/meter/understand-day2-app/README.md +++ b/documentation/meter/understand-day2-app/README.md @@ -1,6 +1,6 @@ # Understand the Implementation of the Day2 Application -Lets first recap the architecture of the EasyFranchise application without metering: +Let us first recap the architecture of the EasyFranchise application without metering: ![](https://raw.githubusercontent.com/SAP-samples/btp-kyma-multitenant-extension/main/documentation/images/easyfranchise-diagrams/Slide4.jpeg) From 7c195feccba525538852a5c3a33e97aed307f8c8 Mon Sep 17 00:00:00 2001 From: D056267 Date: Mon, 4 Dec 2023 12:41:25 +0100 Subject: [PATCH 3/4] typo --- documentation/meter/learn-other-metrics/README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/documentation/meter/learn-other-metrics/README.md b/documentation/meter/learn-other-metrics/README.md index 336e305..66b9599 100644 --- a/documentation/meter/learn-other-metrics/README.md +++ b/documentation/meter/learn-other-metrics/README.md @@ -1,6 +1,6 @@ # Learn More About Other Business Logic Metrics -When looking at the **Easy Franchise Application**, you might want to meter other metrics. For example, you might want to count when an email is sent or when a new Mentor is assigned. +When looking at the **Easy Franchise Application**, you might want to meter other metrics. For example, you might want to count when an email is sent or when a new mentor is assigned. In your own scenario you might face completely different requirements. From 2775434912678b3a0c0f9d109cd210e846369612 Mon Sep 17 00:00:00 2001 From: D056267 Date: Wed, 6 Dec 2023 14:28:57 +0100 Subject: [PATCH 4/4] updating xsec + appRouter --- code/day2-operations/source/day2-approuter/package.json | 2 +- code/easyfranchise/source/approuter/package.json | 4 ++-- code/easyfranchise/source/broker/package.json | 2 +- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/code/day2-operations/source/day2-approuter/package.json b/code/day2-operations/source/day2-approuter/package.json index 8a6c900..542c9e1 100644 --- a/code/day2-operations/source/day2-approuter/package.json +++ b/code/day2-operations/source/day2-approuter/package.json @@ -1,7 +1,7 @@ { "name": "day2-approuter", "dependencies": { - "@sap/approuter": "10.15.0" + "@sap/approuter": "14.4.2" }, "scripts": { "start": "node node_modules/@sap/approuter/approuter.js" diff --git a/code/easyfranchise/source/approuter/package.json b/code/easyfranchise/source/approuter/package.json index 51e9053..6f86dd6 100644 --- a/code/easyfranchise/source/approuter/package.json +++ b/code/easyfranchise/source/approuter/package.json @@ -7,9 +7,9 @@ "start": "node approuter-start.js" }, "dependencies": { - "@sap/approuter": "14.3.4", + "@sap/approuter": "14.4.2", "@sap/xsenv": "^4.0.0", - "@sap/xssec": "^3.4.0", + "@sap/xssec": "^3.6.0", "jwt-decode": "^4.0.0" }, "devDependencies": {}, diff --git a/code/easyfranchise/source/broker/package.json b/code/easyfranchise/source/broker/package.json index 7205b75..ac98752 100644 --- a/code/easyfranchise/source/broker/package.json +++ b/code/easyfranchise/source/broker/package.json @@ -4,7 +4,7 @@ "dependencies": { "@kubernetes/client-node": "~0.15.0", "@sap/xsenv": "~3.1.0", - "@sap/xssec": "~3.2.8", + "@sap/xssec": "^3.6.0", "axios": "^0.23.0", "express": "~4.17.1", "passport": "^0.5.0"