...
...
DPOD
...
integration with API-C can be applied to only a
...
single API Connect
...
domain per DataPower
...
Gateway for
...
firmware lower than 7.6
This limitation is derived from a limitation of the monitored device.
Known workarounds: upgrade Upgrade to firmware 7.6 or / 7.5.2.8 or later.
Changes to Gateway
...
objects
DPOD requires some configuration changes to at both device and domain levels. These changes include but are not limited to syslog Syslog log targets.
At the service level - only the optional deprecated feature of the Extended Transaction requires instrumentation.
To see the full list of changes please look at this table.
No support for DHCP
DPOD does not support DHCP network configuration. Please refer to Change Appliance Network Address
Known workarounds:
...
None.
Operational maintenance plan limitations
DPOD release since v105 few operations maintenance service to assist day to day operational task such backups, configuration sync.
As these features have system wide influence and might affect the availability of the Gateway and services, we provided limitations on the usage of the features.
For backups - see limitations here.
For configuration sync - see limitations here.
For firmware upgrades - see limitations here
Operating System supported locale
The only supported operating system locale definition for DPOD is en_US.UTF-8 as described in the installation prerequisites.
Object names in non-English languages may be partially supported.
Known workarounds:
None.
Limited functionality is provided when DataPower has language different than English
Choosing language in DataPower will impact your syslog records. This will cause DPOD to provide limited analysis on records that are not in English.
Known workarounds:
Change language of your monitored device to English (en).
...
None. Resolution of this issue is part of the short-term product Roadmap.
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.
...
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.
Duplicate Syslog messages appear in Raw Messages
DPOD uses several Syslog log targets in different locations and configurations. By design, it is collecting some error messages twice, and those messages appear in the Raw Messages page or in the Raw Messages tab of a single transaction. This duplication does not break any feature and is required for the correct behavior of DPOD.
Known workarounds: None.
Payload size does not include response size (only request size)
...