Release 11.0.0

What's New

Release 11.0.6

Self-hosted Transaction Monitoring

End-to-End Monitoring is used for monitoring cross product transactions involving webMethods.io iPaaS products and self-hosted products like webMethods Integration Server or API Gateway, but not used for monitoring of transactions that span only the self-hosted products. Support for transaction monitoring of self-hosted products is now available. The agents can now be configured to trace all self-hosted product transactions to the Application Platform Monitoring (APM) tool or data store of your choice using the OpenTelemetry standard. The OpenTelemetry support in End-to-End Monitoring for transactions within the webMethods.io iPaaS products will be available in a later release.

Read More

Hybrid Integration Monitoring setup using Integration Server (IS) package

Hybrid integration transaction support in End-to-End Monitoring was previously only available for recent versions of webMethods Integration Server and API Gateway, and only for certain operating systems since the delivery mechanism was through the IBM Installer and it was a challenge to retroactively change the installer user interface of previous versions. So customers using older versions of webMethods Integration Server and API Gateway could not benefit from this capability. Also, the hybrid monitoring agent setup involved manual configuration that sometimes resulted in incorrect setup.

These limitations have now been addressed with the delivery mechanism of the End-to-End Monitoring agent for hybrid integration transactions using an Integration Server package that also consists of a user interface to configure End-to-End Monitoring.

Read More

Workflow connectors enabled

Support for connector tracing of workflows in IBM webMethods Integration is now enabled.

Security enhancements

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

Reliability enhancements

End-to-End Monitoring collector caching optimizations have been made to assist data store to handle higher load better. Further, observability enhancements have been implemented to more effectively find the root cause of issues during increased load.

Documentation enhancements

Subscriber and listener HTTP-based IBM webMethods Integration transactions monitoring support status has been updated in documentation.

Read More

Release 11.0.2

Deep Link Capability for transaction groups created using End-to-End Monitoring user interface

End-to-End Monitoring deep link capability provides you ease of access without the need to navigate through multiple steps to access details of a transaction. Earlier, deep link capability was limited to a single transaction or a set of transactions. This enhancement now provides you the capability to generate a URL to directly access a transaction group created using the End-to-End Monitoring user interface. The transaction view of a group deep link URL contains either a single group or a set of groups across environments based on the group name.

Read More

Tooltip and documentation enhancements

End-to-End Monitoring user interface now has enhanced tooltips and associated documentation with detailed examples providing you with a better understanding about why End-to-End Monitoring transaction duration is different from individual product’s transaction duration.

Read More

Cloning capability for transaction groups and rules

End-to-End Monitoring group and rule cloning capability provides you with a means of replicating all the properties of existing transaction groups or rules. This functionality simplifies the process of creating similar transaction groups or rules. The clone name and properties are pre-populated and editable.

Read More

Security enhancements

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

Release 11.0.0

Deep Link Capability for easier access to End-to-End Monitoring Transactions

End-to-End Monitoring deep link capability allows you to generate a URL that you can bookmark. When you access this bookmarked URL, the system first authenticates you and then directly takes you to the transaction view in End-to-End Monitoring user interface, pertaining to the transaction ID associated with the deep link. The transaction view contains either a single transaction or a set of transactions based on how the given transaction ID is configured.

This feature provides you ease of access without the need to navigate through multiple steps to access details of a transaction ID, and also allows you to define advanced filter criteria to locate transactions in the End-to-End Monitoring user interface.

Read More

Security enhancements

Security enhancements have been implemented in End-to-End Monitoring to address vulnerabilities found in multiple third-party software components. These security enhancements also include enhanced firewall protection.

Reliability enhancements

Enhancements have been made to introduce circuit-breaker mechanisms at the End-to-End Monitoring agent level as well as at the Redis-based intermediate storage level for traces. These reliability enhancements minimise the impact to product runtimes when recurring issues are experienced within a short period of time, for example, connectivity issues.

Customized service domain support in IBM webMethods API Gateway

End-to-End Monitoring now captures the Fully Qualified Domain Name (FQDN) of transactions from IBM webMethods API Gateway, when the tenant uses a custom domain URL.

Enterprise Disaster Recovery Framework Enhancements

The underlying library of the Enterprise Disaster Recovery Framework has been upgraded to the latest version to enhance reliability and security.

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.