Overview

Business transactions are initiated when client applications make requests for information or submit updates to your organisation through your webMethods.io platform. These business transactions can entail multiple applications and many steps.

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

Eligibility

End-to-End Monitoring is available only in the enterprise edition of IBM webMethods Integration.

If you satisfy the mentioned criteria but still not able to access End-to-End Monitoring, contact IBM support and share the details such as tenant name, cloud provider, and region to enable the capability.

Note
End-to-End Monitoring currently retains monitoring data for seven days. The capability to retain monitoring data for longer periods will be available in a later release.

Know More

  • See Dashboard for a collective view of all the business transactions carried out within your cloud platform.
  • The Alerts page lists all the Rule violations and the Rule list. See Alerts for more details.
  • Click here to see how to specify a custom transaction ID as part of your Flow services.
  • A hybrid integration consists of a transaction that spans multiple platforms and products including both cloud and on-premises setups. See Hybrid Monitoring for more details.
  • Click here to know how to filter transactions based on the environment group and the related stages.
  • See Tutorials for step-by-step user journeys.

Role of End-to-End Monitoring

Let us see an example of a bank customer making a change to the address using a phone banking app, which connects through the bank’s IBM webMethods 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 IBM webMethods API Gateway where the user is validated. Any policy enforcement that is required happens here.

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

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

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 through All Transactions or grouped by integration type such as New Customer Orders or outbound shipping. For more details, see Business Transaction Details Page.

Accessing End-to-End Monitoring

End-to-End Monitoring shows transactions if they pass through one of the following IBM webMethods products. Support has been added to monitor your on-premises integrations with IBM webMethods Integration to ensure complete traceability between your cloud and on-premises hybrid integrations.

End-to-End Monitoring is available directly from your cloud tenant home page and shows transactions if they pass through the following supported IBM products.

To access End-to-End Monitoring

  1. Go to IBM webMethods iPaaS.

  2. Click Login.

  3. Type your Environment name and click Next.

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

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

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.

Authorization

From v10.16.1, End-to-End Monitoring provides you with user authorization options.

This authorization implementation has no impact on you as an end-user of an existing tenant. You will be able to access End-to-End Monitoring user interface as usual.

What has changed?

Policy enabled

Each tenant now has a policy introduced in IBM webMethods iPaaS. This policy is enabled by default. If a given tenant is subscribed to End-to-End Monitoring, then all users of this tenant will be able to access End-to-End Monitoring.

Policy disabled

However, when this policy is disabled for a given tenant, then new End-to-End Monitoring roles start appearing in the IBM webMethods iPaaS administration console. As an end-user, you will be able to access the End-to-End Monitoring user interface, only if you are assigned one of the following roles:

How to enable role based access?

  1. Log in to IBM webMethods iPaaS as an Account-Administrator or Cloud-Tenant-Administrator. You will be able to view all your subscribed products in the app switcher.

  2. In IBM webMethods iPaaS, select Administration.

  3. Click the Policies tab. Scroll down to End-to-End Monitoring Access Policy. Turn off Allow End-to-End Monitoring for all users. Apply your changes.

  4. Click the Users tab. Search for the user that needs role based access. Click on the username.

  5. Edit the user profile. Enable E2eMonitoring-User role. Save your changes.

  6. Log in as the user with role based access. You will now be able to view IBM webMethods End-to-End Monitoring on your app switcher.

  7. Log out and log back in to your tenant for the changes to take effect, in case a page refresh does not apply the required changes.