Server Settings

AMServer Properties file

By editing AMServer Properties file & AvailabilityTests.conf file (available under <Applications Manager Home>/conf/ directory), you can change the default server settings used in ManageEngine Applications Manager.

Key Description
am.webserver.port This is the web server port used by Applications Manager to connect to the browser.
am.ssl.port Keys to enable SSL (https) and this will be enabled by default
am.dbserver.type Backend database type. Possible values : pgsql, mysql, mssql. If key not present, it will use mysql backend
am.db.port / am.mysql.port Port used by the database. am.mysql.port was used before 11
am.tomcat.shutdown.port Tomcat ports for Applications Manager. If any of these ports is occupied when Applications Manager starts, it will be changed automatically. In builds before 11, am.tomcat.shutdown.port will not change automatically even if it is occupied and it has to be changed manually
am.traplistener.port Port in which Applications Manager will listen and receive traps from other device
am.createSupportZipFile Key for zipping of support file. Not used by Applications Manager. Only used by IT360
am.dbport.check While starting up, Applications Manager will check if the DB port mentioned in am.db.port / am.mysql.port is already occupied. If the ports are occupied, it will automatically change am.db.port / am.mysql.port to next unoccupied port and start DB server in that port. This will be done for mysql and pgsql backend. By default these key(s) are true. If customer is using his own pgsql / mysql, these key(s) needs to be set to false. am.mysqlport.check was used before 11
am.webserverport.check While starting up, Applications Manager will check if the web server port mentioned in am.webserver.port is already occupied. If the ports are occupied, it will alert user and shutdown Applications Manager.
am.sockettest.timeout Socket test timeout value in seconds used by various monitors like MySQL, MsSQL, DB2, JBoss, Oracle, Service monitor etc. This value can be also changed from Admin > Availability Settings > Availability Check: Timeout value
am.server.language These keys determine the language of Applications Manager. Default values are am.server.language=en and Possible values are : English ( en / US ), Chinese ( zh / CN ), German ( de / DE ), Spanish ( es / ES ), French ( fr / FR ), Hungarian ( hu / HU ), Japanese ( ja / jp ), Korean ( ko / KR ), Taiwanese ( zh / TW ), Vietnamese ( vi / VN )
am.server.type Key to see if its Professional edition / Enterprise Edition. Possible values are : NORM, AAM, MAS
am.edition.type For Enterprise Edition managed server this will have the host name of admin server
am.adminserver.port For Enterprise Edition managed server this will have the SSL port of admin server
am.server.startresidrange The resourceid range for this Applications Manager. For Enterprise Edition this will be in range according to serverid.
am.ntlm.hostname Fully qualified Hostname of Applications Manager is required for monitoring URLs with windows NTLM authentication. If this field does not have FQHN, we need to update it manually for proper URL NTLM monitoring
am.ntlm.hostdomainname This has the domain name of Applications Manager server which is required for monitoring URLs with windows NTLM authentication.
am.adminpollstry.count For Enterprise Edition, admin server will report that managed server is down according to polls to try set in this key. By default value is 1.
am.appmanager.hostname Hostname of Applications Manager which is used in alert mail, alarm escalation mail, report mails sent by Applications Manager.
am.external.hostname If Applications Manager is in DMZ or behind firewall and has an Internal and External Hostname/IP, we can set External hostname / Ip here so that when users access JRE Thread dumps, MySQL and Ingres Process list.
am.log.dir Key for changing location of logs directory. Not used by Applications Manager. Only used by IT360
am.wmi.encoding Encoding to be used for parsing vbscripts output in WMI mode
  • Under Admin Tab, click on Server Settings under Product Settings.
  • Here is a list of keys that can be configured from the UI:

General Settings

Option Description
Enable SSL * This key enables SSL (HTTPS) and will be enabled by default.
Enable Subgroups view If Enabled, displays subgroups in Alarms, Reports and New Monitor page's Monitor Group.
Enable Subgroups in SLA view Lists sub groups in SLA page, if enabled along with 'Enable subgroups view'.
Send mail if datacollection stopped Admin receives email,if data collection for monitor(s) doesn't occur for more than an hour or if there are out Of memory errors or if data collection stops for 50% of monitors.
Send Monitor Error Mail Sends a mail if data collection stopped for any monitor.
Disable datacleanup in business hours Enabling this key ,ensures that data cleanup doesn't happen between 8:00 am to 6:00 pm.
Open browser on Startup * If enabled, the browser automatically opens when Applications Manager starts.
Enable file Upload Enables file uploads option in Admin tab -> Upload Files/Binaries
Delete Synced SQL files in Admin Server * Disabling this will ensure .sql files(sent from managed server to Admin server for syncing data) are not deleted in admin server, after syncing data.
Maximum Subgroup level Number of levels of subgroups that can be created in a monitor group.
Error poll count If any monitor error continuously occurs poll count times then error mail will be sent to admin id.
Raw data cleanuptime (hours) * Time period (in hours) of raw data stored in database for all non-conf monitor's attributes can be changed by using this key. Maximum time period allowed to retain the raw data is 24 hours.
Conf data cleanup interval (days) Conf data cleanup interval - To change the clean interval of data stored in conf monitors, this key value is changed.
Week Start Day of MG outage comparison Report For Monitor group outage comparison week report, the week starts from Sunday.
OutOfMemoryException duration (mins) If 20 (am.oomexception.count) out of memory error occurs in less than 30 minutes (am.oomexception.duration), Applications Manager restarts
OutOfMemoryException count No of retries out of Memory errors occurred. Default set to 20.
Maximum threads for scheduler * Max threads allowed for Scheduler Task.
Maximum polling load factor to add monitor * Represents Managed server maximum polling load factor to add monitor
Maximum database load factor to add monitor * Represents Managed server maximum database load factor to add monitor
Generate heap dump for free JVM memory (MB) If free JVM memory is less than 20 MB, a heap dump for Applications Manager is generated.
Debug-Info directory size limit (bytes) Debug-Info directory size limit(bytes) - Old files in AppManagerworkingDebug-Info directory are cleared, once it reaches 80% of this key value.
Command size in Execute program action Changing the key value will increase the size limit of 400 characters, for commands in execute program.
Managed server maximum monitor count * Maximum no.of monitors allowed per Managed server.
Probe Key Regeneration interval (days) * Time interval set to regenerate the Probe Registration Key in the Admin server (in days). Value entered should be greater than 0.
Enable weekly stray entries cleanup If enabled, it cleans up stray entries on Saturdays whenever Applications Manager is restarted. After the first cleanup is done, subsequent cleanups will take place on first Saturday of every month.

Availability Settings

Option Description
Enable NativePing Enables Native Ping to determine server monitor availability.
Enable PortTest Enables port test for Server monitoring.
Ports to test Ports mentioned here will be used for port test.
PortTest timeout in seconds Timeout value for checking the ports.
Ping retries Number of retries to execute the ping command in case of failure to check the availability of server.
Application Server timeout Tomcat, Apache, PHP, WebSphere monitor's connection time out value in minutes.

Threads Configuration

Option Description
Main * This thread is used for JMX/SNMP Dashboard,Schedule Reports
URLMonitor Thread * Monitors like HTTP(s) URLs,HTTP(s)-URL Sequence,SAP-CCMS uses this thread for data collection.
KeyValueMonitor Thread* Monitors like Active Directory Amazon,Cassandra,Ceph Storage,DNS Monitor,Database Query Monitor,Exchange Server,Script Monitor etc. uses this thread for data collection.
RBMMonitor Thread * Real Browser Monitoring uses this thread for data collection.
MQSeriesMonitor Thread * IBM Websphere MQ monitor uses this thread for data collection
DataCollection Thread * This thread is used for datacollection of monitors like AIX,AS400/iSeries,Apache Server,DB2,FreeBSD / OpenBSD,HP-UX / Tru64 UNIX,IIS Server etc.
CustomMonitor Thread  * This thread used for dataCollection of Custom Attributes for monitors like RMI,WEBLOGIC-server,JBOSS-server,WebSphere-server,JMX1.2-MX4J-RMI.
WebServiceMonitor Thread * This thread is used for WebServices.
QueryMonitor Thread * This thread is used for Query Monitors.

Database Params Configuration

Option Description
No. of Database Connections * This key is used to configure the no.of non transaction connections to be established with the database.

JVM Params Configuration

Option Description
Maximum Java Heap Size (MB) * Maximum memory allocated for Applications Manager.
Maximum Permgen Size (MB) * Maximum Permgen size allocated for Applications Manager.

- Indicates changes will take effect only after restart of APM.

* - Enterprise Edition

List of Keys that were moved to DB

Key Option to Configure in GUI Admin > Performance Data Collection > servers
am.nosql.rediscover.interval Admin >Performance Data Collection > Database Servers
am.pingtest.command Admin >Performance Data Collection > Ping Monitor
am.repoll.interval Admin >Performance Data Collection > HTTP(s) URLs Admin >Performance Data Collection > Optimize Data Collection >JMX Application
am.dirsize.unit Admin >Performance Data Collection > Optimize Data Collection >File/Directory Monitor
am.ftp.filesize Admin >Performance Data Collection > Optimize Data Collection >FTP/SFTP Monitor
am.htmldata.jre.daystoretain Admin >Performance Data Collection > Optimize Data Collection >JavaRuntime Monitor
am.mqseries.ccsid Admin >Performance Data Collection > Optimize Data Collection >WebSphere Server
am.script.deleterow Admin >Performance Data Collection > Optimize Data Collection >Script Monitor
am.querymonitor.rowcount Admin >Performance Data Collection > Optimize Data Collection >Database Query Monitor
am.vsphere.connection.timeout Admin >Performance Data Collection > Optimize Data Collection >VMware ESX/ESXi Monitor
am.xen.resourcepool.discovery.enable Admin >Performance Data Collection > Optimize Data Collection >Xen Server
am.ssl.enabled Admin >Server Setting > General Settings
am.senddcstoppedmail.enabled - (MAS & Prof)-hidden
am.server.deleteMonitor.comparing.csvToCmdb - hidden
am.server.defaultDiscovery.enabled - hidden
am.userresource.onLogin.update - Hidden
am.querytracker.enable - Hidden
am.simple.theme.enabled - Hidden
am.startmonthread.enabled - Hidden
am.monitorGroup.rules.enable - remove
am.expandWidgets - need to check..
am.spacecheck.warning - remove key and related code
am.dbconnection.refresh - Hidden
am.push.userconfig.details - remove
am.useresource.operations.concurrent.update - Hidden
am.rawdata.value - move to servers tab
am.userResUpdateThread.schedule.interval - Hidden
am.server.maximum.thread.schedulerTask - restart
am.enablenativeping Admin >Server Setting > Availability Settings
Note: Log clean-up in Applications Manager is an automatic process and logs are cleared without any changes in settings. To make changes in clean-up intervals refer to the table above.