Dual channel support

End-to-End Monitoring supports monitoring of transactions originating in self-hosted products such as IBM® webMethods Integration Server or IBM webMethods API Gateway, and also supports monitoring of hybrid integration transactions. However, this support was previously limited to a single channel support that provided transaction monitoring for either hybrid integrations or for self-hosted originating transactions. This capability is now extended to dual channel support that provides simultaneous transaction monitoring for both hybrid integrations and self-hosted originating transactions.

Based on the flags configured, the transaction traces are transmitted to the intended targets. The following table describes the two single channel transmissions and the dual channel transmission criteria based on the flags SW_AGENT_COLLECTOR_ESTABLISH_CLOUD_COMMUNICATION and SW_AGENT_EXTERNAL_ESTABLISH_COMMUNICATION.

Following is the single channel flag configuration for hybrid monitoring.
  • SW_AGENT_COLLECTOR_ESTABLISH_CLOUD_COMMUNICATION:true
  • SW_AGENT_EXTERNAL_ESTABLISH_COMMUNICATION:false
Following is the single channel flag configuration for self-hosted monitoring.
  • SW_AGENT_COLLECTOR_ESTABLISH_CLOUD_COMMUNICATION:false
  • SW_AGENT_EXTERNAL_ESTABLISH_COMMUNICATION:true
Following is the dual channel flag configuration for hybrid monitoring and self-hosted monitoring.
  • SW_AGENT_COLLECTOR_ESTABLISH_CLOUD_COMMUNICATION:true
  • SW_AGENT_EXTERNAL_ESTABLISH_COMMUNICATION:true
Transaction Type Single channel - Hybrid Single channel - Self-hosted Dual Channel
Hybrid integration transaction Sent to End-to-End Monitoring collector. Skipped from End-to-End Monitoring collector and sent to the APM target. However, the traces are accepted or rejected based on the traceId length criteria of the APM target. Sent to both End-to-End Monitoring collector and APM target with 16-byte traceId length.
Note: The traces are sent to both targets as any transaction running on-premises irrespective of the source of the transaction invocation, runs on the on-premises Integration Server.
Self-hosted originating transaction Transactions discarded Sent to APM target with 16 byte traceId length. Sent to APM target with 16 byte traceId length.
Note:
  • Transactions are sent only to the APM target and not transmitted to the End-to-End Monitoring collector.
  • Transactions originating in the on-premises IBM webMethods API Gateway are not transmitted to the End-to-End Monitoring collector when dual channel support is enabled.
Note:
  • Dual channel support is available only for the setup that uses Integration Server (IS) package v10.15 fix 10, Integration Server (IS) package v10.11 fix 14, and not available for the setup that uses IBM webMethods Installer.
  • Dual channel support is also available for webMethods Integration Server (IS), webMethods APIGateway, and webMethods Microservices Runtime (MSR) versions 10.11, 10.15 and 11.1 through the IBM webMethods Update Manager.