- SAP Managed Tags:
SAP Cloud ALM has been used in the past for SAP Cloud projects as a project management tool for implementations but we also have a different side of this tool i.e. SAP Cloud ALM for Operations where one can setup integration monitoring against apps such as S/4HANA Cloud etc. If you are interested in learning about SAP Cloud ALM in general, please check out this link but for our purpose, the focus of this blog is to help you learn and understand how to setup SAP Cloud ALM Integration Monitoring for S/4HC 2108 Edition.
.
So, let’s dig into this setup and see what it takes for us to integrate S/4HANA Public Cloud to monitor OData and SOAP integrations. Afterwards you can learn about how to setup email alerts through SAP Cloud ALM Integration Monitoring in Part 2 of this blog series.
Reference(s):
Prerequisites:
To start things off, you will need to download the service key from the instance in your SAP Cloud ALM subaccount. To do this you will need to Navigate to your instances – Global Account: SAP Cloud ALM > CALM Subaccount > Cloud Foundry > Instances
After you have navigated to the instance, there should be a service key already created (If not you can create a new one) for your instance. Download that service key by clicking on it and select “Download”. Store the downloaded service key in an accessible location because it will be used in the S/4HANA Cloud setup steps.
You will need to set up all the required Communications on S/4HANA Cloud, and to do this you will need to navigate to the Communication Management section.
After you do that you will see all the Communication Management Apps on S/4HANA Cloud but for our scenarios we will only be using 2 apps (Shown above) – Communication Systems & Communication Arrangement.
Communication System
After the new Communication System opens up use the “endpoints” in the service key to fill in the “Host Name” and make sure the Port is set to 443. NOTE: You must ensure you remove “https://“ and “/api” or you will receive an error
Scroll down to the OAuth 2.0 Settings and fill in the “Token Endpoint” with “url” from your service key
Side Note: Ensure you add "/oauth/token" at the end of your OAuth 2.0 Client ID (Client ID).
Furthermore, scroll down to Users for Outbound Communication and click the “+” to create a new user. Choose “OAuth 2.0” as the Authentication Method and then fill in the “Client ID” and “Client Secret” fields with the appropriate information from the Service Key.
After you and have finished creating the outbound user save the Communication System and then you will move on to creating the Communication Arrangement.
Communication Arrangement
Now I want you back out to the Communication Management view and navigate to the Communication Arrangement App.
After doing that you can save the Communication Arrangement and navigate to your SAP Cloud ALM tenant for the last portion of this setup.
In this section of the SAP Cloud ALM Integration Monitoring setup, you will need to select your scope and services from the Integration & Exception Monitoring App. This App will be under SAP Cloud ALM for Operations section in your SAP Cloud ALM tenant.
Here you will need to select your scope by clicking on the bullseye button and then selecting the services you want you want to monitor
After selecting the services from the scope selection, you will need to turn on those services selected from the Configuration panel. To do that click the rack-wheel in the top right corner of the panel
You will only see the services you have previously selected in the configuration panel so all you need to do here is turn those services ON.
Once that is done alerts will begin to come through and you can check those alerts by clicking on your service in the monitoring screen then the type of message/error and the message/error in that order.
After executing all the steps shown above, your SAP Cloud ALM system should have Integration Monitoring up and running.
In conclusion, this blog exposed you to 3 SAP applications namely — SAP BTP Cockpit, SAP S/4HANA Cloud and SAP Cloud ALM. On SAP BTP Cockpit, you retrieved your service key then created all the required communications on S/4HANA Cloud using your service key, Afterwards, you went over to the SAP Cloud ALM to select and turn on the services you wish to monitor. This feature is very beneficial today due to the everchanging requirements customers for for logging, tracking, auditing, and monitoring.
I hope this blog helps you gain maximum customer satisfaction and knowledge about the tool. Please like and share my blog and any feedback in the comments will be appreciated. Thank you.
Manny
PS: I’d like to give a special shoutout to my fellow Integrations colleagues who helped with this fabian.dias & jacobmoore#overview
.
So, let’s dig into this setup and see what it takes for us to integrate S/4HANA Public Cloud to monitor OData and SOAP integrations. Afterwards you can learn about how to setup email alerts through SAP Cloud ALM Integration Monitoring in Part 2 of this blog series.
Reference(s):
- SAP Cloud ALM Integration Monitoring Setup - https://support.sap.com/en/alm/sap-cloud-alm/operations/expert-portal/setup-managed-services/setup-s...
- SAP Cloud ALM Landing page - https://support.sap.com/en/alm/sap-cloud-alm.html
Prerequisites:
- Ensure SAP Cloud ALM has been properly provisioned and has an active SAP Cloud ALM Global Account
- Ensure you are added to the org for the SAP Cloud ALM Global Account and Subaccount
- Ensure you have assigned yourself the appropriate roles on SAP BTP Cockpit
- On the Global account, assign yourself the administrator role – Global Account: SAP Cloud ALM > Members > Add Members > choose “account.sap.com” then enter your ID and save
- On the Subaccount, assign yourself the administrator role – Global Account: SAP Cloud ALM > CALM Subaccount > Security > Administrators > Add Administrators > choose “sap.ids”, check “User & Role Administrator” then enter your email and save
- Assign yourself Org Manager & Org Auditor roles – Global Account: SAP Cloud ALM > CALM Subaccount > Cloud Foundry > Org Members > Add Members > Choose “sap.ids”, select “Org manager” & “Org Auditor”, enter your email and save
- Assign yourself the Space Developer role – Global Account: SAP Cloud ALM > CALM Subaccount > Cloud Foundry > Spaces > select the space already created > Members > Add Member > Choose “sap.ids”, select “Space Developer”, enter your email and save
SAP BTP Cockpit
To start things off, you will need to download the service key from the instance in your SAP Cloud ALM subaccount. To do this you will need to Navigate to your instances – Global Account: SAP Cloud ALM > CALM Subaccount > Cloud Foundry > Instances
After you have navigated to the instance, there should be a service key already created (If not you can create a new one) for your instance. Download that service key by clicking on it and select “Download”. Store the downloaded service key in an accessible location because it will be used in the S/4HANA Cloud setup steps.
S/4HANA Cloud (Rel. 2108)
You will need to set up all the required Communications on S/4HANA Cloud, and to do this you will need to navigate to the Communication Management section.
After you do that you will see all the Communication Management Apps on S/4HANA Cloud but for our scenarios we will only be using 2 apps (Shown above) – Communication Systems & Communication Arrangement.
Communication System
- Navigate to the Communication System App and create a new Communication System. (If one doesn’t already exist and if one does exist skip to the communication Arrangement Section)
- To check if one is already made for your SAP Cloud ALM tenant search for the endpoint provided from the service key previously downloaded in the Host Name field.
- Following that Enter the appropriate System ID and System name you would like your system to have.
After the new Communication System opens up use the “endpoints” in the service key to fill in the “Host Name” and make sure the Port is set to 443. NOTE: You must ensure you remove “https://“ and “/api” or you will receive an error
Scroll down to the OAuth 2.0 Settings and fill in the “Token Endpoint” with “url” from your service key
Side Note: Ensure you add "/oauth/token" at the end of your OAuth 2.0 Client ID (Client ID).
Furthermore, scroll down to Users for Outbound Communication and click the “+” to create a new user. Choose “OAuth 2.0” as the Authentication Method and then fill in the “Client ID” and “Client Secret” fields with the appropriate information from the Service Key.
After you and have finished creating the outbound user save the Communication System and then you will move on to creating the Communication Arrangement.
Communication Arrangement
Now I want you back out to the Communication Management view and navigate to the Communication Arrangement App.
- Create a new Communication Arrangement by clicking “New” but ensure you check if there is already one created to avoid duplicates
- Check if there is already an existing one by typing “0527” in the search field
- Choose the scenario “SAP_COM_0527” which is the Communication Arrangement for SAP Cloud ALM for operations - Application Monitoring Push Integration
- After you do what was instructed above select the Communication System previously created in the Communication system field
- Scroll down to “Additional Properties and Choose the properties relevant to your use case
- The Outbound Communication section is automatically filled up so you can scroll down to “Outbound Services”. Fill in “/” and press Enter for the Path field, it will propagate the Service URL field. Following that under “Job Execution Details” set the “Job status” to Active and set it to run every minute (1)
After doing that you can save the Communication Arrangement and navigate to your SAP Cloud ALM tenant for the last portion of this setup.
SAP Cloud ALM
In this section of the SAP Cloud ALM Integration Monitoring setup, you will need to select your scope and services from the Integration & Exception Monitoring App. This App will be under SAP Cloud ALM for Operations section in your SAP Cloud ALM tenant.
Here you will need to select your scope by clicking on the bullseye button and then selecting the services you want you want to monitor
After selecting the services from the scope selection, you will need to turn on those services selected from the Configuration panel. To do that click the rack-wheel in the top right corner of the panel
You will only see the services you have previously selected in the configuration panel so all you need to do here is turn those services ON.
Once that is done alerts will begin to come through and you can check those alerts by clicking on your service in the monitoring screen then the type of message/error and the message/error in that order.
After executing all the steps shown above, your SAP Cloud ALM system should have Integration Monitoring up and running.
In conclusion, this blog exposed you to 3 SAP applications namely — SAP BTP Cockpit, SAP S/4HANA Cloud and SAP Cloud ALM. On SAP BTP Cockpit, you retrieved your service key then created all the required communications on S/4HANA Cloud using your service key, Afterwards, you went over to the SAP Cloud ALM to select and turn on the services you wish to monitor. This feature is very beneficial today due to the everchanging requirements customers for for logging, tracking, auditing, and monitoring.
I hope this blog helps you gain maximum customer satisfaction and knowledge about the tool. Please like and share my blog and any feedback in the comments will be appreciated. Thank you.
Manny
PS: I’d like to give a special shoutout to my fellow Integrations colleagues who helped with this fabian.dias & jacobmoore#overview
