End-to-End Monitoring Architecture
The following section provides details on how End-to-End Monitoring helps a user to get the details of a business transaction.
Let us consider a use case where a customer is requesting for an address change with his bank using a banking application. Here, the banking application is represented as a Third-party system. Following actions take place when the customer wants to change the address:
1. Customer raises an address change request using the client application. Client application is accessible using any device.
2. The request makes an API call to API gateway where the user is validated. Any policy enforcement required happens here.
3. After successful validation, an Integration service call is made to webMethods Integration Cloud. For example, in this case let us say that the Integration service call made to update the customer record is updateaddress.
4. The Integration service call authenticates the user with the bank and updates the record in the database of the bank.
5. On successful update of the record, a confirmation message is sent to the client application as a response.
What is the Role of End-to-End Monitoring here
As explained earlier in this section,
End-to-End Monitoring monitors the entire business transaction from start to end and provides details of the transaction. A graphical representation of a business transaction flow is as follows. For more information, see
Business Transaction Details page.
