Release 11.1.0

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

What's New

Release 11.1.2 (Preview)

Improved identification of Develop Anywhere, Deploy Anywhere (DADA) runtimes

End-to-End Monitoring now supports improved identification of Develop Anywhere, Deploy Anywhere (DADA) runtimes using unique names. The transactions can now be filtered and grouped based on the runtime names.

Tracing enhancement for publish-subscribe use case in IBM webMethods Integration

End-to-End Monitoring previously only supported tracing of Integration Flow services that published messages to messaging targets. However, Flow services initiated by the subscriber that received the message were not traced.

End-to-End Monitoring now supports the capture of IBM webMethods Integration Flow service traces initiated through subscribers. The Flow service traces are now linked to the parent publisher Flow services to provide a single view of the transaction. Note that this functionality is subject to IBM webMethods Integration release v11.0.8.

Tracing enhancements in on-premises agents

End-to-End Monitoring on-premises agent has now been enhanced to simultaneously support both on-premises only transactions and hybrid integration transactions originating from the cloud. This support was previously limited to either on-premises only transactions or hybrid integration transactions originating from the cloud.

OTLP Enhancements

End-to-End Monitoring OTLP-based tracing for on-premises only use cases is now certified to work with more APM targets such as IBM Instana and AppDynamics.

Security enhancements

Security enhancements have been implemented in End-to-End Monitoring to address vulnerabilities found in multiple third-party software components.

Release 11.1.0

Self-hosted Transaction Monitoring enhancements

Read More

Self-hosted Transaction Monitoring support for Develop Anywhere, Deploy Anywhere (DADA)

End-to-End Monitoring now supports transferring Develop Anywhere, Deploy Anywhere (DADA) transactions to OTLP targets.

New functions setCustomTransactionId and setCustomTransactionIds

IBM webMethods Integration Flow service built-in services now has a new group E2E Monitoring that contains the functions setCustomTransactionId and setCustomTransactionIds. You can use these functions to set the custom transaction ID in End-to-End Monitoring as individual values or as an array of key value pairs.

Read More

For more details about the IBM webMethods Integration functions click here.

You can now generate an End-to-End Monitoring deep link URL using a SW key available in your transaction. This feature facilitates easier access to End-to-End Monitoring through deep link capability from other IBM webMethods iPaaS products.

Note
  • This functionality is usable only when the IBM webMethods iPaaS product exposes the link through the application.
  • Currently only IBM webMethods B2B provides the SW key in transaction attributes.

Read More

Product rebranding

webMethods.io End-to-End Monitoring has been renamed to IBM webMethods End-to-End Monitoring.

Security enhancements

Security enhancements have been implemented in End-to-End Monitoring to address vulnerabilities found in multiple third-party software components.

Performance enhancements

Performance enhancements have been implemented at the application level to reduce the load on the back-end system.

Usage Notes

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

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.