Documentation forWeb Performance Monitor

WPM 2020.2 System Requirements

Release Date: June 4, 2020

Updated August 25, 2020

These recommended system requirements are for SolarWinds Web Performance Monitor (WPM) 2020.2 as a single product installed on Orion Platform 2020.2.

Note the following details about system requirements:

Software requirements for the Orion server

The following table lists software requirements and recommendations for a WPM installation on both physical and virtual systems.

Software Requirements
Operating system
  • Microsoft Windows 10
  • Microsoft Windows Server 2012 R2*
  • Microsoft Windows Server 2016
  • Microsoft Windows Server 2019

*Support for Microsoft Windows Server 2012 R2 is included in WPM 2020.2 so WPM 2.2.3 customers can upgrade to the latest version of WPM. For the best experience, SolarWinds recommends using Windows Server 2016 or 2019 for the Orion server.

Desktop operating systems, such as Windows 10, 64-bit Pro or Enterprise are supported for evaluation environments only. For a smooth transition from your evaluation to production deployment, SolarWinds recommends that you avoid installing evaluations on desktop operating systems.

Do not install WPM on domain controllers; or Microsoft SharePoint, Microsoft Exchange, or BlackBerry servers.

Operating system languages
  • English (UK or US)
  • German
  • Japanese
  • Simplified Chinese
IP address version
  • IPv4
  • IPv6
  • Dual stack

CIDR notation is not supported for IPv6 addresses.

Web server

If you're not using Windows Authentication, make sure Anonymous Authentication is enabled for the SolarWinds NetPerfMon website. Anonymous Authentication is used with the default forms-based authentication.

IIS is installed by the SolarWinds Orion Installer. You can install this software manually to reduce installation time or network bandwidth.

Microsoft .NET Framework

.NET 4.8 or later

Run the same version of. NET on your primary Orion server and any Additional Polling Engines or Additional Web Servers in the environment.

SolarWinds recommends installing .NET on your primary Orion server and all scalability engines before installing WPM. See this article for details.

Orion Web Console browser

The Orion Platform supports the two latest versions of the following web browsers available on the release date:

  • Firefox
  • Chrome

The Microsoft Edge browser is also supported.

Account privileges

SolarWinds recommends that Orion administrators have local administrator privileges on the Orion server to ensure full functionality of local Orion Platform tools. Orion user accounts limited to the Orion Web Console do not require local administrator privileges.

To use domain accounts with WPM, each account should have local administrator privileges and be able to log into the Orion Web Console locally.

SolarWinds Pingdom

To use WPM recordings for Transaction Monitoring in Pingdom, you'll need an active Pingdom account to generate Pingdom API tokens for Web Transaction Recorders. See the WPM Getting Started Guide for details.

Not using Pingdom yet? Click here to start your 14-day free trial.

Port requirements

Return to top

  • Port requirements in the table below apply to the Orion server. In addition, open the following TCP ports on remote machines that host a Web Transaction Recorder or WPM Player:
    • 80, for HTTP traffic
    • 443, for HTTPS traffic
    • 17777, for SolarWinds traffic
  • Ports 4369, 25672, and 5672 are open by default on the main server for RabbitMQ messaging. These ports can be blocked by the firewall. If running High Availability, ensure ports 4369 and 25672 are open.
  • RPC ports > 1024 (TCP, bidirectional) are used by the Job Engine v2 process to communicate with Windows nodes.
Port # Protocol Service/Process Direction Description Encryption

User-defined default: 22

SSH

SolarWinds Job Engine v2

IIS

Outbound from the Orion server to the device

Access Cisco Adaptive Security Appliance (ASA) devices through the Command-Line Interface (CLI).

Device-based
25 TCP SolarWinds Alerting Service V2 Outbound

SMTP port for non-encrypted messages

 
53 UDP SolarWinds Job Engine V2 Bidirectional

Resolve DNS queries

 
80 TCP IIS Inbound

Default Additional Web Server (AWS) port. If you specify any port other than 80, you must include that port in the URL used to access the Orion Web Console. For example, if you specify 192.168.0.3 and port 8080, the URL used to access the Orion Web Console is http://192.168.0.3:8080.

Open the port to enable communication from your computers to the Orion Web Console.

 
135 TCP Microsoft EPMAP (DCE/RPC Locator service) Bidirectional

WMI uses TCP Port 135 to initiate communication with the remotely managed host, then switches to any random high port anywhere between TCP ports 1024 — 65535. Click here for details.

 
161 UDP SolarWinds Job Engine v2, SolarWinds Cortex (communication) Bidirectional

Send and receive SNMP information.

SNMP v1 and v2 are unencrypted.

SNMP v3 uses AES and 3DES encryption.

162 UDP

SolarWinds Trap Service

SNMP Informs

Bidirectional

Receive trap messages

 
443 TCP IIS Inbound

Default port for HTTPS binding. Also used for bi-directional ESX/ESXi server polling.

SSL
465 TCP SolarWinds Alerting Service V2 Outbound

SMTP port used to send TLS-enabled email alert actions.

SSL
514 UDP SolarWinds Syslog Service Inbound

Receive syslog messages

 
587 TCP SolarWinds Alerting Service V2 Outbound

SMTP port used to send TLS-enabled email alert actions.

TLS
1433 TCP

SolarWinds Alerting Service V2

SolarWinds Administration Service

SolarWinds Information Service

SolarWinds Information Service V3

SolarWinds Orion Module Engine

Outbound

Used for communication from the Orion server to the Orion database server.

 
1434 UDP

SolarWinds Alerting Service V2

SolarWinds Administration Service

SolarWinds Information Service

SolarWinds Information Service V3

SolarWinds Orion Module Engine

SQL Server Browse Service

Outbound

Used for communication with the SQL Server Browser Service to determine how to handle certain non-standard SQL Server installations.

Required only if your Orion database server is configured to use dynamic ports.

 
1801 TCP MSMQ Bidirectional

MSMQ WCF binding

WCF
5671 TCP RabbitMQ Bidirectional

For encrypted RabbitMQ messaging (AMQP/TLS) into the main polling engine from all scalability engines.

TLS 1.2
17777 TCP

SolarWinds Orion Module Engine

SolarWinds Information Service

SolarWinds Information Service V3

SolarWinds Cortex (communication)

Bidirectional

Used for communication between:

  • Orion services and SolarWinds Orion module traffic.
  • The Orion Web Console, the main polling engine, and all scalability engines.
  • The main Orion server and pool members.

RSA handshake, AES 256 communication using WCF

TLS 1.2 with Cortex

17778 HTTPS SolarWinds Agent Bidirectional

Supports access to the SWIS API and agent communication.

SSL
17781 TCP WPM Playback Player Bidirectional

The default port the WPM Player listens on. This port must be open between the Orion Server and the WPM Player for proper communications.

 
17782 TCP WPM Playback Player Bidirectional

Used for WPM Player-initiated communications.

 
17783 TCP WPM Playback Player Bidirectional

Used for automatic WPM Player updates.

 

Hardware requirements for the Orion server

Return to top

The following table lists minimum hardware requirements and recommendations for your Orion server on both physical and virtual computers. Use the minimum hardware configuration if you are evaluating the product or do not anticipate heavy usage.

  • Do not install Orion Platform products on the same server as SolarWinds Access Rights Manager (ARM).
  • SolarWinds strongly suggests using the recommended hardware configuration to avoid potential performance issues caused by a heavy load or custom configurations such as increased data retention or more frequent polling intervals.

Installing multiple Orion Platform products on the same computer may change the requirements.

Hardware requirements are listed by deployment size, based on SolarWinds NPM license levels. CPU recommendations for XL deployments use the PassMark Score. For details, see PassMark Performance Test (Copyright © 2019 PassMark® Software, obtained at https://www.cpubenchmark.net/high_end_cpus.html on April 24, 2019).

Feature

Small

SL100, SL250, SL500

Medium

SL2000

Large

SLX

XL

CPU Quad core processor or better Quad core processor or better Quad core processor or better CPUs with a total combined PassMark score of 7,000 or higher
Do not enable Physical Address Extension (PAE).
Hard drive space

10 GB minimum

20 GB recommended

15 GB minimum

40 GB recommended

30 GB minimum

40 GB recommended

40 GB minimum

50 GB recommended

Read/Write I/O performance of 800 IOPS

SolarWinds recommends two 146 GB 15K (RAID 1/Mirrored Settings) hard drives with a dedicated drive for the server operating system and Orion Platform installation.

Some common files may need to be installed on the same drive as the server OS. You may want to move or expand the Windows temporary directories.

Memory

6 GB minimum

8 GB recommended

8 GB minimum

16 GB recommended

16 GB minimum

32 GB recommended

16 GB minimum

32 GB recommended

Orion database server requirements

Return to top

The following table lists software and hardware requirements for your Orion database server using NPM license levels.

Do not install Orion Platform products on the same server as SolarWinds Access Rights Manager (ARM).

  • The Orion server and the Orion database must use separate servers.
  • If you install on a virtual machine, you must maintain your Orion database on a separate, physical drive.
  • You cannot install the Orion database on a SharePoint, Exchange or Blackberry server.
  • As of Orion Platform 2019.2, you can use Amazon RDS or Azure SQL as your database server. See the Orion Platform 2019.2 release notes for details.
  • As of Orion Platform 2019.4, you can use an Azure Managed Instance as your database server. See the Orion Platform 2019.4 release notes for details.
Feature

Small

SL100, SL250, SL500

Medium

SL2000

Large

SLX

XL

Microsoft SQL Server

Express, Standard, or Enterprise versions of:

  • SQL Server 2012*
  • SQL Server 2014
  • SQL Server 2014 SP1
  • SQL Server 2014 SP2
  • SQL Server 2016
  • SQL Server 2016 SP1
  • SQL Server 2016 SP2
  • SQL Server 2017
  • SQL Server 2019

*Support for SQL Server 2012 is included in WPM 2020.2 so WPM 2.2.3 customers can upgrade to the latest version of WPM. For the best experience, use SQL Server 2016 or later.

Enterprise versions of SQL Server:

  • 2012*
  • 2014
  • 2014 SP1
  • 2014 SP2
  • 2016
  • 2016 SP1
  • 2016 SP2
  • 2017
  • 2019

Recommendations

  • Use the 64-bit version of Microsoft SQL Server.
  • Use Express versions only for evaluations and small environments.
  • To gauge database size, consider that 5 WPM transactions with 5 to 10 steps each, and up to 25 actions each, using the default retention settings (7 days) typically consume 300 MB.
  • Use the Simple database recovery model to ensure best performance.
  • Use the Full database recovery model if your Orion Database is hosted on a SQL cluster or if you use Always On Availability. If so, back up your database regularly and ensure that the volume where you store transactions log has free space equal to or greater than the size of the Orion database. Transaction logs will continue to grow indefinitely until a database backup is performed and transactions are committed to the database. SolarWinds recommends daily database backups if using the Full database recovery model.
  • To reduce disk utilization when using SQL Server Express, shorten the Detailed Statistic Retention period on the Polling Settings page. The default value is 7 days. See Optimize the database used by Orion Platform products.
SQL Server collation
  • English with collation setting SQL_Latin1_General_CP1_CI_AS
  • English with collation setting SQL_Latin1_General_CP1_CS_AS
  • German with collation setting German_PhoneBook_CI_AS
  • Japanese with collation setting Japanese_CI_AS
  • Simplified Chinese with collation setting Chinese_PRC_CI_AS

SolarWinds products support a case-insensitive (CI) database on a CS SQL Server.

SolarWinds products do not support case-sensitive databases.

CPU

Quad core processor or better

Dual quad core processor or better

Dual quad core processor or better

CPUs with a total combined PassMark score of 32,000 or higher

Hard drive space

20 GB minimum

40 GB recommended

50 GB minimum

100 GB recommended

100 GB minimum

400 GB recommended*

500 GB minimum

1TB recommended

Read/Write I/O performance of 30,000 IOPs

190,000 IOPS or better recommended

1 Gbit dedicated NIC

  • Due to intense I/O requirements, a RAID 1+0 drive is strongly recommended for the Orion database, data, and log files with a dedicated drive for the server OS and tempdb files. Other RAID configurations can negatively affect SQL Server performance.
  • Mirrored drives for the OS and RAID 1+0 for database data files are recommended.
  • Solid state drives (SSD) are recommended for all components.

Some common files may need to be installed on the same drive as your server OS. You may want to move or expand the Windows or SQL temporary directories. See Working with Temporary Directories.

Memory

8 GB minimum

16 GB recommended

16 GB minimum

64 GB recommended

64 GB minimum

128 GB recommended

256 GB minimum

512 GB recommended

Authentication

Either mixed-mode or Windows authentication. If you require SQL authentication, you must enable mixed mode on your SQL server.

Other software

SolarWinds recommends installing Microsoft SQL Server Management Studio on your Orion database server. The Orion Installer adds the following x86 components if they are not found on your Orion database server:

  • SQL Server System Common Language Runtime (CLR) Types. Orion Platform products use secure SQL CLR stored procedures for selected, non-business data operations to improve performance.
  • Microsoft SQL Server Native Client
  • Microsoft SQL Server Management Objects

* SolarWinds recommends the following hard drive configuration for large deployments:

  • A hardware RAID Controller with a battery backed-up write back cache
  • Disk Subsystem 1 Array 1: 2x 146 GB 15K disks RAID 1 (mirroring) for the OS
  • Disc Subsystem 2 Array 2: 2x 146 GB 15K disks RAID 1 (Pagefile + Extra Storage)
  • Disk Subsystem 3 Array 3: with 6x 15k 146 GB or 300 GB disks configured in a RAID 1+0 array for your SQL MDF and FILEGROUPS.
  • Disk Subsystem 4 Array 4: with 4x 15k 146 GB or 300 GB disks configured in a RAID 1+0 array for your SQL LDF Transaction LOG file
  • Disk Subsystem 5 Array 5: with 4x 15k 146 GB or 300 GB disks configured in a RAID 1+0 array for your tempdb data file
  • Disk Subsystem 6 Array 6: with 4x 15k 146 GB or 300 GB disks configured in a RAID 0 array for your tempdb log file

Web Transaction Recorder requirements

Two types of WPM recorders are added to the Orion server when you install the primary WPM application, and you can also deploy recorders to remote systems.

Here are minimum requirements for remote systems that host a Web Transaction Recorder, which is based on Chromium 78.0.3904.130:

Resource Requirement
CPU Single processor with 1 GHz or more
Memory 2 GB
Operating system
  • x64 systems only
  • Windows 7, 8, 10
  • Windows Server 2008 R2, 2012, 2012 R2, 2016, and 2019

Keep scale and layout settings for Windows set to 100%, as described here.

TCP ports
  • 80, for HTTP traffic
  • 443, for HTTPS traffic
  • 17777, for SolarWinds traffic
  • Two random ports between 1024 and 65535 for inter-process communication between recorders, probes, and drivers.

    Configure firewalls to support the binding of random ports, between 127.0.0.1:1024 and 127.0.0.1:65535.

Here are minimum requirements for remote systems that host a Deprecated WPM Recorder:

Resource Requirement
CPU Single processor with 1 GHz or more
Memory 2 GB
Operating system
  • x64 systems only
  • Windows 7, 8, 10*
  • Windows Server 2008 R2, 2012, 2016*, and 2019*

*SSL certificate authentication is not supported on some OS. >> Learn more

TCP ports
  • 80, for HTTP traffic
  • 443, for HTTPS traffic
  • 17777, for SolarWinds traffic
Web browser

Internet Explorer 11

If your organization requires an earlier IE version, use IE 11 Document Mode to emulate earlier versions. Click here for details.

WPM Player requirements

Return to top

As described here, the WPM Player is a Windows service you can deploy to remote systems to simulate end user experiences with web applications by playing back recorded transactions.

Note the following details about the WPM Player service:

The following requirements apply to remote systems that host WPM Players:

Resource Requirement
CPU Quad core processor or better
Memory 3 GB
.NET Framework .NET 4.5
Operating system
  • Windows 7, 8, 10*
  • Windows Server 2008 R2, 2012, 2016*, and 2019*

*Steps with certificate validation may interrupt playback, as described here.

Account and security

Accounts can access the remote administrator share.

TCP ports
  • 80, for outbound HTTP traffic
  • 443, for outbound HTTPS traffic
  • 17777, for outbound SolarWinds traffic
  • 17781, for bidirectional, server-initiated (passive) communication mode
  • 17782, for bidirectional, player-initiated (active) communication mode
  • 17783, for bidirectional, automatic WPM Player updates

In addition, allow a random port between 1024 and 65535 for inter-process communication between WPM players, probes, and drivers.

Configure firewalls to support the binding of the random port, between 127.0.0.1:1024 and 127.0.0.1:65535.

Web browser

Internet Explorer 11

If necessary, use IE 11 Document Mode to emulate earlier versions. See this article for details.