Release 10.16.0

Highlights

Security enhancements

• Security enhancements are made to address vulnerabilities in numerous third-party software components of End-to-End Monitoring.

Reliability and Performance enhancements

• Reliability enhancements to further minimise trace loss: Multiple enhancements have been made at the product agent and collector levels to minimize trace losses.
• Performance enhancements in the agent to collector communication.

Tracing enhancements

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

• Miscellaneous tracing enhancements:

  • SOAP API version 1.2 call from webMethods API Gateway.

• IBM webMethods B2B transactions currently support HTTP protocol, EDI and XML file types and synchronous integration execution. IBM webMethods B2B release version 10.16 onwards, the B2B agent also supports:

  • AS2 and SFTP protocols.
  • UI submissions.
  • Trading Network services.
  • Flatfile file type.
  • Asynchronous and reliable integration modes.

End-to-End Monitoring tracing capabilities for IBM webMethods Cloud Container

• End-to-End Monitoring agent is now implemented for IBM webMethods Cloud Container solutions. When you now invoke a Cloud Container service, the traces can be visualized in the End-to-End Monitoring user interface. The following use cases of Cloud Container transactions are supported with IBM webMethods Cloud Container release version 10.16:
  
  
  • Cloud Container only use cases: Regular and Nested flow.
  • Two way transactions between IBM webMethods Integration and IBM webMethods Cloud Container.
  • Two way transactions between IBM webMethods B2B and IBM webMethods Cloud Container.
  • Hybrid integration use cases.
  • webMethods API Gateway to IBM webMethods Cloud Container transactions.
  • webMethods API Gateway through IBM webMethods B2B to IBM webMethods Cloud Container transactions.

Asset migration support

• End-to-End Monitoring user interface now provides support for the migration of assets such as groups and rules. Asset migration is helpful in situations when you need to migrate your assets from lower environments such as development into higher environments such as testing, pre-production and production.

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 webMethods.io 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.

Fixes

This section provides information on the fixes for End-to-End Monitoring.