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: tutorials/btp-app-cap-mta-deployment/btp-app-cap-mta-deployment.md
+1-2Lines changed: 1 addition & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -70,7 +70,6 @@ The deployment is based on MTA ( *Multi-Target Application*, sometimes also call
70
70
[ACCORDION-BEGIN [Step 2: ]((For Windows) Install make tool)]
71
71
> ### To earn your badge for the whole mission, you will need to mark all steps in a tutorial as done, including any optional ones that you may have skipped because they are not relevant for you.
72
72
73
-
74
73
The `make` tool is required by the `mbt` tool. Linux and macOS are already shipped with `make`. For Windows you can download it from the GNU Make site:
75
74
76
75
1. Go to <http://gnuwin32.sourceforge.net/packages/make.htm>.
@@ -395,4 +394,4 @@ The result of this tutorial can be found in the [`cap-mta-deployment`](https://g
> ### To earn your badge for the whole mission, you will need to mark all steps in a tutorial as done, including any optional ones that you may have skipped because they are not relevant for you.
29
+
28
30
[SAP Continuous Integration and Delivery (CI/CD)](https://help.sap.com/viewer/product/CONTINUOUS_DELIVERY/Cloud/en-US) is a service on SAP BTP, which lets you configure and run predefined continuous integration and delivery pipelines. It connects with your Git SCM repository and builds, tests, and deploys your code changes. In its user interface, you can easily monitor the status of your builds and detect errors as soon as possible, which helps you prevent integration problems before completing your development.
29
31
30
32
SAP Continuous Integration and Delivery has a ready-to-use pipeline for CAP, that is applicable to multi-target application (MTA) and Node.js based projects. It does not require you to host your own Jenkins instance and it provides an easy, UI-guided way to configure your pipelines.
@@ -178,7 +180,7 @@ If your GitHub repository is not private, you can skip this section. If your Git
178
180
179
181
1. Navigate to the **Credentials** tab in SAP Continuous Integration and Delivery.
180
182
181
-
2. Choose **+** to create credentials.
183
+
2. Choose ( + ) to create credentials.
182
184
183
185
!
184
186
@@ -218,7 +220,7 @@ If your GitHub repository is not private, you can skip this section. If your Git
218
220
[ACCORDION-END]
219
221
---
220
222
[ACCORDION-BEGIN [Step 6: ](Configure a CI/CD job)]
221
-
1. In the **Jobs** tab in SAP Continuous Integration and Delivery, choose **+** to create a new job.
223
+
1. In the **Jobs** tab in SAP Continuous Integration and Delivery, choose ( + ) to create a new job.
- You must be an administrator of the SAP S/4HANA Cloud system.
27
29
- You need to connect this system to your SAP BTP global account, if you'd like to build extension applications for your SAP S/4HANA Cloud system.
28
30
31
+
29
32
## Details
30
33
### You will learn
31
34
- How to configure your CAP application for eventing
32
35
- How to locally test your changes
33
36
- How to deploy your CAP application
37
+
38
+
39
+
To start with this tutorial use the result in the [`ext-service-s4hc-use`](https://github.com/SAP-samples/cloud-cap-risk-management/tree/ext-service-s4hc-use) branch.
40
+
34
41
---
35
42
36
43
[ACCORDION-BEGIN [Step 1: ](Configure your CAP application for eventing)]
44
+
> ### To earn your badge for the whole mission, you will need to mark all steps in a tutorial as done, including any optional ones that you may have skipped because they are not relevant for you.
45
+
37
46
CAP provides native support for emitting and receiving events. Hence, CAP applications can receive events for changes in remote systems. In CAP, the messaging follows a publish subscribe (pub/sub) model. Pub/sub means that sources publish messages and interested consumers can subscribe to receive them. This helps with scalability, decoupling of services, and robustness.
38
47
39
48
Using the Business Partner service that you added in `Step 1: Get the Business Partner service definition` from the tutorial [Add the Consumption of an External Service to Your CAP Application](btp-app-ext-service-add-consumption), you will configure the CAP application to listen and react to events from your SAP S/4HANA Cloud system. As in the previous tutorials, let's again use the example of business partners that are suppliers. So, you will use suppliers when referring to business partners. First you will add event definitions for the SAP S/4HANA events.
@@ -246,7 +255,7 @@ Currently, business partner (that is, supplier) data is stored only in the SAP S
246
255
[ACCORDION-END]
247
256
---
248
257
[ACCORDION-BEGIN [Step 3: ](Test your changes locally)]
249
-
So, you have added logic to create a new risk when an event for a newly created supplier is received.You have also added logic to update our risks when an event for an updated supplier is received from our SAP HANA Cloud system. This is achieved by listening to events from the SAP S/4HANA Cloud system.
258
+
So, you have added logic to create a new risk when an event for a newly created supplier is received.You have also added logic to update our risks when an event for an updated supplier is received from our SAP HANA Cloud system. This is achieved by listening to events from the SAP S/4HANA Cloud system.
250
259
251
260
Now simulate locally business partner creation and update, and see the results:
The result of this tutorial can be found in the [`ext-service-s4hana-consume`](https://github.com/SAP-samples/cloud-cap-risk-management/tree/ext-service-s4hana-consume) branch.
235
231
232
+
<p style="text-align: center;">Give us 55 seconds of your time to help us improve.</p>
The result of this tutorial can be found in the [`ext-service-s4hc-use`](https://github.com/SAP-samples/cloud-cap-risk-management/tree/ext-service-s4hc-use) branch.
240
237
238
+
<p style="text-align: center;">Give us 55 seconds of your time to help us improve.</p>
4. Keep the default settings for **Service** and **Plan** and choose **Create**.
441
+
6. Keep the default settings for **Service** and **Plan** and choose **Create**.
443
442
444
443
!
445
444
@@ -455,11 +454,11 @@ You need to assign your user to the `Launchpad_Admin` role collection, so you do
455
454
456
455
2. Choose your user.
457
456
458
-
4. Under **Role Collections** on the right, choose **Assign Role Collection** and assign the `Launchpad_Admin` role collection to your user.
457
+
3. Under **Role Collections** on the right, choose **Assign Role Collection** and assign the `Launchpad_Admin` role collection to your user.
459
458
460
459
!
461
460
462
-
5. Open another browser or clear your browser's cache.
461
+
4. Open another browser or clear your browser's cache.
463
462
464
463
> 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.
0 commit comments