<p>about your learning experience to help us improve.</p>

You've completed

cleanFiles/bookmap_SAP_Order_Management_-_Technical_Baseline_en-US_learning-sap-com_lsc-prod.zip (MMCP-DROPZONE) - 2024-12-17T10:36:30.000Z

Monitoring with Cloud ALM

<div id="content"><div class="parentsection"><div class="section"><div class="kalturaVideoLessonWrapper"><div aria-label="" class="kalturaVideoLessonContainer" data-testid="video" id="1_iums5d1e"></div></div></div></div><div class="parentsection"><div class="section"><img style="max-width:900px;max-height:none" class="image 1_1_landscape" title="SAP BTP cockpit interface showing destination configuration for Cloud_ALM with HTTP type and OAuth2ClientCredentials authentication." alt="SAP BTP cockpit interface showing destination configuration for Cloud_ALM with HTTP type and OAuth2ClientCredentials authentication." src="/service/media/ICOMF4_02_en-US_media/ICOMF4_02_en-US_images/ICOMF4_U2_L4_T1_001.png" tabindex="0"><div class="imageCaption"></div><div tabindex="0"><h3>Cloud ALM Connection</h3></div><div class="formalblock"></div><p tabindex="0">In this segment, we delve into the straightforward process of connecting Cloud ALM to data ingestion. The key lies in defining a Business Technology Platform (SAP BTP) destination with specific credentials.</p><p tabindex="0">Each global SAP BTP account or customer usually corresponds to a single Cloud ALM tenant.</p><p tabindex="0">By creating this SAP BTP destination with the designated credentials, data ingestion seamlessly registers itself with Cloud ALM. This not only facilitates integration but also sets the stage for efficient monitoring.</p></div></div><div class="parentsection"><div class="section"><img style="max-width:900px;max-height:none" class="image 1_1_landscape" title="Overview of SAP Integration &amp; Exception Monitoring displaying three services with their statuses and quality alerts." alt="Overview of SAP Integration &amp; Exception Monitoring displaying three services with their statuses and quality alerts." src="/service/media/ICOMF4_02_en-US_media/ICOMF4_02_en-US_images/ICOMF4_U2_L4_T1_002.png" tabindex="0"><div class="imageCaption"></div></div></div><div class="parentsection"><div class="section"><img style="max-width:900px;max-height:none" class="image 1_1_landscape" title="Dashboard showing SAP Consumer Industry Cloud integration messages with successful and inbound message statistics. Messages listed below." alt="Dashboard showing SAP Consumer Industry Cloud integration messages with successful and inbound message statistics. Messages listed below." src="/service/media/ICOMF4_02_en-US_media/ICOMF4_02_en-US_images/ICOMF4_U2_L4_T1_003.png" tabindex="0"><div class="imageCaption"></div><div tabindex="0"><h3>Cloud ALM Monitoring</h3></div><div class="formalblock"></div><p tabindex="0">Once the connection is established, the monitoring capabilities within Cloud ALM come to the forefront. The presenter guides through the Cloud ALM interface, showcasing how data ingestion appears in integration and exception monitoring. This dynamic monitoring setup allows users to track individual components or bundle them logically, providing a holistic view of system health. With a focus on the S4 system, data ingestion, and cloud integration, users can efficiently navigate through errors and success messages.</p></div></div><div class="parentsection"><div class="section"><ul style="list-style-type:disc"><li tabindex="0"><a target="_blank" href="https://support.sap.com/content/dam/support/en_us/library/ssp/alm/sap-cloud-alm/SAP_Cloud_ALM_for_Operations_Overview.pdf">SAP Cloud ALM for Operations - Introduction</a></li><li tabindex="0"><a target="_blank" href="https://support.sap.com/en/alm/sap-cloud-alm/operations/expert-portal/integration-monitoring.html?anchorId=section">Integration &amp; Exception Monitoring (sap.com)</a></li><li tabindex="0"><a target="_blank" href="https://help.sap.com/docs/DI_ICS/925366f331c54ee88e2b61ddae0be9fc/960a20e24c074add8291b819cc002075.html">Integrating with SAP Cloud ALM | SAP Help Portal</a></li><li tabindex="0"><a target="_blank" href="https://support.sap.com/en/alm/sap-cloud-alm/operations/expert-portal/integration-monitoring/calm-diics.html?anchorId=section_1064130791_c">Data Ingestion for Industry Cloud Solutions (sap.com)</a></li></ul></div></div></div>

Customizing technical baseline of SAP OMF and SAP OMSA

<div>Learn about Cloud ALM and its monitoring capabilities for technical health checks and automated error handling. Discover how it integrates with various systems and applications for efficient monitoring.<br><br># This description was auto-generated #</div>

Monitoring with  Cloud ALM

This is available on Calm Cloud ALM, so I won't go into depth, but maybe it's worthwhile spending two minutes, three minutes on Cloud ALM so you just know and all we are on the same page what we're talking about. So you already, if you are in the game for a little while, you know that Solution Manager as already in ECC or in former times had certain roles of implementation and so forth. But here we're looking for monitoring, we're looking for technical monitoring, right? So we want to do monitoring, we want to do health checks, we want to see if our application is running. So we want to do this in a kind of automated way. So we have three solutions in that area. One is called Solution Manager, which is mainly used for on-premise systems and pretty much central core. And then we have this Focused Run. It's pretty much for the still S4 processes and hybrid customers. And we have Cloud ALM for everything that is cloud and cloud native. So cloud integration, data ingestion, OMF, you name it. So these solutions will be attached to or connected to Cloud ALM and put mainly their errors in there. So it's not in first sight like business metrics to say, OK, my turnover today was like this. There we have the SIGNAVIO suite and what I learned, the SAP Steward for this kind of process. But it's more technical monitoring, right? So like I said, central infrastructure, cloud ALM, all industry cloud solutions should use cloud ALM for their monitoring purposes. So error messages should be sent to there. So the capabilities that we have is pretty much sending input in the inbound integration, sending things like alerts, events, log entries, something to Cloud ALM. Cloud ALM has these different flavors. For us, the most important here is integration exception monitoring. So we wanted to send the message to data ingestion. And data ingestion didn't receive it, because it rejected is for some data failure or whatever. Then we want to see this error. We have here something called intelligent event processing. How should we react if something like this arrives? Or we want to say, we want to notify somebody. So for example, I want to get an email or somebody who's responsible for maintaining the solution. I want to get an email if an order cannot be created in OMF, right? So I want to be notified. So I don't want to sit in front of my screen, put a stapler on F8 and see what happens. I want to be notified and only react if something happens that needs attention, right? So it can automatically create a ticket, could raise an email or, and this is also something that sometimes customers leverage if they already have some monitoring infrastructure that we send like a ticket or a push to some other application, right? But in the hard, this is this integration exception monitoring. One thing that is important in that direction is that we want to have like an end-to-end flow, right? So we have certain KPIs. We will see some screenshots later in this business process monitoring that we put also these messages in some kind of context. So we have, of course, composable ERP and modularized with cloud applications. We have a process that spans across different systems. We have an S4 system that sends data to integration suite, which sends data to data ingestion, which sends data to OMF. So it is important to have one central point where we can monitor all this data flow. And with this end-to-end monitoring, what Cloud ALM does is something which is called an SAP passport ID. So it would get for some document, for example, that is sent like a correlation ID. And all these components, if they're connected to CAR, need to be able to use this correlation ID to use this for every alert that they send, right? So I send an order to OMF. I use this correlation ID. Then when the order is sent to the fulfillment request, it's sent to S4. If something happens in S4 and I want to raise an error, I use this correlation ID again. So we can see something that especially this one document had an issue in this component and maybe typically stops or it doesn't stop because it's somehow continued, but there's something that needs attention. So we have along this process, maybe something where we say, okay, this message made it through here, arrived here, but it was a process here, so that we know what the process flow hit as systems, as applications, and where an error arised. So this is typically what we address with Cloud ALM, that we can see errors, that it can be react to errors that will be notified. So we can define who should be notified on what, and how messages correlate. And we can create something which is called business process only, where we can say, we want to put together data ingestion with these and these artifacts and data integration and cloud integration. Because cloud integration serves many, maybe 200 interfaces. But in my specific process, as I am responsible for the data that is sent from S4 to data ingestion and to answer. I am responsible for only part of the cloud integrations, only if certain artifacts are used. So I can set something up where, say, I have here this business service. And this is comprised of S4 for certain artifacts or for certain elements, data ingestion, if the artifact name or my iflow has this and this name that is coming up. And other messages are maybe not my responsibility. And I want to see errors from data ingestion. So I can bundle this process chain in a business service and then see monitoring messages just for this abstract of everything that happens in the system. So this is maybe just as a quick one on Kalm and how it's, oops, sorry, and how it's supposed to work. So let's jump back to this unit four here. All right, so monitoring with Cloud ALM. So what it takes to connect Cloud ALM to a data ingestion to Cloud ALM is pretty simple. You just have to define a BTP destination with that name. And this time, this client credentials is the one. As soon as you get one BTP application or cloud application from SAP, you get one Cloud ALM tenant. Here, we don't talk about one tenant test dev product. Normally, you get for one global BTP account or even for the customer, just exactly one Cloud ALM tenant. So you would connect a test tenant, a productive tenant, always to the same Cloud ALM. So here, you have then also in this BTP tenant where Cloud ALM runs. You have then, of course, an instance for Cloud ALM. And there you have a service key. And these credentials from that service key, that is what you enter in the sub-account in which, for example, data ingestion runs or is deployed. Then you create this B destination, Cloud ALM, with this and this credentials. And then data ingestion will register itself. As soon as it finds this BTP destination, It will register itself with Cloud ALM. And then in Cloud ALM, you see the system coming up. So here, for example, I have data ingestion tenant that shows up in this integration and exception monitoring. And this is what I said earlier. You can, of course, monitor the individual components, applications, or you can bundle them here in some kind of process, where I say, OK, there is a logical unit with my S4, with my data ingestion, with my integration suite, with my cloud integration. And then if you go inside these errors, for example, here, you would then see, OK, I have messages here for data ingestion. The object type is my product replications. And you would see here that all requested were completed. So for some applications, you don't necessarily only have errors. Sometimes you have also success messages. And this is where you would go to, to see, okay, if everything is up and running for my data ingestion and my integration. Right. So this is pretty much what the monitoring then looks like. And in the configuration of the monitoring, then you can set something up like notifications and so forth. And this business services where you bundle certain things together. So I, for example, always receive an email if in our OMF an order cannot be created because unknown article or stuff like that. Then I get an email and yeah, if you are, if you care about these issues and you're happy that you get an email, then you don't have to actively look into the application. Right. So here are some links that we will share. So there is a data ingestion setup guide specifically for connecting to Khan. And typically with Cloud ALM, you always have two links. One is the help link of the application. And in, maybe we can quickly call that link. And there is, in Cloud ALM, there is always a guide in this expert portal here, where you would see some information here. Sorry, the window handling sometimes. So you would see here data ingestion for industry cloud in the support site for Cloud ALM in this kind of expert portal. You can see then here, OK, what does it take? What do I have to do? And here is a link to the help to set up the data ingestion for industry cloud solutions for this Cloud ALM connection. Right, and everything that you need to know about Cloud ALM is also available here. So here in this expert portal, you see the supported application. You see some capabilities, and there's even almost every time a how-to video, how to connect, and how to configure certain stuff. So that's quite nice.