DPA 12.0 System Requirements

See the following sections for minimum supported system requirements:

Port requirements
DPA server requirements
Repository database requirements
Virtual environment
Web browsers
MySQL requirements
Java requirements

For information about the database instances you can register for monitoring, see Database instances DPA can monitor.

Port requirements

Port	Protocol	Service or Process	Direction	Encryption	Description
8123	HTTP	Windows: Ignite PI Service Linux: java/tomcat	Inbound Outbound		Default HTTP port for web server
8124	HTTPS	Windows: Ignite PI Service Linux: java/tomcat	Inbound Outbound	TLS 1.0 TLS 1.1 TLS 1.2	Default HTTPS port for web server
8127	TCP	Windows: Ignite PI Service Linux: java/tomcat	Internal		Internal Tomcat shutdown port
80	HTTP	Windows: Ignite PI Service Linux: java/tomcat	Inbound Outbound		Default HTTP port for web server (Amazon Machine Images only)
443	HTTPS	Windows: Ignite PI Service Linux: java/tomcat	Inbound Outbound	TLS 1.0 TLS 1.1 TLS 1.2	Default HTTPS port for web server (Amazon Machine Images only)

DPA server requirements

You can install SolarWinds DPA on any physical or virtual Windows or Linux server that supports the Java Runtime Environment (JRE) version 1.8.

You can also launch DPA in the cloud:

In the Amazon Web Services (AWS) Marketplace from an Amazon Machine Image (AMI).
- The AMI contains a DPA server on Linux with no repository.
- DPA uses AWS Marketplace Metering Service to calculate charges.
In the Azure Marketplace.
- The DPA virtual machine contains a DPA server on Windows and a built-in Microsoft SQL Server database instance configured as the DPA repository.
- Individual licenses must be purchased.

Self-managed DPA server requirements

The CPU and RAM requirements depend on the number of database instances you plan to monitor.

If you register VMware, increase the CPU and RAM requirements by 50%.

Hardware / Software	1 - 20 Monitored DB Instances	21 - 50 Monitored DB Instances	51 - 100 Monitored DB Instances	101 - 250 Monitored DB Instances*
CPUs	1	2	4	4
RAM dedicated to DPA	1 GB	2 GB	4 GB	8 GB
Disk space	2 GB minimum 4 GB recommended
Operating System	Windows Server 2016 Windows Server 2012 R2 Windows 10 (evaluation only) Linux
Operating System Architecture	64-bit
Character sets	To support a multibyte language, the DPA server, repository, and monitored instances must be configured with the same character set.

* If you plan to monitor more than 250 database instances, consider using more than one DPA server and linking the servers together.

Requirements for an AWS DPA server

The minimum required AWS instance type for the DPA server AMI is t2.medium. Smaller instance types are not supported.

A t2.medium size instance is typically powerful enough to monitor 20 database instances. You might need a larger instance type to reliably monitor more than 20 database instances.

Requirements for an Azure DPA server

SolarWinds recommends two or more database throughput units (DTU) per monitored database instance. For more information, see the Azure SQL Database DTU Calculator.

The minimum required Azure tier is standard s0.

Repository database requirements

The repository database stores the data collected by SolarWinds DPA. A supported database instance must be installed on the database server.

Do not host the repository on a database instance that you plan to monitor, because this affects the performance of that instance.

Supported database versions

Database	Edition	Version
Microsoft SQL Server	Standard Enterprise	2017 (Windows or Linux) 2016 SP2 2014 SP2 2012 SP4
Azure SQL	Standard Service Tier or higher	V12
MySQL	Community Enterprise	5.7.9 5.6.10 Amazon RDS for MySQL 5.7.9 Amazon RDS for MySQL 5.6.10 Aurora 5.6.10a Note: MySQL 8.0 is not supported for use as a DPA repository.
Oracle	Standard Enterprise	12.2 (single tenant and multitenant) 12.1 (single tenant and multitenant) 11.2

Although DPA will work with the Express editions of Oracle and SQL Server, SolarWinds does not officially support these editions for the repository because of the database size limits. If you need a free database for an evaluation, SolarWinds recommends using a MySQL database.
You can use an Amazon Relational Database Service (RDS) for MySQL instance as a repository.
You can host a self-managed Oracle or SQL Server database on Amazon EC2 to use as your repository.
If you choose Azure SQL as your repository, SolarWinds recommends two or more database throughput units (DTU) per monitored database instance. For more information, see the Azure SQL Database DTU Calculator.

Repository database server

If you install DPA on the same server as the repository database, you need these requirements in addition to the DPA server requirements. If you register VMware, increase the CPU and RAM requirements by 50%.

These are estimates. They are based on testing done with an average of 2-3 active sessions per monitored instance. If you are monitoring busy instances with an average of more than 2-3 active sessions, please adjust accordingly.

Hardware / Software	1 - 20 Monitored DB Instances	21 - 50 Monitored DB Instances	51 - 100 Monitored DB Instances	101 - 250 Monitored DB Instances
CPUs	2	2	4	4
Database cache available for DPA	4 GB	8 GB	8 GB	16 GB
Disk space	The amount of disk space your repository uses is determined by the number of database instances you are monitoring and the activity level of each instance: Low: 1 GB Medium: 3 GB High: 5 GB Example: You are monitoring five low, three medium, and two high activity database instances. (5 × 1 GB) + (3 × 3 GB) + (2 × 5 GB) = 24 GB Reserve at least 24 GB to provide adequate disk space for this repository database.

Hardware / Software

1 - 20 Monitored DB Instances

21 - 50 Monitored DB Instances

51 - 100 Monitored DB Instances

101 - 250 Monitored DB Instances

CPUs

Database cache available for DPA

4 GB

8 GB

16 GB

Disk space

The amount of disk space your repository uses is determined by the number of database instances you are monitoring and the activity level of each instance:

Low: 1 GB
Medium: 3 GB
High: 5 GB

Example: You are monitoring five low, three medium, and two high activity database instances.

(5 × 1 GB) + (3 × 3 GB) + (2 × 5 GB) = 24 GB

Reserve at least 24 GB to provide adequate disk space for this repository database.

Repository scalability depends on many things, including the database vendor and configuration, the specifications of the repository server, other activity on the repository server, and the activity levels of the monitored database instances.

Required administrator credentials

You must know the following credentials for the database instance hosting your repository.

Repository database type	Credentials
SQL Server	SYSADMIN
Oracle	database administrator (DBA)
MySQL	repository administrator Alternatively, you can: Provide the credentials of a user with privileges to create the repository user. The privileged user requires the Create, Drop, and Create User permissions and must be able to grant the following permissions: `GRANT ALL PRIVILEGES on <databaseName>` Where `<databaseName>` is the repository database you create or select when you set up the MySQL repository storage. Run a script to create the repository user.
Azure SQL Database	repository administrator Alternatively, you can: Provide the credentials of a user with privileges to create the repository user. This user must be a member of the db_owner role. Run a script to create the repository user.

Virtual environment

In a virtual environment, DPA can remotely connect to the following to monitor the virtual environment that virtualized database instances are running on. The virtualized database instances must be registered separately from the virtual environment.

Software	Version
VMware vCenter Server	6.5 6
VMware ESX/ESXi Host	6.5 6

Web browsers

You can use the following browsers to access the SolarWinds DPA web interface:

Microsoft Edge
Microsoft Internet Explorer 11
Do not use IE compatibility view. It may cause SolarWinds DPA to function incorrectly.
Mozilla Firefox: latest stable version
Google Chrome: latest stable version

MySQL requirements

SolarWinds recommends the following settings to optimize reporting capabilities for a MySQL database instance.

MySQL Performance Schema

The Performance Schema monitors server events and collects performance data. If the Performance Schema is not enabled, SolarWinds DPA provides limited data. Monitoring with the Performance Schema disabled excludes the following data:

All instrumented wait events
All wait operations
All file wait time, broken out by file
All object wait time, broken out by index and table
SQL statistics
Performance-schema dependent alerts

The Performance Schema must be enabled at server startup. In MySQL versions 5.6.6 and later, the Performance Schema is enabled by default.

Global and Thread Instrumentation

Global Instrumentation and Thread Instrumentation must be enabled in the Performance Schema configuration. Disabling these instruments has the same effect as disabling the Performance Schema.

By default, SolarWinds DPA enables these instruments in the configuration. However, if you select the Leave As Is option for Performance Schema setup, you must verify that Global Instrumentation and Thread Instrumentation are enabled in the existing Performance Schema configuration.

show_compatibility_56 system variable

If the monitored database instance is MySQL 5.7.6 or later, SolarWinds recommends turning on the show_compatibility_56 system variable. If this variable is on, SolarWinds DPA can collect data for all metrics.

If this variable is off and the Performance Schema is enabled, SolarWinds DPA cannot collect data for the following metrics:

Selects
Inserts
Updates
Deletes

Java requirements

DPA requires JRE 1.8 on the DPA server, and DPA ships with this version of Java for Windows and Linux. If you are installing DPA on a supported operating system, no action is required.

For unsupported operating systems, you must ensure that JRE1.8 is installed on the DPA server. If you need to upgrade the JRE:

Download and install JRE 1.8.
Remove old Java information by deleting the cat.txt and cat.end files from the following directory:
<DPA_Home>/iwc/tomcat/ignite_config/
At a command line, go to the DPA installation directory.
Enter the following command:
./startup.sh