Skip to content

Commit 4386170

Browse files
Change to "scenario" (#22896)
* Updated package name in screenshot * Force to publish new graphic * Added link; no other change * Change to "scenario" * Hid info
1 parent c6188a4 commit 4386170

File tree

5 files changed

+45
-25
lines changed

5 files changed

+45
-25
lines changed

tutorials/abap-environment-monitoring-calm-health-monitoring/abap-environment-monitoring-calm-health-monitoring.md

Lines changed: 45 additions & 25 deletions
Original file line numberDiff line numberDiff line change
@@ -18,8 +18,8 @@ author_profile: https://github.com/julieplummer20
1818
- Access to the Fiori app **Health Monitoring**
1919

2020
## You will learn
21-
- How to configure outbound communication from your SAP BTP ABAP Environment using the communication arrangement **`SAP_COM_0276`**
22-
- How to configure communication from your SAP BTP ABAP Environment instance to the SAP Cloud ALM service using the communication arrangement **`SAP_COM_0527`**
21+
- How to configure outbound communication from your SAP BTP ABAP Environment using the communication scenario **`SAP_COM_0276`**
22+
- How to configure communication from your SAP BTP ABAP Environment instance to the SAP Cloud ALM service using the communication scenario **`SAP_COM_0527`**
2323
- How to configure the use cases you want for SAP Cloud ALM
2424

2525

@@ -33,8 +33,11 @@ For more information, see SAP Help Portal: [Integration in Central Monitoring an
3333

3434
Throughout this tutorial, objects name include a prefix, such as **`Zxx`** or suffix, such as **`XXX`**. Always replace this with your group number or initials.
3535

36-
<!-- border -->![step0-overview](step0-overview.png)
37-
<!-- border -->![step0-overview2](step0-overview2.png)
36+
<!-- border -->
37+
![step0-overview](step0-overview.png)
38+
39+
<!-- border -->
40+
![step0-overview2](step0-overview2.png)
3841

3942
---
4043

@@ -44,78 +47,95 @@ In the BTP Cockpit, you need to create a destination service in your BTP subacco
4447

4548
1. Navigate to your **Space**, choose **Instances**, then choose **Create**.
4649

47-
<!-- border -->![step1a-navigate-to-space-etc](step1a-navigate-to-space-etc.png)
50+
<!-- border -->
51+
![step1a-navigate-to-space-etc](step1a-navigate-to-space-etc.png)
4852

4953
2. Enter the following, then choose **Create**.
5054

5155
- Service: **Destination**
5256
- Plan: **Lite**
5357
- Instance Name: e.g. **`DST`**
5458

55-
<!-- border -->![step1a-create-destinations-service](step1a-create-destinations-service.png)
59+
<!-- border -->
60+
![step1a-create-destinations-service](step1a-create-destinations-service.png)
61+
62+
3. Create a service key for your SAP Cloud ALM service and download it; you will need it later - that is, the SAP Cloud ALM service mentioned in the prerequisites above.
63+
64+
<!-- border -->
65+
![step1c-calm-service-already-created](step1c-calm-service-already-created.png)
5666

57-
3. Create a service key for your SAP Cloud ALM service and download it; you will need it later.
5867

5968
4. Create a new service key for your SAP BTP ABAP Environment and download it; you will need it later.
6069

61-
<!-- border -->![step1c-create-service-key-for-steampunk](step1c-create-service-key-for-steampunk.png)
70+
<!-- border -->
71+
![step1c-create-service-key-for-steampunk](step1c-create-service-key-for-steampunk.png)
6272

6373

64-
### Set up SAP Cloud ALM service
74+
### Configure destination
6575

6676
In the BTP Cockpit, you need to create a destination to SAP Cloud ALM if you have not already done so.
6777

6878
1. Navigate to your **Subaccount** and choose **Destinations > New Destination**.
6979

70-
<!-- border -->![step1c-navigate-to-destinations](step1c-navigate-to-destinations.png)
80+
<!-- border -->
81+
![step1c-navigate-to-destinations](step1c-navigate-to-destinations.png)
7182

7283
2. Configure the destination to your SAP Cloud ALM service using the credentials in the service key (from step 1.3).
7384

74-
<!-- border -->![step1b-destination-to-calm](step1b-destination-to-calm.png)
75-
76-
3. Choose scenario **`SAP_COM_0276`**, paste the service key of your destination service (from step 1.4), then choose **Create**.
77-
78-
<!-- border -->![step2c-comm-arr-create](step2c-comm-arr-create.png)
79-
85+
<!-- border -->
86+
![step1b-destination-to-calm](step1b-destination-to-calm.png)
8087

8188

8289
### Create Communication Arrangement for Destination Service Integration (SAP_COM_0276)
8390

8491
1. Logon to your SAP BTP ABAP Environment as Administrator and choose the app **Communication Arrangements**.
8592

86-
<!-- border -->![step2a-comm-arr](step2a-comm-arr.png)
93+
<!-- border -->
94+
![step2a-comm-arr](step2a-comm-arr.png)
8795

8896
2. Choose **New**.
8997

90-
<!-- border -->![step2b-comm-arr-new](step2b-comm-arr-new.png)
98+
<!-- border -->
99+
![step2b-comm-arr-new](step2b-comm-arr-new.png)
100+
101+
3. Choose scenario **`SAP_COM_0276`**, paste the service key of your destination service (from step 1.4), then choose **Create**.
102+
103+
<!-- border -->
104+
![step2c-comm-arr-create](step2c-comm-arr-create.png)
91105

92106

93107

94108
### Create Communication Arrangement for Application Monitoring (SAP_COM_0527)
95109

96110
1. Again, choose **New**, then choose **Create**.
97111

98-
<!-- border -->![step3a-comm-arr-create-SAP_COM_0527](step3a-comm-arr-create-SAP_COM_0527.png)
112+
<!-- border -->
113+
![step3a-comm-arr-create-SAP_COM_0527](step3a-comm-arr-create-SAP_COM_0527.png)
99114

100115
2. Create a New **Communication System**.
101116

102-
<!-- border -->![step3b-comm-system-new-cutout](step3b-comm-system-new-cutout.png)
117+
<!-- border -->
118+
![step3b-comm-system-new-cutout](step3b-comm-system-new-cutout.png)
103119

104-
3. From the dropdown list, choose the **Name** for your SAP Cloud ALM service, that you configured in step 1.3 - in this example, **`ABAPK8S_CALM`**.
120+
3. From the dropdown list, choose the **Name** for your SAP Cloud ALM service, that you configured in step 3.2.
105121

106-
<!-- border -->![step3c-comm-system-name](step3c-comm-system-name.png)
122+
<!-- border -->
123+
![step3c-comm-system-name](step3c-comm-system-name.png)
107124

108125
4. Choose the use cases you want to enable.
109126

110-
<!-- border -->![step3d-configure-use-cases](step3d-configure-use-cases.png)
127+
<!-- border -->
128+
![step3d-configure-use-cases](step3d-configure-use-cases.png)
111129

112130
5. Configure the job execution details as follows and choose **Save**, then save the communication arrangement.
113131

114-
<!-- border -->![step3e-configure-job-exec-details](step3e-configure-job-exec-details.png)
132+
<!-- border -->
133+
![step3e-configure-job-exec-details](step3e-configure-job-exec-details.png)
115134

116135
Your SAP BTP ABAP environment is registered in your SAP Cloud ALM instance. However, it could take **up to one hour** before the first monitoring data is pushed to your service.
117136

118-
<!-- border -->![step3e-result-calm-health-monitoring](step3e-result-calm-health-monitoring.png)
137+
<!-- border -->
138+
![step3e-result-calm-health-monitoring](step3e-result-calm-health-monitoring.png)
119139

120140

121141
### Test yourself
Loading
Loading

0 commit comments

Comments
 (0)