Scenario introduction:

For the following end-to-end integration monitoring exercise, one part of the integrated workflow of the SAP S/4HANA Lean Procurement has been chosen. A work order is created in SAP Fieldglass and the purchase requisition is replicated to SAP S/4HANA Cloud leveraging a prebuilt integration package (SAP S/4HANA Integration with SAP Fieldglass) from SAP Business Accelerator Hub.

The relevant integration flows for the integration scenario are as follows:

Replicate Purchase Requisition from SAP Fieldglass to SAP S4HANA.Purchase Order Status Replication from SAP S4HANA to SAP Fieldglass.Replicate Purchase Order from SAP Fieldglass to SAP S4HANA.

See also the documentation of the process flow Purchase Order and Invoicing.
Below you see an overview of the integration scenario,

overview of the integration scenario

Business services are the foundation of the E2E monitoring. They connect all the involved systems and messages. Now first, we need to create business service. In Cloud ALM tenant, on right hand side, we can see Managed Components-> Business Services. By clicking configure option, we can add business services.

add Business Service

After adding business service, we can configure this.
Configuration of business services involves the following steps:

Configure services and systems that are part of the business service.Configure filters for data collection. Filters make sure that only certain messages are considered as part of the business service. Note: You can create business service filters based only on messages. Exceptions are currently not supported in business services.Set up events.

We have now added services which are need for this business scenario which are SAP Integration Suite, SAP S/4HANA and SAP Fieldglass. Also, Filtering added for all AIF messages. And event details for filter have been activated.

Configuration for Business Services

And now we can also decide path as shown below, and we can proceed by saving all the information.

path for integration scenario

Now Let’s bring the end-to-end business scenario ExternalWorkforce into the scope.

SAP Cloud ALM tenant for Integration and Exception Monitoring

Filter for Business Services.If you click on Go in the upper right corner for filtering, then you can select the ExternalWorkforce scenario.Apply the selection.The card in the overview page should look like below,

Select scope for Monitoring

Overview on business scenario topology

The overview page offers a central view that shows the status of integration scenarios and services that are in scope. It provides a first indicator where faulty messages or in case of Cloud Integration deployment exceptions occurred. In this blog post, you will get insights of the used color-coding and the functionalities this page is offering.

Note: Each card in the overview page represents a service or a business scenario. The left-side color reflects the overall status for the selected time. You may identify the scenarios by the boxes of the involved services The screenshot below is taken from a demo tenant and shows an extended view covering a mix of business services and cloud services.

In the screenshots below we are focusing on the card of the business scenario ExternalWorkforce.

card of the business scenario ExternalWorkforce

By clicking the ‘Quality’ icon, you can check whether the data collection is running successfully for the involved services.
Within the popup that shows up click on the Cloud Integration service. The status of monitoring messages and integration artifact exceptions is displayed separately from each other.In case of raised alerts, you would be able to jump directly to the embedded alerting by clicking on the number of alerts in the footer of each card.Check the status of business service events with the time-calendar-icon
It shows the events from the Cloud Availability Center. If maintenance, disruption or degradation events raise up for a service it will be displayed here.By clicking on the Star icon, you can set an entry to your favorite ones and track them more easily also in cases there are not selected to your scope.By clicking on the information icon (i), you can get an understanding of the color-coding of a service’s status.

The color of the left side of each card is the overall status of the integration scenario or the service. It depends on the selected time frame.

Inside of a card you may distinguish:

In case of monitoring a single cloud service the status of monitoring messages is separated from monitoring exceptions. Clicking on the red bar you may get directly to the list of faulty messages. Same for the others.In case of monitoring an integration scenario you see the status of each involved service by its color.

1. Click on the three dots and select Go to Details.

Go to Details of Business Scenario

2. Oversee the numbers in the topology view of the ExternalWorkforce scenario: 32 messages have been exchanged, 30 exceptions have been detected, and 5 alerts have been raised.

Topology View

Watch all SAP Integration Suite messages of an integration scenario

Here you will see all messages exchanged via SAP Integration Suite for the integration scenario ExternalWorkforce in a selected time frame. If you click on the Cloud Integration node MyCPI and to SAP Integration Suite Messages on the right side, then this will drill down to the next level.

Topology View

The SAP Integration Suite messages page shows the exchanged messages

exchange message view

In the header section some stats are displayed and the integration flows that are relevant for the ExternalWorkforce scenario show up:

Replicate Purchase Requisition from SAP Fieldglass to SAP S4HANAPurchase Order Status Replication from SAP S4HANA to SAP Fieldglass_ERSReplicate Purchase Order from SAP Fieldglass to SAP S4HANA

Below you see the list of messages transferred in the selected time frame and for each message beyond the message status also the package name, artifact name, and other fields.
Erroneous messages are highlighted in red. As you can see one message sent by the SAP Fieldglass instance has failed, others have completed successfully.

Check failed message alerts

Here you will watch alerts that have been raised for failed messages.
1. If you click on the exclamation mark icon! in the left-side navigation and navigate to the Alerting page, then you can select the Erroneous CPI Messages Detected alert for the Cloud Integration service MyCPI if any.

Alert Inbox

Highlighted you see some information from SAP Integration Suite, mainly in related integration flow of this erroneous message. Also, the SAP Fieldglass tenant has sent an error message and with that raised an alert.

In the alert details page, you see all failed messages grouped together for the integration flow Replicate Purchase Requisition from SAP Fieldglass to SAP S/4HANA. Also, you can perform some actions as showed below,
Note: you might see some different messages or no messages as per your scenario.

actions possible for Alert

You’ve now monitored the integration scenario ExternalWorkforce that is sending messages from SAP Fieldglass to SAP S/4HANA Cloud mediated by the Cloud Integration capability of SAP Integration Suite. You have seen how to detect faulty messages very quickly in the overview page, also in the alerting section of Integration & Exception Monitoring along with your email inbox.

More information

Find the complete list of supported products for Health Monitoring and how to set up the application in the SAP Cloud ALM for Operations Expert Portal to get started. This page is continuously updated.

If you want to understand the comparison with other ALM tools please check out the blog post Monitoring tools for Cloud Integration capability of SAP Integration Suite.

In this blog post, we will focus on end-to-end monitoring of an integration scenario leveraging the Integration & Exception Monitoring of SAP Cloud ALM for Operations. Get experience with the monitoring of a prebuilt integration scenario ExternalWorkforce that span across the cloud applications SAP Fieldglass and SAP S/4HANA Cloud. You will be able to monitor the exchanged messages and check alerts for failed messages as well.Scenario introduction:For the following end-to-end integration monitoring exercise, one part of the integrated workflow of the SAP S/4HANA Lean Procurement has been chosen. A work order is created in SAP Fieldglass and the purchase requisition is replicated to SAP S/4HANA Cloud leveraging a prebuilt integration package (SAP S/4HANA Integration with SAP Fieldglass) from SAP Business Accelerator Hub.The relevant integration flows for the integration scenario are as follows:Replicate Purchase Requisition from SAP Fieldglass to SAP S4HANA.Purchase Order Status Replication from SAP S4HANA to SAP Fieldglass.Replicate Purchase Order from SAP Fieldglass to SAP S4HANA.See also the documentation of the process flow Purchase Order and Invoicing.Below you see an overview of the integration scenario,overview of the integration scenario Business services are the foundation of the E2E monitoring. They connect all the involved systems and messages. Now first, we need to create business service. In Cloud ALM tenant, on right hand side, we can see Managed Components-> Business Services. By clicking configure option, we can add business services.add Business Service After adding business service, we can configure this.Configuration of business services involves the following steps:Configure services and systems that are part of the business service.Configure filters for data collection. Filters make sure that only certain messages are considered as part of the business service. Note: You can create business service filters based only on messages. Exceptions are currently not supported in business services.Set up events.We have now added services which are need for this business scenario which are SAP Integration Suite, SAP S/4HANA and SAP Fieldglass. Also, Filtering added for all AIF messages. And event details for filter have been activated. Configuration for Business Services And now we can also decide path as shown below, and we can proceed by saving all the information.path for integration scenarioNow Let’s bring the end-to-end business scenario ExternalWorkforce into the scope.SAP Cloud ALM tenant for Integration and Exception Monitoring Filter for Business Services.If you click on Go in the upper right corner for filtering, then you can select the ExternalWorkforce scenario.Apply the selection.The card in the overview page should look like below,Select scope for Monitoring Overview on business scenario topologyThe overview page offers a central view that shows the status of integration scenarios and services that are in scope. It provides a first indicator where faulty messages or in case of Cloud Integration deployment exceptions occurred. In this blog post, you will get insights of the used color-coding and the functionalities this page is offering.Note: Each card in the overview page represents a service or a business scenario. The left-side color reflects the overall status for the selected time. You may identify the scenarios by the boxes of the involved services The screenshot below is taken from a demo tenant and shows an extended view covering a mix of business services and cloud services.In the screenshots below we are focusing on the card of the business scenario ExternalWorkforce.card of the business scenario ExternalWorkforceBy clicking the ‘Quality’ icon, you can check whether the data collection is running successfully for the involved services.Within the popup that shows up click on the Cloud Integration service. The status of monitoring messages and integration artifact exceptions is displayed separately from each other.In case of raised alerts, you would be able to jump directly to the embedded alerting by clicking on the number of alerts in the footer of each card.Check the status of business service events with the time-calendar-iconIt shows the events from the Cloud Availability Center. If maintenance, disruption or degradation events raise up for a service it will be displayed here.By clicking on the Star icon, you can set an entry to your favorite ones and track them more easily also in cases there are not selected to your scope.By clicking on the information icon (i), you can get an understanding of the color-coding of a service’s status.The color of the left side of each card is the overall status of the integration scenario or the service. It depends on the selected time frame.Inside of a card you may distinguish:In case of monitoring a single cloud service the status of monitoring messages is separated from monitoring exceptions. Clicking on the red bar you may get directly to the list of faulty messages. Same for the others.In case of monitoring an integration scenario you see the status of each involved service by its color. 1. Click on the three dots and select Go to Details.Go to Details of Business Scenario2. Oversee the numbers in the topology view of the ExternalWorkforce scenario: 32 messages have been exchanged, 30 exceptions have been detected, and 5 alerts have been raised.Topology View Watch all SAP Integration Suite messages of an integration scenarioHere you will see all messages exchanged via SAP Integration Suite for the integration scenario ExternalWorkforce in a selected time frame. If you click on the Cloud Integration node MyCPI and to SAP Integration Suite Messages on the right side, then this will drill down to the next level.Topology ViewThe SAP Integration Suite messages page shows the exchanged messagesexchange message viewIn the header section some stats are displayed and the integration flows that are relevant for the ExternalWorkforce scenario show up:Replicate Purchase Requisition from SAP Fieldglass to SAP S4HANAPurchase Order Status Replication from SAP S4HANA to SAP Fieldglass_ERSReplicate Purchase Order from SAP Fieldglass to SAP S4HANABelow you see the list of messages transferred in the selected time frame and for each message beyond the message status also the package name, artifact name, and other fields.Erroneous messages are highlighted in red. As you can see one message sent by the SAP Fieldglass instance has failed, others have completed successfully.Check failed message alertsHere you will watch alerts that have been raised for failed messages.1. If you click on the exclamation mark icon! in the left-side navigation and navigate to the Alerting page, then you can select the Erroneous CPI Messages Detected alert for the Cloud Integration service MyCPI if any.Alert InboxHighlighted you see some information from SAP Integration Suite, mainly in related integration flow of this erroneous message. Also, the SAP Fieldglass tenant has sent an error message and with that raised an alert.In the alert details page, you see all failed messages grouped together for the integration flow Replicate Purchase Requisition from SAP Fieldglass to SAP S/4HANA. Also, you can perform some actions as showed below,Note: you might see some different messages or no messages as per your scenario.actions possible for Alert You’ve now monitored the integration scenario ExternalWorkforce that is sending messages from SAP Fieldglass to SAP S/4HANA Cloud mediated by the Cloud Integration capability of SAP Integration Suite. You have seen how to detect faulty messages very quickly in the overview page, also in the alerting section of Integration & Exception Monitoring along with your email inbox. More informationFind the complete list of supported products for Health Monitoring and how to set up the application in the SAP Cloud ALM for Operations Expert Portal to get started. This page is continuously updated.If you want to understand the comparison with other ALM tools please check out the blog post Monitoring tools for Cloud Integration capability of SAP Integration Suite. Read More Technology Blog Posts by SAP articles

#SAP

#SAPTechnologyblog