IBM DataPower Operations Dashboard v1.0.17.0

A newer version of this product documentation is available.

You are viewing an older version. View latest at IBM DPOD Documentation.

Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Symptoms

  • In DPOD dashboards, Transactions page and Raw Messages page, many transactions and log messages appear twice.

  • All transactions/messages usually belong to the same domain or device.

Cause

  • DPOD uses DataPower gateway log targets to get the transactional data from the DataPower gateways. Each domain in the DataPower gateway contains one or more log targets for DPOD.

  • Since it is possible to connect a single domain or a device to one or more DPOD instances (e.g. for HA), the log target names include the DPOD environment name (DPOD-MSC-<env name>-<suffix>).

  • Duplicate transactions and messages happen when there are duplicate log targets, with different environment names, but with the same destination DPOD instance (host name / IP).

  • Consider the following scenario as an example of such a case:

    • DPOD env1 is installed. A DataPower gateway is then added and set up to send transactional data to DPOD env1. This will create DPOD-MSC-env1-<suffix> log targets on all of its domains.

    • DPOD env1 is then uninstalled, without removing the DataPower gateway from DPOD Web Console, which leaves the log targets as is in the DataPower Gateway.

    • DPOD env2 is then installed on the same machine/IP address of the old env1 instance (for example, to change the architecture of DPOD from a Medium installation to a High installation to be able to process more TPS). The same DataPower gateway is then added and set up to send transactional data to DPOD env2. This will create additional DPOD-MSC-env2-<suffix> log targets on all of its domains.

    • Now, each log message will be sent twice - once from the DPOD-MSC-env1-<suffix> log target and once from the DPOD-MSC-env2-<suffix> log target, both will be sent to the same DPOD instance and will be shown twice.

Resolution

  • Inspect the log targets in the domains of the DataPower gateway, find the duplicate log targets with the wrong/old environment name, and delete them.

  • In the future, before DPOD uninstallation, make sure to remove all DataPower gateways from DPOD Web Console. This will provide you with the option to remove all log targets from the DataPower gateway as part of its removal from DPOD, and will prevent the duplication if this DataPower gateway will be added to another DPOD instance that will share the same machine/IP address.

  • No labels

IBM DataPower Operations Dashboard (DPOD) v1.0.17.0