WS-M does not capture Multi Protocol Gateway services payloads

This limitation is derived from a limitation of the monitored device.

Known workarounds: 

DPOD version 1.0.2 and IDG Firmware 7.5.2 with iFix ...  should provide this functionality out of the box!

The customer can manually modify the services to include a formatter, or use DPOD's custom logging mechanism to add payload data to the transaction details

Transactions under Default domain are not monitored

This limitation is derived from a limitation of the monitored device. Log targets defined at the Default domain collect all logs from all domains, and currently there is no available filter on the log targets to filter out logs from other applicative domains.

Known workarounds: There is a workaround, but it only applies if the customer is willing to duplicate all network traffic or alternatively run transactions only on the Default domain. Please contact support for more details.

Payload size does not include response size (only request size)

At present, monitored devices do not report the front end response payload size. Nor do they report on the backend request and response.

Known workarounds: None. Resolve this issue is part of product Roadmap.

Limitation on the number of domains to be monitored on a single gateway

IDG currently has a limit of 256 Syslog log targets per instance.

Since DPOD currently adds 2 log targets for each monitored domain, including default domain, DPOD can monitor up to 128 domains, if no other Syslog log targets are defined on that device.

Known workarounds: None.


B2B support is limited

At present, B2B has the most important features supported such transaction (IDG term) aggregation . Still Configuration sampling and specific filtering in dashbaoards are part of the current version.

Known workarounds: None. Resolve this issue is part of product Roadmap

Callacble rule invocation appears as a seperated transaction

At present, monitored devices do not report the front end response payload size. Nor do they report on the backend request and response.

Known workarounds: None. Resolve this issue is part of product Roadmap

Error is not displayed in "Extended transactions"

The extended transaction is the only feature of DPOD that involves instrumentation of XSLT transformation to the Web Service Proxy policy (request / response and error rules).

The instrumentation is integrated by the system only when initiated by the system administrator and not by default.

when an error is being raised but the service (WS-Proxy) the following situation are possible :

Since there is no error rule, an extended transaction log record is not being generated and there for the error is not displayed in "extend transactions" screen.

The extended transaction will look similar to the following (you can see that one record is missing) :



Since there is no error rule, an extended transaction log record is not being generated and there for the error is not displayed in "extend transactions" screen.

Previous services do have error rule so the  "extend transactions" screen will look similar to the following :