System Requirements

This section lists the system requirements for installing and working with Applications Manager.

Hardware Requirements

The performance of Applications Manager depends considerably on the CPU and memory of the system. The following table describes the recommended configuration of the system running the product on respective environments.

 
Professional Edition / Plugin Professional Edition

On-premise Setup

Number of Monitors Processor Memory Hard Disk
1 to 100



2 Core / 2.0 GHz and above

 3 GB RAM 50 GB & above
101 to 250 4 GB RAM 75 GB & above
251 to 500 8 GB RAM 100 GB & above
501 to 750 10 GB RAM 125 GB & above

Cloud VM Setup

Number of Monitors Processor Memory Hard Disk AWS recommended instance type Azure recommended instance size
1 to 250



2 Core / 2.0 GHz and above		 4 GB RAM 75 GB & above Type: m-series large (Eg: m5.large)
vCPU: 2
Memory: 8 GB
Processor: 2.4 GHZ		 Size: D-series D2 size (Eg: D2as_v4)
vCPU: 2
Memory: 8 GB
Processor: 2.4 GHZ
251 to 500 8 GB RAM 100 GB & above Type: m-series large (Eg: m5.large)
vCPU: 2
Memory: 8 GB
Processor: 2.4 GHZ		 Size: D-series D2 size (Eg: D2as_v4)
vCPU: 2
Memory: 8 GB
Processor: 2.4 GHZ
501 to 750 16 GB RAM 125 GB & above Type: m-series xlarge (Eg: m5.xlarge)
vCPU: 4
Memory: 16 GB
Processor: 2.4 GHZ		 Size: D-series D2 size (Eg: D2as_v4)
vCPU: 4
Memory: 16 GB
Processor: 2.4 GHZ
 
Enterprise Edition / Plugin Enterprise Edition
 
Note:
  • If you plan to store more historical data for monitors, make sure to allocate extra disk space. Environments with high monitoring frequency or many monitors may need additional storage to support extended data retention.
  • In AWS and Azure, 4 GB RAM is only available in burstable instance types. For a non-burstable option, we recommend using the M series in AWS and D series in Azure.
  • We strongly recommend assigning a dedicated Applications Manager-installed machine for production.
  • We do not recommend installing Applications Manager on NAS (Network-Attached Storage) as it could potentially affect the shutdown process of the PostgreSQL Database.
  • The above-mentioned memory does not include the memory used by OS, which should account for another 4 GB.
  • Solid-State Drives (SSD) are strongly recommended.
  • In Enterprise Edition setup, if number of Probe Servers are high, 16 GB RAM for the Central Server is recommended.
  • It is recommended to read the Best Practices Guide before going into production.
  • Support for Applications Manager 32-bit installations has been deprecated from March 31,2022. Existing customers refer this post for details.
  • Refer the System requirements for configuring Webpage Analyzer Monitors.

End User Monitoring System Requirements (for the machine where EUM Agent is to be deployed)

Following table shows the recommended configuration of the system to deploy EUM agent in both Professional Edition / Plugin Professional Edition and Enterprise Edition / Plugin Enterprise Edition :

On-premise Setup

Number of RBM Monitors OS Processor Memory Hard Disk
1 to 5 Windows / Linux 4 Core / 2.4 GHz and above 8 GB RAM 40 GB & above
6 to 20 Windows / Linux 8 Core / 2.4 GHz and above 16 GB RAM 75 GB & above

Cloud VM Setup

Number of RBM Monitors Processor Hard Disk AWS recommended instance type Azure recommended instance size
1 to 5 4 Core / 2.4 GHz and above 40 GB & above Type: m-series xlarge (Eg: m5.xlarge)
vCPU: 4
Memory: 16 GB
Processor: 2.4 GHZ		 Size: D-series D4 size (Eg: D4as_v3)
vCPU: 4
Memory: 16 GB
Processor: 2.4 GHZ
6 to 20 8 Core / 2.4 GHz and above 75 GB & above Type: m-series 2xlarge (Eg: m5.2xlarge)
vCPU: 8
Memory: 32 GB
Processor: 2.4 GHZ		 Size: D-series D8 size (Eg: D8as_v3)
vCPU: 8
Memory: 32 GB
Processor: 2.4 GHZ
 
Note:
  • We strongly recommend assigning a dedicated machine for the EUM Agent for production purposes.
  • A maximum of 20 EUM Agents are allowed per Applications Manager instance.
  • For configuring other EUM Monitors other than RBM monitors, the system configuration given for 1 to 5 RBM monitors will be sufficient.
  • For RBM Monitors:
    • The recommendations are based on five steps per monitor. The configuration will vary depending on the load.
    • RBM monitor with Edge playback is supported only on the Windows EUM agent.
    • The performance of the monitor is influenced by the following factors:
      • The number of steps added in the monitor
      • The polling interval of the monitor
      • The time taken for the page to load

Learn more about End User Monitoring

Learn more about Real Browser Monitoring

Real User Monitoring System Requirements

The RUM Agent must be installed on a dedicated Windows or Linux machine with a minimum of 8 GB RAM.

The RUM Agent works with both the Professional Edition and the Enterprise Edition (with Probe Server) of Applications Manager.

OS No of Monitors Processor Memory Hard Disk
Windows (Windows 11/10 or Windows Server 2025/2022/2019/2016) /
Linux ( Amazon Linux 2 & 2023 / CentOS Stream 9 / Debian 11.x to 12.13 / Fedora 39 to 41 / openSUSE 15.x / Oracle Linux 7.x to 10.x / RHEL 7.x to 10.1 / SUSE Linux Enterprise 15.x / Ubuntu 16.04 to 25.x / Rocky Linux 10 / BOSS Linux 10)		 1 - 20 2 Core / 2.0 GHz and above 8 GB RAM 40 GB
Note:
  • Each Applications Manager instance can support up to 20 RUM Agents.
  • A single RUM Agent can efficiently manage 5000 page views per minute (~200 million page views per month).

Software Requirements

User Privilege: In Windows, Administrator privileges are required for Applications Manager installation.

 
Windows OS
Evaluation Production
Windows 11/10 or Windows Server 2025/2022/2019/2016 Windows Server 2025/2022/2019/2016
 
Linux OS
Evaluation Production
Amazon Linux 2 and 2023 / CentOS Stream 9 / Debian 11.x to 12.13 / Fedora 39 to 41 / openSUSE 15.x / Oracle Linux 7.x to 10.x / RHEL 7.x to 10.1 / SUSE Linux Enterprise 15.x / Ubuntu 16.04 to 25.x / Rocky Linux 10 / BOSS Linux 10 Amazon Linux 2 and 2023 / CentOS Stream 9 / Debian 11.x to 12.13 / Fedora 39 to 41 / Oracle Linux 7.x to 10.x / RHEL 7.x to 10.1 / Ubuntu 16.04 to 25.x / Rocky Linux 10 / BOSS Linux 10
Note: Learn more about the capabilities of Windows vs Linux Downloads before downloading them.
 

Supported Database Backends

Applications Manager supports PostgreSQL and Microsoft SQL database backends for storing all the configuration information and data collected.

Note: Support for Applications Manager with MySQL database was deprecated on March 31,2017. Existing customers can refer to this post for details.

PostgreSQL

  • In Applications Manager versions 17 and higher, the default backend database is PostgreSQL v15. To enable remote PostgreSQL backend in these versions, use PostgreSQL versions 15.5 to 15.x.
  • In Applications Manager versions 16 and earlier, the default backend database is PostgreSQL v11. To enable remote PostgreSQL backend in these versions, use PostgreSQL versions 11.16 to 11.x.
Note: The PGSQL backend has been tested for Applications Manager with cloud services such as AWS RDS and Microsoft Azure PgSQL.

Microsoft SQL

Supported Version: Applications Manager supports the following Microsoft SQL database versions: 64-bit version of Microsoft SQL Servers 2025/ 2022/ 2019/ 2017/ 2016 (SQL Standard / Enterprise Edition).

Authentication: Applications Manager supports mixed mode of authentication (SQL and Windows authentication).

Ports: Default MS SQL database port used is 1433 through TCP.

Note: The MSSQL backend has been tested for Applications Manager with cloud services such as AWS RDS, Azure SQL Server, Azure SQL Managed Instance, and Google Cloud Platform SQL.

The following section lists the various requirements of an MS SQL backend database server for Applications Manager:

 
User-role requirement
  • When creating a new database:
    • Ensure that the user account is part of the dbcreator server role.
  • In the case of utilizing an existing unused database:
    • It is sufficient for the user account to be assigned to the db_owner database role within the existing database.
Note: The user account used for installation must have access to the MASTER databases. Learn more about configuring MS SQL database
 
SQL Server Collation
  • Applications Manager supports any case-insensitive collation setting.
  • Use the following collation settings for respective languages listed below:
    • English with collation setting (SQL_Latin1_General_CP1_CI_AS)
    • Norwegian with collation setting (Danish_Norwegian_CI_AS)
    • Simplified Chinese with collation setting (Chinese_PRC_CI_AS)
    • Japanese with collation setting (Japanese_CI_AS)
    • German with collation setting (German_PhoneBook_CI_AS)
 
SQL AlwaysOn Availability Groups
  • Applications Manager also supports SQL AlwaysOn Availability Groups as database backend.
  • To connect to the SQL AlwaysOn, you will need to provide the SQL availability group's DNS name and listener port (usually 1433) in the place of the database details specified during installation.
 
CPU
Number of Monitors CPU
1 to 100 monitors 2 Core / 2 GHz and above
101 to 250 monitors 2 Core / 2 GHz and above
251 to 1000 monitors 4 Core / 2 GHz and above
1001 to 10000 monitors 4 Core / 2 GHz and above
 
Memory
Number of Monitors Memory
1 to 100 monitors 4 GB and above
101 to 250 monitors 8 GB and above
251 to 1000 monitors 12 GB and above
1001 to 10000 monitors 16 GB and above
 
Hard Drive Space

Following storage requirements are specifically for the size of SQL datafiles and transaction log files. They do not include requirements for Microsoft SQL installation files, storing SQL backups, etc.

Number of Monitors Minimum Hard Drive Space
1 to 100 monitors 50 GB
101 to 250 monitors 75 GB
251 to 1000 monitors 100 GB
1001 to 10000 monitors 150 GB
Note:
  • We recommend that you create a separate account for Applications Manager in your MS SQL database server. Learn more about configuring MS SQL database backend for Applications Manager
  • It is recommended that the SQL server is connected to the same LAN as that of Applications Manager.
  • Latency between Applications Manager server and database server should be less than 10 milliseconds.
  • Solid-State Drives (SSD) are strongly recommended.
  • Use SQL Server Express only for evaluations and small environments, such as 10 monitors.
  • From Applications Manager v15000 onwards, Microsoft JDBC driver will be used to establish connection with SQL database server from Applications Manager (except Plugin) by default. However, you can choose between Microsoft JDBC and jTDS JDBC drivers for establishing connection by selecting the required driver under Settings → Server Settings → Database Configuration. For SQL server version 2008 alone, only SQL authentication can be used to establish connection through Microsoft JDBC driver.

Enterprise Edition Limitations

Only Light Load Monitors = 750 Monitors

Only Heavy Load Monitors = 400 Monitors

Medium Load Monitors = 600 Monitors (200 Heavy Load + 400 Light Load)

In Applications Manager, Maximum Load Capacity Per Probe refers to the highest number of monitors or resources that can be efficiently handled by a single probe. It varies based on the probe's configuration, hardware specifications, and the types of monitors being used. The types of monitors that fall within the Heavy Loaded and Light Loaded categories are listed in the following table.

Monitor Type Heavy Loaded Monitors Light Loaded Monitors
Application Servers
  • JBoss server
  • Microsoft .NET
  • Tomcat
  • WebLogic Cluster
  • WebLogic Server
  • WebSphere Server
  • Apache Geronimo
  • GlassFish
  • Java Runtime
  • Jetty Server
  • Oracle Application
  • Resin
  • SilverStream
  • VMware vFabric tc Server
Cloud Apps
  • Amazon Elastic Kubernetes Service
  • Azure Kubernetes Service (AKS)
  • Azure SQL Database
  • Oracle Cloud Autonomous Database
  • Note:
    The 3 services given below are considered as Heavy (Only when PowerShell mode is enabled):
    • Azure Virtual Machine
    • Exchange Online
    • SharePoint Online
  • Amazon
  • Amazon ActiveMQ
  • Amazon API Gateway (HTTP API)
  • Amazon API Gateway (REST API)
  • Amazon API Gateway (WebSocket API)
  • Amazon CloudFront
  • Amazon CloudHSM
  • Amazon Direct Connect
  • Amazon DMS Replication Instance
  • Amazon DMS Replication Task
  • Amazon Elastic Container Registry
  • Amazon Elastic File System
  • Amazon File Transfer Family
  • Amazon FSx File Cache
  • Amazon Gateway Load Balancer
  • Amazon Key Management Service
  • Amazon RabbitMQ
  • Amazon Route 53 Health Checks
  • Amazon Secrets Manager
  • Amazon Storage Gateway
  • Amazon Storage Gateway File Share
  • Amazon Storage Gateway Volume
  • NAT Gateway
  • Amazon Web Application Firewall
  • Application Load Balancer
  • DynamoDB
  • EC2 Instance
  • Elastic Beanstalk
  • Elastic Container Service
  • Elastic Kubernetes Service
  • Lambda
  • Network Load Balancer
  • RDS Instance
  • Simple Queue Service
  • Microsoft Azure
  • Azure Active Directory
  • Azure App Service Plan
  • Azure App Services
  • Azure Application Gateway
  • Azure Backup Vault
  • Azure Bastion
  • Azure Cache for Redis
  • Azure Connection
  • Azure Container App
  • Azure Container Instance
  • Azure Container Registry
  • Azure Cosmos DB
  • Azure Database for MariaDB Server
  • Azure Database for MySQL Server
  • Azure Database for PostgreSQL Server
  • Azure DNS Zone
  • Azure Event Hub Cluster
  • Azure Event Hub Namespace
  • Azure ExpressRoute Circuit
  • Azure Firewall
  • Azure Front Door and CDN Profile
  • Azure Functions
  • Azure Key Vault
  • Azure Key Vault Managed HSM
  • Azure Load Balancer
  • Azure Logic App (Consumption)
  • Azure Logic App (Standard)
  • Azure Network Interface
  • Azure Network Watcher Connection
  • Azure Premium Storage Account
  • Azure Private DNS Zone
  • Azure Private Endpoint
  • Azure Private Link Service
  • Azure Public IP Address
  • Azure Recovery Service Vault
  • Azure Relay
  • Azure Service Bus
  • Azure SQL Managed Instance
  • Azure Storage Accounts
  • Azure Storage Sync Service
  • Azure Synapse Analytics
  • Azure Traffic Manager Profile
  • Azure Virtual Machine Scale Sets
  • Azure Virtual Network
  • Azure Virtual Network Gateway
  • Oracle Cloud
  • Oracle Cloud Instance
  • Oracle Cloud Load Balancer
  • Oracle Cloud Storage
  • Google Cloud Platform
  • Compute Engine
  • Google Cloud Filestore
  • Google Cloud Storage
  • Google Kubernetes Engine
  • Microsoft 365
  • Microsoft Teams
  • OpenStack
Converged Infrastructure
  • Cisco UCS
  • Nutanix
  • KVM
  • Microsoft Hyper-V Server
  • VMWare Horizon View
  • VMware ESX/ESXi, vCenter
  • VMware Horizon View Connection Broker
  • Microsoft Windows Cluster
  • Linux
  • AIX
  • Windows
  • Sun Solaris
  • Mac
  • IBM I
  • FreeBSD/OpenBSD
  • Ceph Storage
  • SNMP/Network Device
  • Windows Performance Counter
  • xenServer
  • RHEV
  • Oracle VM
  • FTP/SFTP
Custom Monitors
  • Note: Below are custom monitors, load depends on the user configuration so categorizing under Medium load.
    • File / Directory Monitor
    • Script Monitor/Custom monitor type
    • SAP CCMS
    • Database Query monitor.
 ---
Database Servers
  • Oracle
  • MSSQL
  • MySQL
  • PostgreSQL
  • Sybase ASE
  • Oracle PDB
  • MySQL
  • Oracle RAC
  • DB2 for i
  • DB 2
  • Informix
  • SAP SQL Anywhere
  • Sybase Replication
  • Dameng DB
  • Cassandra
  • Couchbase
  • Hbase
  • Hadoop
  • Hazelcast
  • Memcached
  • MongoDB
  • Neo4j
  • Oracle coherence
  • Oracle Nosql
  • Redis
ERP
  • Oracle EBS
  • Microsoft Dynamics AX
  • Microsoft Dynamics CRM / 365 (On-Premise)
Mail Servers
  • Exchange Server
 ---
Middleware / Portal
  • IBM Websphere MQ
  • IBM Websphere Message Broker
  • Microsoft BizTalk
  • MS Office SharePoint
  • WebLogic Integration
  • Apache ActiveMQ
  • Apache Kafka
  • Oracle Tuxedo
  • Rabbit MQ
  • Microsoft MQ (MSMQ)
  • Microsoft Skype For Business
SAP Apps
  • SAP HANA
  • SAP MaxDB
  • SAP Server
  • Siebel Enterprise Server
  • SAP Business One
  • SAP Java
Services
  • Istio
  • Apache ZooKeeper
  • Active Directory
  • Network Policy Server (Radius Server)
  • JMX Applications
Virtualization
  • Citrix Virtual Apps and Desktop
  • Kubernetes
  • OpenShift
  • Docker
  • Docker Container
  • XenApp
Web Server / Web Services
  • Apache Solr
  • Apache Spark
  • Elasticsearch
  • HAProxy
  • HTTP(s) URL Sequence
  • Nginx Plus
  • Real Browser Monitoring (RBM)
  • Real User Monitoring (RUM)
  • REST API Sequence
  • Webpage Analyzer
  • Website Content
  • Apache Server
  • IBM HTTP Server
  • Oracle HTTP Server
  • Brand Reputation
  • DNS Monitor
  • HTTP(s) URL
  • LDAP Server
  • Mail Server
  • Nginx
  • Ping Monitor
  • PHP
  • REST API
  • Service Monitor
  • SSL/TLS Certificate Monitor
  • Telnet Monitor
  • UDP Port Monitor
  • Web Server
  • Web Services
 
Note:
  • The maximum number of monitors an Central server can handle is up to 10000 monitors (200 Probes / Central).
  • The limit might vary based on the amount of data being collected in the Probe Server, and the Network Latency between the Central and the Probe Servers.

Thank you for your feedback!

Was this content helpful?

We are sorry. Help us improve this page.

How can we improve this page?
Do you need assistance with this topic?
By clicking "Submit", you agree to processing of personal data according to the Privacy Policy.