System Requirements

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

• Hardware Requirements
• Cloud VM Hardware Requirements
• End User Monitoring System Requirements
• Software Requirements
• Supported Database Backends
• Enterprise Edition Limitations
• Windows vs Linux versions of 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.

* The above mentioned memory does not include memory used by OS which should account for another 4 GB.
* If number of Managed Servers are high, 16 GB RAM for the Admin Server is recommended.

Cloud VM Hardware Requirements

The following table describes the recommended configuration of the system to deploy Applications Manager on AWS or Azure.

* The above mentioned memory does not include memory used by OS which should account for another 4 GB.
* If number of Managed Servers are high, 16 GB RAM for the Admin Server is recommended.

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

EUM Agents for Firefox based RBM monitors have to be installed on a dedicated Windows / Linux machine - 8 GB RAM, 40 GB HD. EUM Agents for Microsoft Edge based RBM monitors have to be installed on a dedicated Windows - 8 GB RAM, 40 GB HD. EUM Agents for Chrome based RBM monitors have to be installed on a dedicated Windows / Linux machine - 8 GB RAM, 40 GB HD. However, Applications Manager can be installed on Windows or Linux. This works with the Professional Edition and Enterprise Edition (with Managed Server).

Best Practices:

• It is suggested to have a processor with 4 cores.
• A single EUM Agent can handle up to 15 to 20 RBM monitors simultaneously (varies based on the load)

Know more about End User Monitoring

Know more about Real Browser Monitoring

Software Requirements

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

Supported Database Backends

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

PostgreSQL

PostgreSQL comes bundled with your download of Applications Manager from Build 11000. We support PostgreSQL versions up to 10.21 (for 32-bit installation) and 11.16 (for 64-bit installation) for the backend. For Applications Manager with PostgreSQL database backend, there will be two more additional users (dbuser and rouser) created along with the existing PostgreSQL user.

For normal installations, user account of 'dbuser' will be used in the database_params.conf file instead of 'postgres' user. However, for service pack installations, 'postgres' user will be used by default and other two users will be created on very first startup of Applications Manager after service pack upgrade.

MS SQL

The supported Microsoft SQL database versions that you may use are: 64-bit version of Microsoft SQL Servers 2022/ 2019/ 2017/ 2016/ 2014 (SQL Standard / Enterprise Edition). It is also recommended that the SQL server and Applications Manager are in the same LAN.

SQL Server Collation : Any case-insensitive collation. For Chinese Installation use Chinese_PRC_CI_AS, Japanese Installation use collation setting (Japanese_CI_AS)

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.

Prerequisites for using SQL AlwaysOn Availability Groups as database backend:

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.

Note: For proper functionality, we recommend that you create a separate account for Applications Manager in your MS SQL database server. Learn more

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)