Considerations

View the considerations related to GDPR and various supported products.

GDPR Considerations

From a General Data Protection Regulation (GDPR) perspective, note the following considerations:

Product Considerations

End-to-End Monitoring has the following considerations with respect to the various supported products.

IBM webMethods API Gateway

Following is the current status of monitoring support in End-to-End Monitoring for HTTP-based IBM webMethods API Gateway transactions:

Action Supported
Invoke REST API in API Gateway Yes
Invoke SOAP API version 1.2 Yes
Invoke SOAP API version 1.1 Yes

IBM webMethods B2B

Following is the current status of monitoring support in End-to-End Monitoring for IBM webMethods B2B transactions:

Type Supported Currently Unsupported
Document Submission From IBM webMethods B2B User Interface Batch Executions
Channel Submission through REST client Reprocessed transactions
IBM webMethods B2B Connector submit in IBM webMethods Integration
wm.tn:submit , wm.tn:submitWithAttachments, wm.tn.route:routeBizdoc
Channel Protocols HTTP AS4
AS2 RNIF
SFTP
Document Types EDI
XML
Flatfile
Channel Type Inbound
Outbound
Integration Types IBM webMethods Integration
External Call
Cloud Container
Integration execution mode Synchronous
Asynchronous
Reliable
Important
  • For End-to-End Monitoring to trace the IBM webMethods B2B transactions, add the following B2B attribute of type String: e2e:ot-tracer-traceid.


Note
  • The document IDs of the involved documents are considered as the custom Transaction ID for IBM webMethods B2B transaction traces. However for AS2 channel protocol, both document ID and message ID are considered as custom Transaction ID.
  • Custom Transaction ID for B2B node in the transaction is the document ID submitted. However, custom Transaction ID for the whole transaction captures all the document IDs involved in IBM webMethods B2B.
  • Transaction name format is now SenderName:ChannelName instead of SenderName(Organization Unit):ChannelName.
  • The following document submission types are traced from IBM webMethods B2B only when cloud container tracing is enabled:
    • wm.tn:submit
    • wm.tn:submitWithAttachments
    • wm.tn.route:routeBizdoc

IBM webMethods Integration and Flow services

Following is the current status of monitoring support in End-to-End Monitoring for HTTP-based IBM webMethods Integration transactions:

Transaction Supported
Workflow execution Yes
Workflow execution through webMethods.io REST API Yes
Outgoing traces from workflow support is only for HTTP and IBM webMethods Integration Flow services connectors Yes
Flow execution using Play button or HTTPS Yes
Flow execution using Scheduler Yes
Workflow execution using “Run flow” connector Yes
Subscriber No
Listener No

Connectors

Following is the current status of monitoring support for IBM webMethods Integration Flow service connectors and Workflow connectors in End-to-End Monitoring:

Connector type Flow services Support Workflows Support
Predefined Connectors Yes From IBM webMethods Integration release v11.0.3 onwards.
Rest Connectors Yes From IBM webMethods Integration release v11.0.3 onwards.
SOAP Connectors Yes From IBM webMethods Integration release v11.0.3 onwards.
On-premise Connectors Yes From IBM webMethods Integration release v11.0.3 onwards.
Flat file Connectors Yes From IBM webMethods Integration release v11.0.3 onwards.
Note
  • Support for connector tracing of Flow services functionality is subject to IBM webMethods Integration release v10.16.5.
  • Support for connector tracing of Workflows functionality is subject to IBM webMethods Integration release v11.0.3.

Multi-Hop

Following is the current status of monitoring support in End-to-End Monitoring for a transaction when it moves from one component to another:

Transaction Supported
API Gateway to WMIC/Flow Editor REST invocation Yes
API Gateway to WMIC/Flow Editor SOAP 1.1 invocation Yes
API Gateway to WMIC/Flow Editor SOAP 1.2 invocation No
WMIC/Flow Editor to API Gateway using REST or SOAP Yes
Workflow to API Gateway using HTTP connector or CloudStreams connector Yes
Workflow to API Gateway No
Workflow to B2B using HTTP connector Yes
Workflow to B2B using CloudStreams connector No
Flow to API Gateway using CloudStreams connector Yes
Flow to B2B using CloudStreams connector No
Invoking B2B application from IBM webMethods Integration No

IBM webMethods Integration Server and Microservices Runtime

Following is the current status of monitoring support in End-to-End Monitoring for Integration Server and Microservices Runtime transactions:

Transaction Supported
Invoke Flow service Yes
Invoke Java Service Yes
Invoke Adapter Service Yes
Invoke Map Service Yes
Invoke XSLT Service Yes
Invoke webMethods Messaging Trigger Yes
Invoke HTTP Outbound Yes
Invoke Synchronous Service Yes
Invoke Asynchronous Service Yes
Invoke Publish Outbound Yes
Invoke OData Service No
Invoke JMS send/sendAndWait Yes

IBM webMethods Cloud Container

Following is the current status of monitoring support in End-to-End Monitoring for IBM webMethods Cloud Container transactions:

Transaction Supported Currently Unsupported
Cloud Container only use cases Regular flow
Nested flow
IBM webMethods Integration to IBM webMethods Cloud Container transactions Using Flow service
Using work flow
IBM webMethods Cloud Container to IBM webMethods Integration transactions Using Flow service
IBM webMethods B2B to IBM webMethods Cloud Container transactions Synchronous
Asynchronous
Reliable
Document submission
IBM webMethods Cloud Container to IBM webMethods B2B transactions Yes
Hybrid Integration use case Yes JNDI enabled hybrid use case
IBM webMethods API Gateway to IBM webMethods Cloud Container transactions Yes
IBM webMethods API Gateway through IBM webMethods B2B to IBM webMethods Cloud Container transactions Yes

End-to-End Monitoring support for the above listed Cloud Container use cases, is currently only available on demand for this initial release version 10.15.2. Click here to enable support for IBM webMethods Cloud Container use cases.

Click Hybrid monitoring with Integration Server through Cloud Container services for more details.