
This blog is the third and final part in a three part series that introduces how to enable SAP Cloud ALM for your Integration and Exception Monitoring needs. This first blog will discuss how to provision SAP Cloud ALM, the second blog will discuss connecting SAP Integration Suite to SAP Cloud ALM, and the third blog will discuss connecting third party incident management to SAP Cloud ALM.
First Blog - https://community.sap.com/t5/technology-blogs-by-members/sap-cloud-alm-provisioning/ba-p/13708430
Second Blog - https://community.sap.com/t5/technology-blogs-by-members/configuring-sap-cloud-alm-for-integration-s...
Third Blog - This Blog
If there are any updates to either these messages, or exceptions, specific events can be triggered which can send an email, start a custom operation flow (such as Build Process Automation), ticket to an external vendor (such as ServiceNow), or send a chat notification in external team chats (such as Microsoft Teams). These all provide different functionality but require a similar process in setup (aside from emails).
To access these, go to the Integration Suite Tenant and select Edit Configuration.
Select the Integration Suite Service you wish to configure the events for.
You can now enable external tickets, MS Teams notifications, alerts and other events, depending on the event type you have selected. These events have to be configured individually, but the general process is described below.
Event Types:
Erroneous Integration Artifact – An integration failed to deploy
Erroneous CPI Message Detected(Single) – A Integration Message Failed or was escalated
Erroneous CPI Message Detected(Group) – An Integration Message, linked with other Integration Messages, Failed or was escalated
Prerequisites
For external ticketing, the API call to the third party services must be configured before connecting to an event. The steps to do so are as follows.
Here we will need to create a subscription, but this requires configuring both a webhook, and mapping for the external API call. Both of these configurations are on the left hand side of the page.
This will be the API path from the Service Endpoint you configured earlier
Field | Value |
Name | Appropriate Name |
Path | Specific API Path after configured Service Endpoint |
Resource Type | Choose Appropriate from Drop Down |
Destination Source | Select Appropriate Type |
Destination ID | Select appropriate Service Endpoint |
This mapping will shape the Event information into the API call request body, and will map out a JSON request
There are multiple default mapping options available (such as to the Service Now Events, and MS Teams), but they can also be customised.
Refer to this SAP community blog post about Advanced Mapping.
Once this is saved with the configured webhook and mapping, the subscription is now configured correctly. If there are any issues with the API, the Console on the left-hand side of the screen can be used to troubleshoot the issue.
After enabling this option, you will have configured the events to either create an external ticket, or send emails on an event. This process is also similar for the chat notification, where the subscription created would apply to MS Teams.
Thanks for reading!
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
6 | |
5 | |
4 | |
4 | |
3 | |
3 | |
3 | |
3 | |
3 | |
3 |