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.
| Edition | Number of Monitors | Processor | Memory* | Hard Disk |
|---|---|---|---|---|
| Professional Edition/Plugin Professional Edition | 1 to 100 | 2 Core / 2.0 GHz and above | 4 GB RAM | 100 GB & above |
| 101 to 250 | 2 Core / 2.0 GHz and above | 8 GB RAM | 150 GB & above | |
| 251 to 500 | 4 Core / 2.0 GHz and above | 12 GB RAM | 200 GB & above | |
| Enterprise Edition/ Plugin Enterprise Edition | 250 to 1000 1 Admin & 2-3 Managed servers |
4 Core / 2.0 GHz and above | 12 GB RAM | 200 GB & above per instance |
| 1001 to 10000 1 Admin & 2-20 Managed servers |
4 Core / 2.0 GHz and above | 16 GB RAM | 200 GB & above per instance |
* If the number of Managed Servers are high, 16 GB RAM for the Admin Server is recommended.
* The above mentioned memory does not include memory used by OS which should account for another 4 GB.
Note : Do take a look at the Best Practices Guide.
| Software | Evaluation | Production |
|---|---|---|
| Windows OS | Windows 11/ 10 (or) Windows Server 2022/ 2019/ 2016/ 2012 R2 | Windows Server 2022/ 2019/ 2016/ 2012 R2 |
| Linux OS | Cent OS 7/ CentOS Stream 8 and above/ Debian/ Fedora/ openSUSE/ Oracle Linux/ RHEL 7 and 8/ SUSE Linux Enterprise/ Ubuntu 14 to 20.04 | CentOS Stream 8 and above/ Debian/ Fedora/ openSUSE/ Oracle Linux/ RHEL 7 and 8/ SUSE Linux Enterprise/ Ubuntu 14 to 20.04 |
| Browsers | 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 |
User Privilege: In Windows, Administrator privileges required for Applications Manager installation.
Applications Manager supports PostgreSQL and Microsoft SQL database backends for storing all the configuration information and data collected.
PostgreSQL comes bundled with your download of Applications Manager from Build 11000. We support PostgreSQL versions up to 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.
| User Name | Description | Required Privileges |
|---|---|---|
| dbuser | Used in case users do not want to use the SUPERUSER privilege for the Applications Manager database. |
|
| rouser | Used to query the database from Applications Manager QueryTool option, in order to avoid users to execute UPDATE, DELETE, INSERT and ALTER type of queries. |
|
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.
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
It allows us to track crucial metrics such as response times, resource utilization, error rates, and transaction performance. The real-time monitoring alerts promptly notify us of any issues or anomalies, enabling us to take immediate action.
Reviewer Role: Research and Development
Tech Support Manager, Lexmark