Client Requirements

DPOD's web user interface requires the following for administration and end users:

The Web Console requires a minimum screen resolution of 1280 X 720.
Supported user web browsers are Firefox , Internet Explorer 11+ , Chrome 50+ , Safari 43+

Monitored Device (DataPower) Requirements

DPOD supports only the supported firmware detailed in this documentation.

If any of the the monitored devices attached to DPOD is to be upgraded to firmware versions 7.6.+ you MUST upgrade to DPOD 1.0.5.0+ before the firmware upgrade in order to be able to browse transactions from this device.

DPOD supports only DataPower with language set to english.

Server Requirements

Physical HW or Hypervisor

DPOD can be installed on either a Virtualized Environment (Hypervisors) or Physical server (Intel(C) based CPUs and supporting CentOS 7.x OS). Consult the table below for information to support this decision.

Hypervisor SW

For a production environment suitable for hypervisor (virtual environment), the virtual appliance is supported on the following VMware hypervisors:

VMWare ESX v5.5 , v6.0
VMWare Player - v12.0 , v12.5
VMWare Workstation - v12.0 , v12.5
VMware Fusion v8.0
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

Resource Requirements

DPOD offers 6 basic load configuration setups.

One load configuration architecture setup for development that exists only in the Developer ISO file! The Developer edition ISO file name is DPOD-Developer-CentOS-<version>.iso (Can be download from Fix Central)

Five load configuration architecture setups that exist for the Standard Edition are available in:

Appliance Mode (ISO file) - DPOD_CentOS_<version>.iso (Can be download from PPA) - for example: DPOD_CentOS_1.0.4.iso
Non-Appliance Mode (Compressed Executable file) - DPOD_RedHat_<version>.cef (Can be download from PPA) - for example: DPOD_CentOS_1.0.3.cef

The following table lists the typical usage characteristics for each setup edition, and the physical or virtual resources it requires.

Availability in Edition	Load Configuration Architecture Setup	Goal	TPS Limits recommended⁽⁴⁾	Supports Virtual Env	Cores ⁽¹⁾	Memory ⁽³⁾	Storage (GB)
Developer	Development	Developers only. In rare cases can be used for functional POCs. restricted license	2-3	Yes	2	3 GB	All: 20GB
Standard	Minimal	POCs and Evaluation. Limited history period to reduce memory requirements	5	Yes	4	18 GB	OS: 40 Install: 40 Data⁽²⁾: 100+
Standard	Low	Environment with low load levels	40	Yes	6	32 GB	OS: 40 Install: 40 Data⁽²⁾: 100+
Standard	Medium	Environment with Moderate load	80	Yes	8	64GB	OS: 40 Install: 40 Data⁽²⁾: 300+
Standard	High	Environment with High load	120	Yes, but not recommended	12	128GB	OS: 40 Install: 40 Data⁽²⁾: 1,000+
Standard	High_20dv	Environment with Medium load	200 Can be increased to 1500 TPS⁽⁵⁾	No. Must be installed on a physical server	16 (Physical)	200GB	OS: 40 Install: 40 Data⁽²⁾: 2,000
Standard	High_20dv	Environment with High load	1500 TPS⁽⁵⁾		20 (Physical)⁽⁵⁾	256GB	OS: 40 Install: 40 Data⁽²⁺⁵⁾: 8,000

Customers who need to handle more than 1500 TPS will be required to install multiple nodes.

High Load capacity plan sizing example

A customer wants to attach a pool of appliances to DPOD. This pool generates a peak of circa 10,000 TPS.

This customer will need to have 7 intel based physical servers, with hyperthreaded cpus, each with 256GB of memory, 20 physical cores and storage specification as described below.

1 Node = 1500 TPS

7 Nodes = 10,500 TPS.

Customers who plan to use more than one node are expected to submit a sizing questionnaire.

Each DPOD environment (up to 7 nodes) will support no more than 10,000 TPS.

Customers with higher load still are expected to create separate environments, each can handle up to 10,000 TPS.

⁽¹⁾ These could be cores on an 80% utilized ESXi

⁽²⁾ Local SSD preferred - should be located on a data store separated from the other disks

⁽³⁾ Best query performance is achieved by using reserved memory configuration

⁽⁴⁾ The TPS is the total transaction load across all devices/domains connected to DPOD

IBM DataPower Operations Dashboard may also be installed as a custom distributed edition (not All-in-One) that allows installation on several servers located across separate geographical locations.

This normally requires creating a custom architecture based on a sizing process.

⁽⁵⁾ To cater for 1500 TPS, customers are required to have 256GB memory, 20 Physical cores (each is HyperThreaded thus equivalent to a total of 40), Local storage with RAID0 across 4-8 SSD Disks (SAS 6GBs) - each supporting at least 80K Random Write IOPS 4KiB and write avg latency of less than 35 uSec.

Storage Recommendation

DPOD serves as a database and should therefore be configured to use very fast disks. For this reason, DPOD installation requires 3 separate DISKS for OS , Installatio and Data.
Usage of slow disks is not recommended and will impact the amount of time between creation of transaction logs and the availability of the data on DPOD's dashboards.
For Physical hardware installations that can utilize HW RAID services the following setup is recommend:
- RAID5 - 40GB - for OS disk
- RAID5 - 40GB - for App disk
- RAID0 - Depends on volume - for Data disk.

RAID Support

DPOD does not support the CentOS built-in RAID (Software Raid). The only supported RAID is the one handled by a controller

Network Requirements

DPOD requires at least one network interface for accessing DPOD's User Interface and communications with DataPower's Management Interface.

Operating System Requirements - Only applicable to Non Appliance mode

CentOS 7.2.0 - x86-64 bit or RHEL 7.2.0 - x86-64 bit only .
Server OS must be a fresh install without any other installed products .
In Non Appliance mode the OS support is not covered but recommendations will be provided.
Other 3rd party software products for backups, security and monitoring may be installed. However, due to diversity their impact is unknown.
During resolution of issues, DPOD support will ask the customer to disable these 3rd party tools, so that issues may be isolated and DPOD verified as their source. Support will not be provided if the 3rd party tools are not disabled.

Utility Software for Administrators

An SSH client to connect to the DPOD appliance once installed.
An FTP Client software to upload/edit files in the appliance when required .

Browser not supported