DPOD was is designed for deployment using either a standalone (All-in-one) or a distributed topology using remote DPOD collectors.
There are 4 basic deployment options for DPOD:
- All-In-One with a single network interface
- All-In-One with two network interfaces
- All-In-One with External Self Service Consoleexternal self service web console
- All-In-One with DPOD Remote remote collector
- High Availabilityavailability, Resiliency and Disaster Recovery
TODO HK: replace all pictures - rename IDOD to DPODresiliency and disaster recovery
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 the DataPower Gateway and accessing the DPOD consoleWeb Console.
This scenario is appropriate for cases in which there is 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 in this deployment scenario:
- Network Interface 1 – for communicating with the DataPower Gateway
- Network Interface 2 – for user access to the accessing DPOD Web Console.
This deployment scenario is appropriate when a separation is required between network access from console Web Console users and DataPower GatewaysGateway.
Note: It is the System Administrator’s responsibility to
...
configure the second interface and make the proper static
...
routing definitions
...
.
...
Scenario 3: All-In-One with External Self Service Web Console
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.
...
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.
The 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 they 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.
Scenario 4: All-In-One with DPOD Remote Collector
This deployment scenario addresses deploying DPOD to monitor geographically dispersed locations. Communication with these locations is performed over WAN, and are susceptible to challenges of limited or unreliable network connectivity. To address this scenario, DPOD provides the ability to deploy instances of the DPOD Remote Collector alongside the All-In-One DPOD instance.
A Remote Collector is normally deployed in sites which are geographically separated from the DPOD main installation site. A Remote Collector deployed in a site communicates with the DataPower Gateways there using DPOD agents. The data it collects is then sent asynchronously to the DPOD main installation site.
This setup is appropriate when the existing DataPower Gateway deployment includes geographically dispersed sites, especially if network access between them is unreliable or limited (e.g. because of bandwidth).
Please see detailed instructions and requirements for the DPOD Remote Collector deployment.
Scenario 5: High Availability, Resiliency and Disaster Recovery
DPOD can support supports a few HA-DR scenarios. For a list of supported scenarios and detail detailed explanation please review the section High Availability, Resiliency or Disaster RecoveryTODO HK - add HA Scenario details.
DPOD is not supporting Data Replication as the amount and rate of the new data to be processed is high and the resources required to support the replication are usually found as not cost effective.
DPOD HA-DR capabilities are focus on the HA of the product components without the Store collected data.