/
Hardware and Software Requirements

IBM DataPower Operations Dashboard v1.0.23.x

Hardware and Software Requirements

Owned by Copy Page Tree
Last updated: Mar 23, 2025 by Amit Munwes
6 min read

In this page:

Supported DataPower Gateways

The following DataPower gateways can be monitored and managed by DPOD:

Supported Hypervisors

DPOD can be installed on a virtual infrastructure (hypervisor). The following hypervisors are supported for running DPOD:

  • VMware ESXi v7.x-v8.x with Intel processors.

  • VMware Workstation/Player v16.x-v17.x with Intel processors.

  • VMware Fusion v12.x-v13.x on Mac with Intel processors.

  • AWS EC2 Instance (Virtual Machine) with Intel processors (using Non-Appliance installation mode only).

  • Microsoft Azure Virtual Machine with Intel processors (using Non-Appliance installation mode only).

Supported Physical Hardware

DPOD can be installed on physical servers with Intel processors, 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 the DPOD support team in a short sizing process.

Supported Kubernetes Versions

See Cloud Agent Prerequisites for supported Kubernetes / OpenShift Container Platform (OCP) versions for deploying the DPOD Cloud Agent component.

Operating System Requirements (only applicable to Non-Appliance mode)

  • RHEL v8.3-v8.10, v9.4-v9.5 - x86-64 bit only.

  • Rocky Linux v8.3-v8.10, v9.4-v9.5 - x86-64 bit only.

  • Some maintenance or advanced configuration tasks requires root or a user capable of running the sudo command (e.g. installation, upgrade, backup and restore of the DPOD application).

  • Review the Operating System Requirements for Non-Appliance Mode and work with your Linux team to configure the OS properly.

  • Third-party software such as antivirus, cybersecurity, monitoring, APM, endpoint protection, backup, etc. might significantly decrease the performance of DPOD and impact its functionality. During the resolution of issues, DPOD support will ask the customer to disable any 3rd party software in order to isolate the issues and verify their source. Support cannot be provided if the 3rd party tools are not disabled.

Resources Requirements and Deployment Profiles

The required resources depend on the type of installation, the expected TPS (Transactions Per Second) / EPS (Events Per Second) rate and the duration of the retention period. Make sure you are familiar with DPOD’s Installation Scenarios before choosing a deployment profile.

  • For up to 1,000 TPS / 50,000 EPS (total across all DataPower gateways), choose one of the options from the table below.

  • For over 1,000 TPS / 50,000 EPS (total across all DataPower gateways), complete a sizing process by opening a support ticket with IBM Support.

Note:

  • It is not possible to change the deployment profile after DPOD is installed. In order to change from one deployment profile to another, a new installation of DPOD is required, discarding the old data collected so far.

  • Virtual deployments performance cannot be guaranteed, since it depends on the server hosting the VM (e.g: ESXi), its configuration, the overall load it is experiencing at any given time from any of its VMs, and especially the performance of the remote storage. This may result with a lower or higher performance for the same resources in different environments.
    To ensure best performance in virtual deployments:

    • The virtual machine configuration should be set to have reserved CPUs.

    • The virtual machine configuration should be set to have reserved memory.

    • The virtual machine should have no snapshots.

  • It is recommended to conduct a performance test to determine the actual performance on your specific environment. The performance test should be conducted when the DPOD data directories are at ~70% utilization. Gradually increase the TPS load (at ~30 minutes intervals) until DPDO starts to report internal alerts of dropped messages.

  • If the TPS/EPS is too high and DPOD is unable to process all the incoming messages, some will be dropped, causing DPOD to show unreliable data (some transactions, errors or transactional data might be missing). When messages are dropped, an internal alert is generated and displayed in the DPOD Web Console (under Manage → DPOD Health → Internal Alerts).

Edition

Deployment Profile

Goal

Expected TPS/EPS

Virtual / Physical

Cores

RAM

Storage

Edition

Deployment Profile

Goal

Expected TPS/EPS

Virtual / Physical

Cores

RAM

Storage

DPOD Simulator

Development

Demonstration, development and evaluation only

5 TPS (1)
250 EPS

Several containers

8 cores (2)

12 GB (3)

25 GB free space in the Docker working directory (/var/lib/docker)

Docker Container for Developer

Development

Demonstration, development and evaluation only

5 TPS (1)
250 EPS

Container

2 cores (2)

5 GB (3)

6 GB free space in the Docker working directory (/var/lib/docker)

Developer

Development

Demonstration, development and evaluation only

5 TPS (1)
250 EPS

Virtual server

2 cores (2)

5 GB (3)

Single disk: 65 GB

Standard

Minimal

Demonstration, development and evaluation only

5 TPS (1)
250 EPS

Virtual server

4 cores (2)

18 GB (3)

Single disk(6): 200-400 GB

OR

3 disks: (4)
OS: 50 GB
App/Logs: 100 GB
Data: 100-300 GB

 

Standard

Low

All-in-One single server installation

250 TPS (1)
12,500 EPS

Virtual server

4 cores (2)

32 GB (3)

3 disks: (4)
OS: 50 GB
App/Logs: 100 GB
Data: 100-1000 GB

Standard

Medium

All-in-One single server installation

500 TPS (1)
25,000 EPS

Virtual server

8 cores (2)

64 GB (3)

3 disks: (4)
OS: 50 GB
App/Logs: 100 GB
Data: 300-2,000 GB

Standard

High

All-in-One single server installation

1,000 TPS (1)
50,000 EPS

Virtual server

16 cores (2)

128 GB (3)

3 disks: (4)
OS: 50 GB
App/Logs: 100 GB
Data: 1-5 TB

256 GB (3)

Data: 5-8 TB

Standard

High_20dv

All-in-One single server installation

5,000 TPS (1)
250,000 EPS

Physical server

Needs sizing (5)

 

Standard

Federated Architecture (Cell environment)

Environments with a high level of traffic (TPS)

5,000 TPS (1)
250,000 EPS

Virtual servers

Needs sizing (5)

Standard

Federated Architecture (Cell environment)

Environments with a high level of traffic (TPS)

25,000 TPS (1)
1,250,000 EPS

Physical servers

Needs sizing (5)

(1) The TPS is the maximum total transactions load across all devices/domains connected to DPOD. The sizing assumes 50 events (e.g.: log messages) per transaction.
(2) To ensure best indexing performance, the virtual machine configuration should be set to have reserved CPUs, and the hosting server (e.g.: ESXi) CPU utilization should not exceed 80%.
(3) To ensure best query performance, the virtual machine configuration should be set to have reserved memory, and the hosting server (e.g.: ESXi) memory utilization should not exceed 80%.
(4) The presence of virtual machines snapshots may significantly impact the I/O performance. To ensure best indexing and query performance, the virtual machine should have no snapshots.
(5) Customers will be provided with specifications after a short sizing process with support L3 team.
(6) Using a single disk is possible by specifying a special command line option. For more information, consult your DPOD SME that supports the POC/evaluation process.

CPU Requirements

  • DPOD supports Intel processors only.

  • On AWS, DPOD was providing the expected performance with 3rd generation Intel Xeon Scalable processors (up to 3.5 GHz), used for example by the r6i.4xlarge instance type (with 16 virtual CPUs and 128 GB RAM).

Storage Requirements

  • DPOD is I/O intensive, as it needs to persist all logs and information at very high rates. Therefore, for most of the installations, it needs to be configured with very fast disks, and with at least 3 separate disks (OS, app/logs, data).

  • Some configurations, such as the Cell environment, require additional data disks.

  • Usage of slow disks will impact the maximum TPS that DPOD can process and the performance of queries.

  • For each 1 TB of data 64 GB of RAM is recommended for responsive queries (dashboards and filters).

  • NFS is not supported for the data disk, as the Store relies on file system behavior that NFS does not supply. Data corruption and other problems can occur.

  • Software RAID (such as RHEL built-in software RAID) is not supported.

  • The data disk retention is automatically managed by DPOD. For each type of data (transactional, resources, payload, etc.), once its quota is full, old data will be discarded to make room for new data of the same type. A bigger disk size will hold a longer history.

  • On AWS, DPOD was providing the expected performance with an EBS gp3 volume with 16,000 IOPS and 1,000 MB/s throughput.

Network Requirements

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

  • Some configurations, such as the Cell environment, require two network interfaces.

  • Firewall requirements are detailed in Firewall Requirements.

User Registry Requirements

  • LDAP/OIDC registry is required to enable roles and permissions in production environments.

Client Requirements

DPOD's Web Console requires the following for administration and end-users:

  • A minimum screen resolution of 1280x720 pixels.

  • Supported web browsers are:

    • Firefox - latest 2 versions

    • Chrome - latest 2 versions

    • Safari -  latest 2 versions

    • Microsoft Edge Chromium - latest 2 versions

 

Related content

Copyright © 2015 MonTier Software (2015) Ltd.