...
DataPower Gateway firmware 10.5.x, 10.0.x and 2018.4.x.
Some functionalities are also available for lower firmware levels. For more details please see Release Notes.API Connect 10.0.x, 2018.4.x and 5.0.8.x.
DPOD only supports gateways with supported firmware levels that meet the minimum system requirements for DataPower Gateways.
The DataPower Gateway language must be set to English.
...
Supported Hypervisors
DPOD can be installed on either a virtual environment (hypervisors) or physical servers (Intel(C) based CPUs), depending on the required performance.For a production environment suitable for hypervisor (virtual environment), the virtual appliance is supported on the following VMware hypervisorsinfrastructure (hypervisor). The following hypervisors are supported for running a DPOD production installation:
VMWare ESX - v6.0, v6.5, v6.7, v7.0
VMWare Workstation/Player - v14, v15, v16
VMware Fusion - v11.0, v11.5, v12.x
PureApp (only on Intel Processors) - no pattern yet available, can be provided only as an imported OVA.For Hyper V support - contact your IBM sales representatives.
Hyper-V
DPOD is NOT currently tested on Hyper-V, and there are currently no plans to add such testing in the future. Therefore it cannot be guaranteed that the installation of DPOD on Hyper-V works, nor can the performance of such an installation be guaranteed. If a customer decides to install DPOD on Hyper-V:
The support will be limited to application bugs and issues that affect other hypervisors as well (issues that are not specific to Hyper-V).
The customer might be asked to install DPOD on a supported infrastructure (such as VMware or physical servers) to prove that the issue is not specific to Hyper-V, in order to get support.
Note: DPOD can also be installed on physical servers (it might even be required for high loads), which can provide an alternative for customers that only own Hyper-V for virtualization. More information is available below.
Supported Physical Hardware
DPOD can be installed on physical servers (with Intel(C) based CPUs), especially when the load is high and the performance requires so. See the resources requirements listed below for more information.
Physical hardware should be purchased according to specifications provided by support L3 team in a short sizing process.
Resources Requirements
DPOD offers 6 deployment profiles:
...
Available in Edition | Deployment Profile | Goal | TPS Limit(4) | Supports Virtual Environment | Cores | RAM | Storage |
|---|---|---|---|---|---|---|---|
Developer | Development | Developers only. In rare cases can be used for functional POCs. Under restricted license. | 2-3 TPS | Can be virtual (5) | 2 cores (1) | 4 GB (3) | Single disk: 30GB |
Standard | Minimal | POCs and evaluation. | 5 TPS | Can be virtual (5) | 4 cores (1) | 18 GB (3) | Single disk: 200-400 GB |
Standard | Low | Environment with low load levels | 40 TPS | Can be virtual (5) | 6 cores (1) | 32 GB (3) | OS: 40 GB |
Standard | Medium | Environment with moderate load | 80 TPS | Can be virtual (5) | 8 cores (1) | 64 GB (3) | OS: 40 GB |
Standard | High | Environment with moderate load | 120 TPS | Can be virtual, but not recommended (5) | 16 cores (1) | 128-256 GB (3) | OS: 40 GB |
Standard | High_20dv | Environment with medium to very high load | 200-2750 TPS (6) | Must be installed on a physical server | Needs sizing (6) | Needs sizing (6) | Needs sizing (6) |
Standard | Environment with very high load that requires several DPOD servers | >2750 TPS (6) | Must be installed on physical servers | Needs sizing (6) | Needs sizing (6) | Needs sizing (6) |
...
(6) Customers will be provided with specifications after a short sizing process with support L3 team.
...