ManageEngine has been recognized as a Customers' Choice in the 2023 Gartner Peer Insights™ Voice of the Customer for Application Performance Monitoring and Observability report. Learn more

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 MonitorsProcessorMemoryHard Disk
1 to 100 2 Core / 2.0 GHz and above 4 GB RAM 50 GB & above
101 to 250 8 GB RAM 75 GB & above
251 to 500 2 Core / 2.0 GHz and above 12 GB RAM 100 GB & above

Cloud VM Setup

Number of MonitorsProcessorMemoryHard DiskAWS recommended instance typeAzure recommended instance size
1 to 250 2 Core / 2.0 GHz and above 8 GB RAM 75 GB & above Type: m4.large
vCPU: 2
Memory: 8 GB
Processor: 2.4 GHZ
Size: D2s_v3
vCPU: 2
Memory: 8 GB
Processor: 2.4 GHZ
251 to 500 2 Core / 2.0 GHz and above 12 GB RAM 100 GB & above Type: m4.xlarge
vCPU: 4
Memory: 16 GB
Processor: 2.4 GHZ
Size: D4s_v3
vCPU: 4
Memory: 16 GB
Processor: 2.4 GHZ
 
Enterprise Edition / Plugin Enterprise Edition
 
Note:
  • We strongly recommend assigning a dedicated Applications Manager-installed machine for production.
  • 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 Managed Servers are high, 16 GB RAM for the Admin 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.

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 :

OSProcessorMemoryHard Disk
Windows / Linux 2 Core / 2.0 GHz and above 8 GB RAM 40 GB

 

 
Note:
  • We strongly recommend assigning a dedicated Applications Manager-installed machine for production.
  • The above-mentioned memory does not include the memory used by OS, which should account for another 4 GB.
  • A maximum of 20 EUM Agents are only allowed per Applications Manager instance.
  • A single EUM Agent can handle up to 15 to 20 RBM monitors simultaneously (varies based on the load).
  • RBM monitor with Edge playback is supported only in Windows EUM agent.

Know more about End User Monitoring

Know more about Real Browser Monitoring

Real User Monitoring System Requirements

RUM Agent have to be installed on a dedicated Windows / Linux machine - 8 GB RAM. RUM Agent can work with the Professional Edition and Enterprise Edition (with Managed Server) of Applications Manager.

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

OSNo of MonitorsProcessorMemoryHard Disk
Windows (Windows 11/ 10 (or) Windows Server 2022/ 2019/ 2016/ 2012 R2) /
Linux (Cent OS 7/ CentOS Stream 8 and above/ Debian/ Fedora/ openSUSE/ Oracle Linux/ RHEL 7, 8 and 9/ SUSE Linux Enterprise/ Ubuntu 14 to 22)
1 - 20 2 Core / 2.0 GHz and above 8 GB RAM 40 GB
 
Given below are the good to have practices for RUM:
  • Each Applications Manager instance can support upto 20 RUM Agents.
  • On an average, a single RUM Agent can efficiently manage 5000 page views per minute i.e. 200 million page views per month. This performance may vary based on the hardware specifications of the hosting server.

Software Requirements

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

 
Windows OS
EvaluationProduction
Windows 11/ 10 (or) Windows Server 2022/ 2019/ 2016/ 2012 R2 Windows Server 2022/ 2019/ 2016/ 2012 R2
 
Linux OS
EvaluationProduction
Amazon Linux 2/ Cent OS 7/ CentOS Stream 8 and 9/ Debian 10.x to 11.6/ Fedora 38/ openSUSE 15.x/ Oracle Linux 7.x/ RHEL 7 to 9.1/ SUSE Linux Enterprise 15.x/ Ubuntu 14.04 to 22.04 Amazon Linux 2/ CentOS Stream 8 and 9/ Debian 10.x to 11.6/ Fedora 38/  Oracle Linux 7.x/ RHEL 7 to 9.1/ Ubuntu 14.04 to 22.04
 
Browsers
EvaluationProduction
Chrome/ Firefox/ Edge
For all browsers, enable JavaScript, cookies, working with iframes and third-party cookies
Chrome (preferred)/ Firefox/ Edge
For all browsers, enable JavaScript, cookies, working with iframes and third-party cookies
Note: Do take a look at the Windows vs Linux Downloads page to compare the capabilities of Windows and Linux variations before downloading the product.
 

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

  • By default, when you download Applications Manager, PostgreSQL v11.x is bundled as its backend database.
  • For Remote PostgreSQL, Applications Manager supports PostgreSQL v11.16 to v11.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 2022/ 2019/ 2017/ 2016/ 2014 (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 MonitorsCPU
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 MonitorsMemory
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 MonitorsMinimum 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

Maximum Load Capacity Per Probe:

Light Load Category: Application Servers, Cloud Apps, Web Servers, Mail Servers, Services, Custom Monitors
Heavy Load Category: Servers, ERP, Database Servers, Virtualization, Converged Infrastructure, Middleware / Messaging

Only Light Load Monitors = 300 Monitors
Only Heavy Load Monitors = 200 Monitors
Medium Load Monitors = 250 Monitors (100 Heavy Load + 150 Light Load)

Note:
  • The maximum number of monitors an Admin server can handle is up to 10000 monitors (200 Probes / Admin).
  • The limit might vary based on the amount of data being collected in the Managed Server, and the Network Latency between the Admin and the Managed Servers.