Scenario 1: All-in-One with a Single Network Interface

This is the most common deployment scenario. All DPOD components reside on the same appliance (either virtual or physical).

A single network interface is used both for communicating with DataPower Gateways and accessing DPOD Web Console.

This scenario is appropriate for cases in which there are no organizational restrictions on providing users with direct access to DPOD’s IP address.

Scenario 2: All-in-One with Two Network Interfaces

In this deployment scenario, all DPOD components reside on the same appliance (either virtual or physical). To address network and access restrictions, DPOD uses two network interfaces:

• Network Interface 1 – for communicating with the DataPower Gateways.
• Network Interface 2 – for accessing DPOD Web Console.

This deployment scenario is appropriate when a separation is required between network access from Web Console users and DataPower Gateway.

Note: It is the System Administrator’s responsibility to configure the second interface and make the proper static routing definitions.

Scenario 3: Federated Deployment (Cell Environment)

Federated architecture best fits customers that execute high load (thousands of transactions per second or more) in their gateways.

The cell environment implements the federated architecture by distributing DPOD's Store and DPOD's agents across different federated servers.

The cell environment has two main components:

• Cell Manager - a DPOD server (usually virtual) that manages all Federated Cell Members (FCMs), as well as providing central DPOD services such as the Web Console, reports, alerts, resource monitoring, etc.
• Federated Cell Members (FCMs) - DPOD servers (usually physical with very fast local storage) that include Store data nodes and agents (Syslog and WS-M) for collecting, parsing and storing data.

The cell environment does not replicate any data between the members, so adding more members will not provide any HA / DR capabilities.

For more information, see Setup a Cell Environment.

Scenario 4: All-in-One with External Self Service Web Console (Deprecated)

In this deployment scenario two DPOD instances are deployed. The first one is the All-In-One, internal instance which is fully operational. The second one is an external Self-Service Web Console that does not store data. It only serves as a UI component, communicating with the internal DPOD instance over HTTP.

This deployment scenario supports both single and dual network interfaces, as specified in the preceding scenarios.

An organization should consider using this deployment scenario when DPOD users are members of a different network to DPOD itself, or when a separation is required between the user interface and the data stored in the system.

DPOD's External Self Service Console is an additional installation of DPOD. This second installation connects to the primary DPOD and enables developers to still use DPOD while only accessing the external DPOD, and does not require them to access through a more-secure network. This setup allows administrators to prevent unnecessary access to DataPower.

Using this deployment, developers will have access to Investigate.

High Availability, Resiliency and Disaster Recovery

DPOD supports a few HA-DR scenarios. For a list of supported scenarios and detailed explanation, please review the section High Availability, Resiliency and Disaster Recovery.