Release 10.17.0

Explore the release highlights, usage notes, known issues, and fixes for IBM webMethods End-to-End Monitoring.

What's New

10.17.4

Security enhancements

Reliability enhancements

IBM webMethods Integration Connectors

Numerous IBM webMethods Integration Flow services use predefined and configurable connectors to invoke third-party SaaS applications. Connectors not only connect to external third-party SaaS products, but also to other webMethods.io products. End-to-End Monitoring can now monitor the connectors’ tracing with additional granularity. The End-to-End Monitoring user interface displays an expand button on a connector node invoked by IBM webMethods Integration Flow services. Expanding this node lets you view the connector’s actual details, along with its icon.

Note: This support for connector tracing of Flow services functionality is subject to IBM webMethods Integration release v10.16.5. Support for connector tracing of Workflows will be available in a subsequent release.

Read More

webMethods Integration Anywhere server call trace support

End-to-End Monitoring now supports tracing of webMethods Integration Anywhere server calls originating from IBM webMethods Integration Workflows.

Rule violation email notification enhancements

End-to-End Monitoring now provides enhanced rule violation notification emails. The notification email provides details pertaining to the group associated with the rule violated. Rules can now be set with severity levels as well.

Read More

Daylight saving support

End-to-End Monitoring now considers daylight savings while displaying the transaction execution time to better correlate with the transaction execution time displayed in other IBM cloud products.

10.17.0

Security enhancements

Reliability enhancements

Performance enhancements

Tracing enhancements

The following products and use cases are now supported by End-to-End Monitoring:

User Interface enhancements

The following user interface enhancements are implemented to improve the overall user experience and provide greater functionality:

User authorization

Usage Notes

This section provides any additional information that you need to work with End-to-End Monitoring.

IBM webMethods iPaaS Region Sample URL
US1 Oregon AWS https://tenantname.e2em-aw-us.webmethods.io/e2emonitoring/
US2 East Azure https://tenantname.e2em-az-us.webmethods.io/e2emonitoring/
EU2 Frankfurt AWS https://tenantname.e2em-aw-eu.webmethods.io/e2emonitoring/
EU3 West Azure https://tenantname.e2em-az-eu.webmethods.io/e2emonitoring/
AU1 Australia East Azure https://tenantname.e2em-az-au.webmethods.io/e2emonitoring/

Known Issues

This section lists the issues for this release that were known when this release readme was published.

UHM-970
In End-to-End Monitoring, API Gateway traces without a transactional event are not getting traced.

UHM-973
In End-to-End Monitoring, for a complex integration, where one SOAP API or REST API calls another SOAP API, only the starting point of the trace is captured. For the same complex integration, both the traces appear as part of its monitoring feature. The same limitation is not observed when REST APIs are called from a SOAP API or another REST API.