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.

webMethods Integration Cloud

Following is the current status of monitoring support in End-To-End Monitoring for HTTP-based Integration Cloud transactions:

Action Supported
Invoke an integration using Play Button or over HTTPS Yes
Invoke REST APIs or SOAP APIs in webMethods Integration Cloud Yes
Invoke any supported application Yes
Invoke an integration using the “Run Now” option No
Invoke an integration using Scheduler No

webMethods API Gateway

Following is the current status of monitoring support in End-To-End Monitoring for HTTP-based webMethods.io API transactions:

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

webMethods.io B2B

Following is the current status of monitoring support in End-To-End Monitoring for webMethods.io B2B transactions:

Type Supported Currently Unsupported
Document Submission From webMethods.io B2B User Interface Batch Executions
Channel Submission through REST client
webMethods.io B2B Connector submit in webMethods.io 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 webMethods.io Integration
External Call
Cloud Container
Integration execution mode Synchronous
Asynchronous
Reliable

Important:

  • For End-to-End Monitoring to trace the webMethods.io 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 webMethods.io 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 webMethods.io B2B.
  • More details are currently not supported for reprocess and resubmit transactions.
  • Transaction name format is now SenderName:ChannelName instead of SenderName(Organization Unit):ChannelName.

webMethods.io Integration and FlowServices

Following is the current status of monitoring support in End-To-End Monitoring for HTTP-based webMethods.io 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 webMethods.io Integration FlowServices connectors Yes
Flow execution using Play button or HTTPS Yes
Flow execution using Scheduler Yes
Workflow execution using “Run flow” connector Yes

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 webMethods IO Integration No

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 FlowService 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 Trigger No