You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: managed-html5-runtime-fiori-mta/readme.md
+1-1
Original file line number
Diff line number
Diff line change
@@ -7,7 +7,7 @@
7
7
8
8
## Description
9
9
10
-
This is an example of an SAP Fiori app that is accessed by a managed application router. The SAP Fiori app is exposed to the SAP Launchpad service and is visible in the content manager of the launchpad. The app is deployed to the HTML5 Application Repository and uses the Authentication & Authorization service (XSUAA service) and the destination service.
10
+
This is an example of an SAP Fiori app that is accessed by a managed application router. The SAP Fiori app is exposed to the SAP Launchpad service and is visible in the content manager of the launchpad. The app is deployed to the HTML5 Application Repository via the Cloud Foundry environment and uses the Authentication & Authorization service (XSUAA service) and the destination service.
11
11
12
12
The web app that is contained in the `uimodule.zip` defines the following properties in the `manifest.json` file. Otherwise, the correspoding values in the `mta.yaml` descriptor need to be updated as well.
# Basic SAPUI5 App with a Managed Application Router and a Backend Component in the Kyma Runtime
2
+
3
+
4
+
## Diagram
5
+
6
+

7
+
8
+
9
+
## Description
10
+
11
+
This is an example of an SAP Fiori app that is accessed by a managed application router and a backend component that runs in the Kyma runtime. The SAPUI5 app is exposed to an SAP Launchpad service and is visible in the content manager of the launchpad. The app is deployed to the HTML5 Application Repository via the Kyma runtime and uses the Authentication & Authorization service (XSUAA service) and the destination service.
12
+
The backend component accepts incoming requests and returns the payload of the decoded JWT token (if available) at `/be`.
13
+
14
+
15
+
16
+
As a result of deploying this `/deployment.yaml` you will get 2 pods:
17
+
18
+
1.`html5appdeployer` - an html5-app-deployer library based application that uploads favorites html5 application to HTML5 Application Repository and generates the required destinations.
19
+
2.`backend` - a simple nodejs server that returns the JWT forwarded by the managed application router
20
+
21
+
In addition the following service instances are created:
22
+
- xsuaa/application service instance bound to backend container
23
+
- html5-apps-repo/app-host service instance bound to html5appdeployer container (used to upload content to html5 repo)
24
+
- destination/lite instance - this is for future use - (automatically generate destination configurations on instance level)
25
+
26
+
## Download and Deployment
27
+
1. Have an account for a Docker registry and log in the the docker CLI (e.g. [DockerHub](https://docs.docker.com/docker-hub/))
28
+
1.[Install the Kubernetes Command Line Tool](https://developers.sap.com/tutorials/cp-kyma-download-cli.html)
29
+
1. Subscribe to the [launchpad service](https://developers.sap.com/tutorials/cp-portal-cloud-foundry-getting-started.html) if you haven't done so before.
30
+
2. Build and upload the docker image of the backend component
31
+
```
32
+
cd kyma-html5-repo-example/backend
33
+
docker build -t iobert/kyma-simple-backend .
34
+
docker push iobert/kyma-simple-backend
35
+
```
36
+
2. Build and upload the docker image of the html5 app deployer
37
+
```
38
+
cd ../html5-app-deployer
39
+
docker build -t iobert/kyma-html5-app-deployer
40
+
docker push iobert/kyma-html5-app-deployer
41
+
```
42
+
4. Add your account id (e.g. "43de072btrial") to the destination which is defined in the environment variable `BACKEND_DESTINATIONS` of the [deployment descriptor](html5-app-deployer/deployment.yaml).
43
+
2. Deploy the project
44
+
```
45
+
kubectl apply -f deployment.yaml
46
+
```
47
+
48
+
2. Access the web app via the SAP BTP cockpit or assemble the URL according to the following pattern:
> You can find the destination service instance ID in the Kyma console
55
+

56
+
57
+
58
+
## Check the Result
59
+
60
+
### Check the HTML5 App
61
+
62
+
Access the URL described in [Download and Deployment](#download-and-deployment) to view the web app. You are redirected to a sign-on page before you can see the web app.
0 commit comments