Page Comparison

...

• 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 deployment profile of DPOD from a Medium installation profile to a High installation profile 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.

...