Changes to Gateway Objects
The product DPOD requires some configuration changes to configuration on a at both device and domain levels - such syslog target and more.As for . Theses changes include but are not limited to syslog targets.
At the service level only - 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: todo: hk
NEW! - 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 the Default domain are not monitored
This limitation is derived from a limitation of the monitored device. Log
Log targets defined at the Default domain collect all logs from all domains, and currently there is no available filter on way to apply a filter to the log targets in order to filter out logs from other applicative 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
tothat can be monitored on a single gateway
From 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 it might , IDG may support up to 500 - (See http://www.ibm.com/support/knowledgecenter/SS9H2Y_7.5.0/com.ibm.dp.doc/logtarget_logs.html (Prior IDG currently has a limit of 256 Syslog log targets per instance.)
By With default configuration, each domain will have on the IDG has 2 syslog targets defined by IDG.Since DPOD currently adds another 2 . DPOD adds 2 additional log targets for each monitored domain, and 1 for the default domain,
Customer will also have its own log target to other system (like Security tools)
So Number of domain is Equals to : 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 DPOD can monitor up to 125 domains, if no 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: Customer
Customers are encouraged to move some of its their domains to another devicedifferent devices.
B2B support is limited
At present,
B2B hasthe most important
features supported such transaction (IDG term) aggregation . StillB2B features (e.g transaction aggregation) are supported. Configuration sampling and specific filtering in dashboards are part of the current version.
Known workarounds:
None.
ResolveResolution of this issue is part of the product
roadmapRoadmap.
Callable rule invocation appears as a separate transaction
At present, monitored devices do not report the front end response payload size
. Nornor do they report on the backend request and response.
Known workarounds:
None. Resolve
None. Resolution of this issue is part of the product
roadmapRoadmap.
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.
When The behaviour when an error is being raised but by the service (WS-Proxy) the following situation are possible depends on the applicable scenario:
No error rule in the service
thatwhere the error is
beingraised
on and previous. Previous services are configured with "Process HTTP errors = on"
SinceAs there is no error rule, an extended transaction log record
iswill not
beingbe generated
and thereforefor the error
is, and it will not be displayed
in "extend transactionson the "Extended Transactions" screen.
The extended transaction display will
resemble the following (
you can see thatnote: one record is missing)
:
No error rule in the service
thatwhere the error is
beingraised
on but previous. Previous services do have error rule configured
SinceAs there is no error rule, an extended transaction log record
iswill not
beingbe generated
and thereforefor the error
is, and it will not be displayed
in "extend transactionson the "Extended Transactions" screen.
However, as previous services do have an error rule
so the "extend transactions" screen will look similar to, the "Extended Transactions" display will resemble the following:
The Extended
transaction is not supportingTransaction facility does not support APIC / APIM.
You must NOT run it in API-C / API-M Domains
Note: In some cases, the Extended
transactionTransaction is not deployed on MPG services
because of. This is due to the diversity of configuration in these services.
Customer is
Customers are encouraged to open a PMR and provide the service configuration - so
these cases can be
eliminatedaddressed and resolved.
No support for DHCP
No DPOD does not support for DHCP network configuration. Please refer to Change Appliance Network Address
Known workarounds:
None
None.