Introduction

End-to-End Monitoring allows you to follow the complete flow of your business transaction across multiple products regardless of their complexity. This allows you to understand immediately what is going on and why, in real time and from a single web view.

Watch the following video to get an overview of the features and how to use them.


Also refer the Tutorials section for more detailed information.

Summary

Business transactions are initiated when client applications make requests for information or submit updates to your organisation through your webMethods.io integration platform. These business transactions can implicate multiple applications and many steps as shown in the diagram below.

Here we can see an example of a bank customer making a change to his address using a phone banking app that connects through the bank’s webMethods.io platform:

  1. Customer raises an address change request using a client application. The client application is accessible from any device.

  2. The request makes an API call to webMethods.io API where the user is validated. Any policy enforcement that is required happens here.

    Note: Currently, End-to-End Monitoring does not support any asynchronous requests.

  3. After successful validation, an integration service call is made to webMethods.io Integration. For example, 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.

How does End-to-End Monitoring help?

End-to-End Monitoring traces each step of your business transaction which could be a service invocation, API call or a B2B transaction. This tracing takes place in real time from start to finish, regardless of the product, or the timing across asynchronous hops through your integration platform. The transactions can be viewed by All Transactions or grouped by integration type such as “New Customer Orders” or “outbound shipping”. Refer to the section Business Transaction Details Page, for more details.

Accessing End-to-End Monitoring

Software AG Cloud products are available in several geographical regions, operated by different infrastructure providers. Click here for information on the available products and also the underlying infrastructure provider in a region.

Microsoft Azure based tenants

End-to-End Monitoring is available directly from your cloud tenant home page and will show transactions if they pass through one of the following Software AG products.

We will be shortly adding support for monitoring your on-premises integrations with webMethods.io Integration, to ensure complete traceability between your cloud and on-premises hybrid integrations.

  1. Go to Software AG Cloud.

  2. Click Login.

  3. Type your Environment name and click Next.

  4. Select the app switcher and click End-to-End Monitoring.

  5. You can also access End-to-End monitoring from the app switcher available in the following products:

    • webMethods.io API Gateway


    • webMethods.io Integration


    • webMethods.io B2B

The Business Transaction Details page provides you an end-to-end view of the transactions along with the time spent by a transaction at each component of the platform.

AWS based tenants

You can access End-to-End Monitoring using the app switcher available in webMethods.io Integration.

The Business Transaction Details page provides you an end-to-end view of the transactions along with the time spent by a transaction at each component of the platform.

GDPR Considerations

From a General Data Protection Regulation (GDPR) perspective, the following considerations are to be noted:

Product Considerations

End-to-End Monitoring has the following product considerations with respect to the various supported products:

webMethods Integration Cloud

Following is the current status of monitoring support in End-To-End Monitoring for HTTP-based Integration Cloud transactions:

Action Supported
Invoke an integration using Play Button or over HTTPS Yes
Invoke REST APIs or SOAP APIs in webMethods Integration Cloud Yes
Invoke any supported application Yes
Invoke an integration using the “Run Now” option No
Invoke an integration using Scheduler No

webMethods API Gateway

Following is the current status of monitoring support in End-To-End Monitoring for HTTP-based webMethods.io API transactions:

Action Supported
Invoke REST API in API Gateway Yes
Invoke SOAP API version 1.2 No
Invoke SOAP API version 1.1 Yes

B2B

Following is the current status of monitoring support in End-To-End Monitoring for HTTP-based webMethods.io B2B transactions:

Transaction Supported
Channel: HTTP Inbound, Rule: Synchronous, Doc Type: EDI Yes
Channel: HTTP Inbound, Rule: Synchronous, Doc Type: XML Yes
Channel: HTTP Inbound, Rule: Reliable No
Channel: HTTP Inbound, Rule: Asynchronous No
Channel: HTTP Outbound No
Channel: AS2 No

webMethods.io Integration and FlowServices

Following is the current status of monitoring support in End-To-End Monitoring for HTTP-based webMethods.io Integration transactions:

Transaction Supported
Workflow execution Yes
Workflow execution through webMethods.io REST API Yes
Outgoing traces from workflow support is only for HTTP and webMethods.io Integration FlowServices connectors Yes
Flow execution using Play button or HTTPS Yes
Flow execution using Scheduler No
Workflow execution using “Run flow” connector Yes

Multi-Hop

Following is the current status of monitoring support in End-To-End Monitoring for a transaction when it moves from one component to another:

Transaction Supported
API Gateway to WMIC/Flow Editor REST invocation Yes
API Gateway to WMIC/Flow Editor SOAP 1.1 invocation Yes
API Gateway to WMIC/Flow Editor SOAP 1.2 invocation No
WMIC/Flow Editor to API Gateway using REST or SOAP Yes
Workflow to API Gateway using HTTP connector or Cloudstreams connector Yes
Workflow to API Gateway No
Workflow to B2B using HTTP connector Yes
Workflow to B2B using Cloudstreams connector No
Flow to API Gateway using Cloudstreams connector Yes
Flow to B2B using Cloudstreams connector No
Invoking B2B application from webMethods IO Integration No

webMethods Integration Server and Microservices Runtime

Following is the current status of monitoring support in End-To-End Monitoring for Integration Server and Microservices Runtime transactions:

Transaction Supported
Invoke FlowService Yes
Invoke Java Service Yes
Invoke Adapter Service Yes
Invoke Map Service Yes
Invoke XSLT Service Yes
Invoke webMethods Messaging Trigger Yes
Invoke HTTP Outbound Yes
Invoke Synchronous Service Yes
Invoke Asynchronous Service Yes
Invoke Publish Outbound Yes
Invoke OData Service No
Invoke JMS Trigger No