Skip to content

Commit 2adafa4

Browse files
iwonahahniwonahahn
authored
Update btp-app-kyma-deploy-application.md
1 parent cca5971 commit 2adafa4

1 file changed

Lines changed: 14 additions & 21 deletions

File tree

‎tutorials/btp-app-kyma-deploy-application/btp-app-kyma-deploy-application.md‎

Lines changed: 14 additions & 21 deletions
Original file line numberDiff line numberDiff line change
@@ -71,10 +71,8 @@ The configuration for XSUAA is read from the `xs-security.json` file that was cr
7171
---
7272
[ACCORDION-BEGIN [Step 2: ](Build docker images)]
7373

74-
[DONE]
75-
[ACCORDION-END]
76-
---
77-
[ACCORDION-BEGIN [Step 3: ](Set the environment variable for the container registry)]
74+
You need to set the environment variable for the container registry.
75+
7876
1. Open a terminal and run the following command:
7977

8078
```
@@ -86,7 +84,7 @@ The configuration for XSUAA is read from the `xs-security.json` file that was cr
8684
[DONE]
8785
[ACCORDION-END]
8886
---
89-
[ACCORDION-BEGIN [Step 4: ](CAP build)]
87+
[ACCORDION-BEGIN [Step 3: ](CAP build)]
9088
1. Execute the following command in your project folder:
9189
9290
```Shell/Bash
@@ -107,7 +105,7 @@ The configuration for XSUAA is read from the `xs-security.json` file that was cr
107105
[DONE]
108106
[ACCORDION-END]
109107
---
110-
[ACCORDION-BEGIN [Step 5: ](Build CAP service)]
108+
[ACCORDION-BEGIN [Step 4: ](Build CAP service)]
111109
1. Run the following command:
112110
113111
```Shell/Bash
@@ -125,7 +123,7 @@ The configuration for XSUAA is read from the `xs-security.json` file that was cr
125123
[DONE]
126124
[ACCORDION-END]
127125
---
128-
[ACCORDION-BEGIN [Step 6: ](Build DB deployer)]
126+
[ACCORDION-BEGIN [Step 5: ](Build DB deployer)]
129127
1. Run the following command:
130128
131129
```Shell/Bash
@@ -143,7 +141,7 @@ The configuration for XSUAA is read from the `xs-security.json` file that was cr
143141
[DONE]
144142
[ACCORDION-END]
145143
---
146-
[ACCORDION-BEGIN [Step 7: ](Push docker images)]
144+
[ACCORDION-BEGIN [Step 6: ](Push docker images)]
147145
Now that we've build the docker images, let's push them to the container registry.
148146
149147
1. Make sure you're logged in to your container registry:
@@ -162,7 +160,7 @@ Now that we've build the docker images, let's push them to the container registr
162160
[DONE]
163161
[ACCORDION-END]
164162
---
165-
[ACCORDION-BEGIN [Step 8: ](Deploy)]
163+
[ACCORDION-BEGIN [Step 7: ](Deploy)]
166164
1. Deploy your app:
167165
168166
```Shell/Bash
@@ -179,14 +177,13 @@ Now that we've build the docker images, let's push them to the container registr
179177
180178
If the error message "no healthy upstream" is shown, wait a few seconds and try again.
181179
182-
6. When you choose the **Mitigation** or **Risk** service entity, you will see an error message:
180+
4. When you choose the **Mitigation** or **Risk** service entity, you will see an error message:
183181
184182
!![CAP 401 error](cap_mta_403_error.png)
185183
186-
187184
The service expects a so called `JWT` (JSON Web Token) in the HTTP `Authorization` header that contains the required authentication and authorization information to access the service. In the next tutorial, you will deploy the SAP Fiori UIs, so that you can access your UIs from SAP Fiori Launchpad. The Launchpad will trigger the authentication flow to provide the required token to access the service.
188185
189-
7. List installed helm charts:
186+
5. List installed helm charts:
190187
191188
```Shell/Bash
192189
helm list
@@ -199,18 +196,14 @@ Now that we've build the docker images, let's push them to the container registr
199196
cpapp risk-management 5 yyyy-mm-dd time timezone deployed cpapp-1.0.0 1.0.0
200197
```
201198
202-
[DONE]
203-
[ACCORDION-END]
204-
---
205-
[ACCORDION-BEGIN [Step 9: ](Troubleshooting)]
206-
The Helm chart starts a job that deploys the database content and a deployment with the CAP service. After successful execution, the job is deleted.
207-
199+
> Troubleshooting:
200+
> The Helm chart starts a job that deploys the database content and a deployment with the CAP service. After successful execution, the job is deleted.
208201
In case you encounter an error during the deployment process, follow the instructions to troubleshoot.
209202
210203
[DONE]
211204
[ACCORDION-END]
212205
---
213-
[ACCORDION-BEGIN [Step 10: ](Check your database deployment)]
206+
[ACCORDION-BEGIN [Step 8: ](Check your database deployment)]
214207
```
215208
kubectl get jobs
216209
```
@@ -262,7 +255,7 @@ This is helpful if the pod couldn't be started.
262255
[DONE]
263256
[ACCORDION-END]
264257
---
265-
[ACCORDION-BEGIN [Step 11: ](Check SAP HANA cloud trusted IP addresses)]
258+
[ACCORDION-BEGIN [Step 9: ](Check SAP HANA cloud trusted IP addresses)]
266259
A possible error cause is that your SAP HANA Cloud instance doesn't allow your Kyma's cluster IP address.
267260
268261
You can check and adjust the settings for [the trusted source IP addresses](https://help.sap.com/docs/HANA_CLOUD/9ae9104a46f74a6583ce5182e7fb20cb/0610e4440c7643b48d869a6376ccaecd.html) in SAP HANA Cloud Central.
@@ -278,7 +271,7 @@ The command takes a few second to execute and will print a JSON object with an I
278271
[DONE]
279272
[ACCORDION-END]
280273
---
281-
[ACCORDION-BEGIN [Step 12: ](Check your CAP service)]
274+
[ACCORDION-BEGIN [Step 10: ](Check your CAP service)]
282275
If the deployment was successful, you should see the running CAP service in the list of pods:
283276
284277
```

0 commit comments

Comments
 (0)