Skip to content

Commit 42a5a4c

Browse files
iwonahahniwonahahn
authored
Update btp-app-kyma-launchpad-service.md
1 parent 1629231 commit 42a5a4c

1 file changed

Lines changed: 31 additions & 30 deletions

File tree

‎tutorials/btp-app-kyma-launchpad-service/btp-app-kyma-launchpad-service.md‎

Lines changed: 31 additions & 30 deletions
Original file line numberDiff line numberDiff line change
@@ -43,18 +43,14 @@ To start with this tutorial use the result in the [`kyma-add-helm-chart`](https:
4343

4444
[ACCORDION-BEGIN [Step 1: ](Prepare UI Applications)]
4545

46-
[DONE]
47-
[ACCORDION-END]
48-
---
49-
[ACCORDION-BEGIN [Step 2: ](Add navigation targets)]
5046
In this tutorial, you will use the SAP Launchpad service to access your CAP service and its UI. Additionally, the SAP Launchpad service provides features like personalization, role-based visibility, theming, and more. You can add multiple applications to one launchpad, including subscribed ones and applications from SAP S/4HANA or SAP BTP.
5147

5248
Navigation targets are required to navigate between applications, but also to start the applications from SAP Launchpad service. In the next steps, you add the navigation targets `Risks-display` and `Mitigations-display` to the application manifest (`manifest.json`) file.
5349

5450
[DONE]
5551
[ACCORDION-END]
5652
---
57-
[ACCORDION-BEGIN [Step 3: ](Add navigation target for Risks UI)]
53+
[ACCORDION-BEGIN [Step 2: ](Add navigation target for Risks UI)]
5854
1. Open the file `app/risks/webapp/manifest.json`.
5955

6056
2. Add the external navigation target to the `sap.app` JSON object. You can add it right behind the `sourceTemplate` object:
@@ -88,7 +84,7 @@ Navigation targets are required to navigate between applications, but also to st
8884
[DONE]
8985
[ACCORDION-END]
9086
---
91-
[ACCORDION-BEGIN [Step 4: ](Add navigation target for Mitigations UI)]
87+
[ACCORDION-BEGIN [Step 3: ](Add navigation target for Mitigations UI)]
9288
Do the same with the mitigations manifest file `app/mitigations/webapp/manifest.json`, but with the `semanticObject` name `Mitigations`.
9389

9490
<!-- cpes-file app/mitigations/webapp/manifest.json:$["sap.app"].crossNavigation -->
@@ -120,7 +116,7 @@ Do the same with the mitigations manifest file `app/mitigations/webapp/manifest.
120116
[DONE]
121117
[ACCORDION-END]
122118
---
123-
[ACCORDION-BEGIN [Step 5: ](Install required UI tools)]
119+
[ACCORDION-BEGIN [Step 4: ](Install required UI tools)]
124120
1. Install [SAPUI5 tooling](https://www.npmjs.com/package/@sap/ux-ui5-tooling) package as global module in the root folder of your project:
125121

126122
```Shell/Bash
@@ -136,12 +132,12 @@ Do the same with the mitigations manifest file `app/mitigations/webapp/manifest.
136132
[DONE]
137133
[ACCORDION-END]
138134
---
139-
[ACCORDION-BEGIN [Step 6: ](Add deployment config for HTML5 applications)]
135+
[ACCORDION-BEGIN [Step 5: ](Add deployment config for HTML5 applications)]
140136
141137
[DONE]
142138
[ACCORDION-END]
143139
---
144-
[ACCORDION-BEGIN [Step 7: ](Add SAP Fiori elements Risks application)]
140+
[ACCORDION-BEGIN [Step 6: ](Add SAP Fiori elements Risks application)]
145141
1. Switch to `app/risks` folder:
146142
147143
```Shell/Bash
@@ -181,7 +177,7 @@ Do the same with the mitigations manifest file `app/mitigations/webapp/manifest.
181177
[DONE]
182178
[ACCORDION-END]
183179
---
184-
[ACCORDION-BEGIN [Step 8: ](Add SAP Fiori elements Mitigations application)]
180+
[ACCORDION-BEGIN [Step 7: ](Add SAP Fiori elements Mitigations application)]
185181
1. Switch to the `app/mitigations` folder
186182
187183
```Shell/Bash
@@ -202,7 +198,7 @@ Do the same with the mitigations manifest file `app/mitigations/webapp/manifest.
202198
[DONE]
203199
[ACCORDION-END]
204200
---
205-
[ACCORDION-BEGIN [Step 9: ](Change cloud service)]
201+
[ACCORDION-BEGIN [Step 8: ](Change cloud service)]
206202
The `fiori` command automatically sets some value to the SAP Cloud service property in both `app/risks/webapp/manifest.json` and `app/mitigations/webapp/manifest.json` files. Change the `sap.cloud.service` property in `app/risks/webapp/manifest.json` and `app/mitigations/webapp/manifest.json`:
207203
208204
```JSON[3]
@@ -215,7 +211,7 @@ The `fiori` command automatically sets some value to the SAP Cloud service prope
215211
[DONE]
216212
[ACCORDION-END]
217213
---
218-
[ACCORDION-BEGIN [Step 10: ](Create package.json and build script for app deployer)]
214+
[ACCORDION-BEGIN [Step 9: ](Create package.json and build script for app deployer)]
219215
1. Create a file `app/package.json` for the HTML5 application `deployer` application and add the following code to it:
220216

221217
```JSON
@@ -261,7 +257,6 @@ The `fiori` command automatically sets some value to the SAP Cloud service prope
261257

262258
This script calls the UI5 build for the two SAP Fiori applications and copies the result into the `resources` directory.
263259

264-
265260
3. Navigate back to your project root folder:
266261

267262
```Shell/Bash
@@ -285,7 +280,7 @@ The `fiori` command automatically sets some value to the SAP Cloud service prope
285280
[DONE]
286281
[ACCORDION-END]
287282
---
288-
[ACCORDION-BEGIN [Step 11: ](Build HTML5 application deployer image)]
283+
[ACCORDION-BEGIN [Step 10: ](Build HTML5 application deployer image)]
289284
1. Set container registry environment variable:
290285

291286
```Shell/Bash
@@ -313,7 +308,7 @@ The `fiori` command automatically sets some value to the SAP Cloud service prope
313308
[DONE]
314309
[ACCORDION-END]
315310
---
316-
[ACCORDION-BEGIN [Step 12: ](Configure Helm chart for HTML5 application deployment)]
311+
[ACCORDION-BEGIN [Step 11: ](Configure Helm chart for HTML5 application deployment)]
317312
1. Add the HTML5 Application `deployer` to your Helm chart:
318313

319314
```
@@ -349,15 +344,17 @@ The `fiori` command automatically sets some value to the SAP Cloud service prope
349344

350345
The backend destination configuration creates a destination with the name `cpapp-srv` pointing to the URL for your CAP service `srv`.
351346

352-
[DONE]
347+
[VALIDATE 1]
353348
[ACCORDION-END]
354349
---
355-
[ACCORDION-BEGIN [Step 13: ](Re-Deploy your application)]
350+
[ACCORDION-BEGIN [Step 12: ](Re-Deploy your application)]
356351
```Shell/Bash
357352
helm upgrade cpapp ./chart --install
358353
```
359-
360-
## Subscribe to SAP Launchpad service
354+
[DONE]
355+
[ACCORDION-END]
356+
---
357+
[ACCORDION-BEGIN [Step 13: ](Subscribe to SAP Launchpad service)]
361358

362359
1. Enter your **Global Account**. If you are using a trial account, choose **Go To Your Trial Account**.
363360

@@ -378,24 +375,28 @@ helm upgrade cpapp ./chart --install
378375
!![New Instance or Subscription](new_instance_dialog.png)
379376

380377
You have now subscribed to the SAP Launchpad service.
381-
382-
## Assign SAP Launchpad role collection
378+
[DONE]
379+
[ACCORDION-END]
380+
---
381+
[ACCORDION-BEGIN [Step 14: ](Assign SAP Launchpad role collection)]
383382

384383
You need to assign your user to the `Launchpad_Admin` role collection, so you don't get an error accessing the **Launchpad Service** site later on.
385384

386385
1. Choose **Security** **&rarr;** **Users** on the left.
387386

388387
2. Choose your user.
389388

390-
4. Under **Role Collections** on the right, choose **Assign Role Collection** and assign the `Launchpad_Admin` role collection to your user.
389+
3. Under **Role Collections** on the right, choose **Assign Role Collection** and assign the `Launchpad_Admin` role collection to your user.
391390

392391
!![Add role](add_launchpad_admin_role.png)
393392

394-
5. Open another browser or clear your browser's cache.
393+
4. Open another browser or clear your browser's cache.
395394

396395
> See section [Initial Setup](https://help.sap.com/viewer/8c8e1958338140699bd4811b37b82ece/Cloud/en-US/fd79b232967545569d1ae4d8f691016b.html) in the SAP Launchpad service's documentation for more details.
397-
398-
## Create your SAP Launchpad site
396+
> [DONE]
397+
[ACCORDION-END]
398+
---
399+
[ACCORDION-BEGIN [Step 15: ](Create your SAP Launchpad site)]
399400

400401
1. Choose **Services** **&rarr;** **Instances and Subscriptions** on the left.
401402

@@ -448,9 +449,10 @@ You need to assign your user to the `Launchpad_Admin` role collection, so you do
448449
13. Type in `Risk Management Site` for the site name and choose **Create**.
449450

450451
> The new site gets the `Everyone` role by default, so you don't have to assign it explicitly. The default site properties are sufficient for the purposes of this tutorial.
451-
452-
453-
## Test your SAP Launchpad site
452+
[DONE]
453+
[ACCORDION-END]
454+
---
455+
[ACCORDION-BEGIN [Step 16: ](Test your SAP Launchpad site)]
454456

455457
1. Choose **Go to site**.
456458

@@ -468,8 +470,7 @@ You have launched your `Risks` app through the SAP Launchpad service.
468470

469471
> If you choose **Go**, you will get an error because you haven't assigned a role collection to your user yet. We'll do it in the next tutorial.
470472
471-
472-
[VALIDATE_1]
473+
[DONE]
473474
The result of this tutorial can be found in the [`kyma-launchpad-service`](https://github.com/SAP-samples/cloud-cap-risk-management/tree/kyma-launchpad-service) branch.
474475

475476

0 commit comments

Comments
 (0)