Release 11.1.0

What's New

Self-hosted Transaction Monitoring enhancements

• End-to-End Monitoring now supports self-hosted transaction monitoring with APM targets that accept a trace_id of 16 characters or less.
• End-to-End Monitoring now supports self-hosted transaction monitoring for 10.11 and 10.15 through IBM webMethods Update Manager, and for 11.1.0 through IBM webMethods Installer.

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.

Generating a deep link URL from SkyWalking(SW) framework attribute

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.

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.

• Additional headers are noticed when running a REST application.
  When a REST application Flow service is run with changed header attributes, sw6 headers are observed in the pipeline output result. sw6 is a valid request header used by End-to-End Monitoring for monitoring IBM product runtimes. This has no impact on feature functionalities.

  
  
  

• End-to-End Monitoring is supported on the latest version of Google Chrome web browser (v105 or later).

• After End-to-End Monitoring is upgraded, the older version browser’s cache and cookies are not cleared automatically. This may lead to incorrect display of page content. Ensure that you clear the browser’s cache manually after every upgrade, and then access End-to-End Monitoring.

• End-to-End Monitoring is best experienced when the scale and layout are adjusted to the following settings:

• IBM webMethods iPaaS products are available in several geographical regions, operated by different infrastructure providers. Go to the IBM webMethods iPaaS Regions website for more information.

• Mapping of End-to-End Monitoring production URLs with the IBM webMethods iPaaS Regions is as follows:

• Information on major releases, hotfixes, and patch releases including the latest statistics on the availability of cloud environments, incident history, and planned maintenance events are available on the iPaaS Service Status page.
  
  

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.