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 console
- All-In-One with DPOD Remote remote collector
- High Availabilityavailability, Resiliency resiliency and Disaster Recoverydisaster recovery
TODO HK: replace all pictures - rename IDOD to DPOD
...
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 Console
...