Page Comparison

Changes to Gateway objects

...

At present, the most important B2B features (e.g. transaction aggregation) are supported. Configuration sampling and specific filtering in dashboards are part of the current version.

The deprecated Extended Transaction is the only feature of DPOD that involves instrumentation of an 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.
The behavior when an error is raised by the service (WS-Proxy) depends on the applicable scenario:
- No error rule in the service where the error is raised. Previous services are configured with "Process HTTP errors = on"
  - As there is no error rule, an extended transaction log record will not be generated for the error, and it will not be displayed on the "Extended Transactions" screen.
  - The extended transaction display will resemble the following (note: one record is missing)
    Image Removed
- No error rule in the service where the error is raised. Previous services do have error rule configured
  - As there is no error rule, an extended transaction log record will not be generated for the error, and it will not be displayed on the "Extended Transactions" screen.
  - However, as previous services do have an error rule, the "Extended Transactions" display will resemble the following:
    Image Removed
Known workarounds: None.

You must NOT run the Deprecated Extended Transaction feature in API-C / API-M Domains.
Note: In some cases, the Deprecated Extended Transaction is not deployed on MPG services. This is due to the diversity of configuration in these services.
Customers are encouraged to open a PMR (Ticket) and provide the service configuration - so these cases can be addressed and resolved.
Known workarounds: Similar functionality can be applied with the new non intrusive-extend transaction introduced in v1.0.8.0