|
ManageEngine® Applications Manager Server Settings | ||
By editing AMServer Properties file & AvailabilityTests.conf file (AppManager Home/Conf/), you can change the default server settings used in ManageEngine Applications Manager.
| AMServer Properties file | |
| 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.webcontainer.port | |
| am.rmiregistry.port | |
| am.shutdown.port | |
| 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 am.server.country=US. 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.country | |
| am.server.type | Key to see if its Professional edition / Enterprise Edition. Possible values are : NORM, AAM, MAS |
| am.edition.type | |
| am.adminserver.host | 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.failover.preferredstandby | |
| 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.scheduleReports.enableSSL | |
| am.user.resource.enabled | |
| am.sso.enabled | |
| 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 | |
| Enable SSL* | Enable SSL - This key enables SSL(https) and will be enabled by default. |
| Enable Subgroups view | Enable Subgroups view - If Enabled, displays subgroups in Alarms, Reports and New Monitor page's Monitor Group. |
| Enable Subgroups in SLA view | Enable Subgroups in SLA view - Lists sub groups in SLA page, if enabled along with 'Enable subgroups view'. |
| Send mail if datacollection stopped | 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 | Send Monitor Error Mail - Sends a mail if data collection stopped for any monitor. |
| Disable datacleanup in business hours | 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* | Open browser on Startup - If enabled, the browser automatically opens when Applications Manager starts. |
| Enable file Upload | Enable file Upload - Enables file uploads option in Admin tab -> Upload Files/Binaries |
| Delete Synced SQL files in Admin Server * | 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 | Maximum Subgroup level - Number of levels of subgroups that can be created in a monitor group. |
| Error poll count | 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)* | Raw data cleanuptime - Time period (in hours) of raw data stored in database for all non-conf monitor's attributes can be changed by using this key. |
| 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 | Week Start Day of MG outage comparison Report- For Monitor group outage comparison week report, the week starts from Sunday. |
| OutOfMemoryException duration (mins) | OutOfMemoryException duration - If 20 (am.oomexception.count) out of memory error occurs in less than 30 minutes (am.oomexception.duration), Applications Manager restarts |
| OutOfMemoryException count | OutOfMemoryException count - No of retries out of Memory errors occurred. Default set to 20. |
| Maximum threads for scheduler * | Maximum threads for scheduler - Max threads allowed for Scheduler Task. |
| Maximum polling load factor to add monitor * | 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) | 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 | 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. |
| Availability Settings | |
| Enable NativePing | Enable NativePing - Enables Native Ping to determine server monitor availability. |
| Enable PortTest | Enable PortTest - Enables port test for Server monitoring. |
| Ports to test | Ports to test - Ports mentioned here will be used for port test. |
| PortTest timeout in seconds | PortTest timeout in seconds - Timeout value for checking the ports. |
| Ping retries | Ping retries - No.of retries to execute the ping command in case of failure to check the availability of server. |
| Application Server timeout | Application Server timeout - Tomcat, Apache, PHP, WebSphere monitor's connection time out value in minutes. |
| Threads Configuration | |
| Main * | Main Thread - This thread is used for JMX/SNMP Dashboard,Schedule Reports |
| URLMonitor * | URLMonitor Thread - Monitors like HTTP(s) URLs,HTTP(s)-URL Sequence,SAP-CCMS uses this thread for data collection. |
| KeyValue_Monitor * | 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. |
| RBM_Monitor * | RBMMonitor Thread - Real Browser Monitoring uses this thread for data collection. |
| MQSeries * | MQSeriesMonitor Thread - IBM Websphere MQ monitor uses this thread for data collection |
| DataCollection * | 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 * | 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 * | WebServiceMonitor Thread - This thread is used for WebServices. |
| QueryMonitor Thread * | QueryMonitor Thread - This thread is used for Query Monitors. |
| DataBase Params Configuration | |
| 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 spacer | |
| 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
Data Backup |
Production Environment |