Changes to Gateway Objects

DPOD requires some configuration changes to at both device and domain levels. Theses changes include but are not limited to syslog targets.

At the service level -  only the optional feature of Extended Transaction requires instrumentation .

To see the full list of changes please look at this table

WS-M does not capture Multi Protocol Gateway services payloads for firmware pre 7.5.2 ?

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

Known workarounds:  DPOD version 1.0.2 and IDG Firmware 7.5.2.1 (especially  with iFix IT17479: JSON PAYLOAD NOT CAPTURED BY WSM AGENT )  should provide this functionality out of the box!

Transactions under the 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 way to apply a filter to the log targets in order to filter out logs from other application 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) todo:hk - what do you mean? is this the other way around?

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. Resolution of this issue is part of the product Roadmap.


Limitation on the number of domains that can be monitored on a single gateway

IDG with firmware prior to 7.5.X can only support a maximum of 256 Syslog log targets per instance, starting at 7.5.X, IDG may support up to 500 (See http://www.ibm.com/support/knowledgecenter/SS9H2Y_7.5.0/com.ibm.dp.doc/logtarget_logs.html)

With default configuration, each domain on the IDG has 2 syslog targets defined. DPOD adds 2 additional log targets for each monitored domain, and 1 for the default domain, and customers may configure their own log targets for other
systems (e.g. security tools).

The formula to calculate the number of domains available per device is therefore:
{500 -[Number of Existing Domains * 2]  - [Customer predefined syslog targets] }/ 2 todo:hk is this 500 or 256?

When no other Syslog log targets are defined on that device, DPOD can monitor up to 125 domains.

Known workarounds:

Customers are encouraged to move some of their domains to different devices.


B2B support is limited

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.

Known workarounds:

None. Resolution of this issue is part of the product Roadmap.


Callable rule invocation appears as a separate 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. Resolution of this issue is part of the product Roadmap.

Error is not displayed in "Extended transactions"

The 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 behaviour 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)

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: 

The Extended Transaction facility does not support APIC / APIM.

You must NOT run it in API-C / API-M Domains


Note: In some cases, the 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 and provide the service configuration - so these cases can be addressed and resolved.

No support for DHCP 

DPOD does not support DHCP network configuration. Please refer to Change Appliance Network Address

Known workarounds: 

None.