Transaction use cases supported in end-to-end monitoring

End-to-end monitoring traces transactions across IBM webMethods Hybrid Integration capabilities. Review the supported transaction use cases and capability-specific considerations.

API Connect

Transaction uses cases for API Connect.
Transaction Supported
Transactions from API Connect to App Connect. Yes
Transactions from webMethods API Gateway, webMethods Integration, or webMethods B2B Integration to API Connect. Yes
Transactions from Integration runtime management to API Connect. No
Transactions from API Connect to webMethods Integration, webMethods B2B Integration, or webMethods API Gateway. Yes

App Connect

Transaction uses cases for App Connect.
Transaction Supported
Transactions from webMethods API Gateway, webMethods Integration, or webMethods B2B Integration to App Connect. Yes
Transactions from webMethods Integration workflows to App Connect by using callable flows. Yes
Integrations in App Connect that have HTTP, REST, SOAP, and callable flow constructs. Yes
Integrations in App Connect by using IBM® MQ. Yes
Integrations in IBM App Connect Enterprise. Yes

To trace transactions in App Connect Enterprise, end-to-end monitoring provides an OpenTelemetry receiver endpoint that you can configure in App Connect Enterprise. For more information, see Monitoring end-to-end transactions in IBM webMethods Hybrid Integration.

Event Endpoint Management

End-to-end monitoring supports tracing producer-consumer transactions in webMethods Integration, routed through Event Endpoint Management.

To trace transactions routed through the event gateway in Event Endpoint Management, configure the event gateway to send OpenTelemetry trace information to end-to-end monitoring. For more information, see Preparing to integrate with IBM webMethods Hybrid Integration End-to-end Monitoring.

Supported and unsupported transaction uses cases for Event Endpoint Management
Transaction Supported
webMethods Integration publishes one or more messages to a Kafka server through an event gateway in Event Endpoint Management. Yes
webMethods Integration consumes messages using a Kafka listener through an event gateway in Event Endpoint Management. Yes

To set up end-to-end monitoring for Kafka record tracing, generate your API Key and configure OpenTelemetry metrics, as required.

webMethods API Gateway

End-to-end monitoring supports HTTP-based webMethods API Gateway transactions that occur through REST API and SOAP 1.1 API and 1.2 API calls.

webMethods B2B Integration

End-to-end monitoring supports the following transaction use cases in webMethods B2B Integration.
Document submission methods
  • From the webMethods B2B Integration user interface
  • Using an inbound channel
  • Using webMethods B2B Integration connectors in webMethods Integration
  • Using the following built-in services: wm.tn:submit, wm.tn:submitWithAttachments, wm.tn.route:routeBizdoc
Monitoring support for the transactions also depends on the following factors:
Channel protocols
Supported: HTTP, AS2
Unsupported: AS4, RNIF, CXML
Channel types
Inbound and outbound
Document types
EDI, XML, Flatfile
Integration types
webMethods Integration and external calls
Integration execution modes
Synchronous, asynchronous, and reliable
Support for IBM Sterling® VAN
End-to-end monitoring does not trace the status of transactions between IBM Sterling VAN and webMethods B2B Integration. You can monitor these transactions in webMethods B2B Integration.

webMethods Integration

Transaction uses cases for webMethods Integration.
Transaction Supported
Workflow executions Yes
Flow service executions Yes
Scheduled executions of flow service Yes
Transactions that involve on-premises Integration Server, Microservices Runtime, API Gateway No

In flow services and workflows, end-to-end monitoring supports tracing transactions for the following connector types in webMethods Integration.

  • Predefined Connectors
  • REST Connectors
  • SOAP Connectors
  • On-premises Connectors
  • Flat file Connectors
Consider the following points when you trace webMethods Integration transactions by using end-to-end monitoring:
  • A publisher-subscriber JMS transaction is traced as a single transaction when a webMethods Integration flow service publishes to a subscriber that calls a flow service.
  • A producer-consumer Kafka transaction through Event Endpoint Management is traced as separate transactions. However, the consumer transactions include a link back to the corresponding producer transaction for full traceability.
  • Producer-consumer transactions between webMethods Integration and Kafka server, routed through event gateway in Event Endpoint Management.
  • Consumer transactions in webMethods Integration using Kafka listeners, routed through event gateway in Event Endpoint Management.
  • When a flow service in webMethods Integration consumes messages from a Kafka server routed through event gateway in Event Endpoint Management without using the listener, end-to-end monitoring traces the transaction as a simple flow.
  • Transactions that involve conditional branching, switch case, and loops in flow services and workflows are supported.
  • Workflows that include the Wait for Callback action are not fully supported in end-to-end monitoring. This behaviour is because the action splits the flow into multiple parts, and each part is traced as a separate transaction rather than as a single transaction.

Integration runtimes

Transaction uses cases in webMethods Integration runtimes.
Transaction Supported
Start Flow service Yes
Start Java™ Service Yes
Start adapter Service Yes
Start Map Service Yes
Start XSLT Service Yes
Start webMethods Messaging Trigger Yes
Start HTTP Outbound Yes
Start Synchronous Service Yes
Start Asynchronous Service Yes
Start Publish Outbound Yes
Start OData Service No
Start JMS send or sendAndWait Yes

Connectors

End-to-end monitoring supports the following IBM webMethods Integration flow service and workflow connectors:

Connector type Flow services support Workflows support
Predefined Connectors Yes Yes
Rest Connectors Yes Yes
SOAP Connectors Yes Yes
On-premise Connectors Yes Yes
Flat file Connectors Yes Yes
Note:

Tracing is not supported for connectors that are defined at a child service level.

IBM webMethods Managed File Transfer

End-to-end monitoring supports the following transaction use cases in IBM webMethods Managed File Transfer.
File transactions
The trace information related to the following file operations performed by clients, using any protocol (for example, FTP, SFTP) or web client is available in End-to-end monitoring.
  • File upload
  • File download
Actions
When a file is processed by Schedule or Post-processing action, trace information for the operation is sent to End-to-end monitoring.
When a Post-processing action is triggered as part of a file operation, both the transactions are part of the same trace in End-to-end monitoring.
When an action (Post-processing or Schedule) triggers a webMethods Integration flow service, the transactions in Managed File Transfer and webMethods Integration for the file will be part of the same transaction in End-to-end monitoring.

[Technology preview] On-premises IBM MQ

End-to-end monitoring supports the following use cases with IBM MQ.
Transaction Supported
Transactions from App Connect Enterprise to IBM MQ. Yes
Transactions from IBM MQ to App Connect Enterprise. Yes
Transactions from App Connect to IBM MQ. Yes
Transactions from IBM MQ to App Connect. Yes
Transactions from webMethods Integration to IBM MQ. Yes
Transactions from IBM MQ to webMethods Integration. Not yet supported
Transactions from IBM MQ to webMethods Integration listeners. Yes
Transactions from webMethods Integration to Integration Server (on-premises) by using IBM MQ. Not yet supported
Transactions from App Connect to Integration Server (on-premises) by using IBM MQ. Not yet supported
Transactions from external systems to App Connect by using IBM MQ. Yes
Transactions from App Connect to external systems by using IBM MQ. Yes