ManageEngine® Applications Manager


Chapter 11.3 Enterprise Edition - Failover Support

<< Prev

Home

Next >>

 

Enterprise Edition - Failover Support

 

There are two methods of implementing failover support in ManageEngine Applications Manager:

  1. Primary server - Secondary server architecture

  2. Replication

Primary Server - Secondary Server Architecture

This setup involves a primary Applications Manager, a secondary Applications Manager and a common database. The primary and secondary Applications Manager refer to the common database only. While the primary Applications Manager talks with the database, the secondary Applications Manager simply listens to the database. If the primary server goes down, the secondary server takes over. Afterwards, the initial primary server is restarted and it starts functioning as a secondary server.


Failover Setup Details

Let us assume we are going to set up three nodes - node1, node2 and node3.

Applications Manager: node1, node2

MySQL Database: node3


Configuring the MySQL Server in node 3:

This will start the MySQL Database Server.

By default, this MySQL is configured in such a way that it accepts connections for the machine in which the Applications Manager is installed. Hence, you need to add entries for the hosts node1 and node2 to access this database.

Please refer the below link for configuring permissions.

http://manageengine.com/products/applications_manager/troubleshoot.html#m20

For stopping the MySQL database, you can use the stopMySQL.bat.
[Open this file and change the line "set MYSQL_HOME=..\mysql" to "set MYSQL_HOME=.\mysql"]

Installing Applications Manager in node1 and node 2

After installing Applications Manager in node1 and node2, do the following configurations

Top


For Windows:

By default AppManager9 - C:\Program Files\ManageEngine\AppManager9\

For Linux:

 

By default AppManager9 - /opt/ManageEngine/AppManager9

Sample Files:

 

AMServer.properties

am.mysql.port=3306

am.mysqlport.check=false


database_params.conf
url jdbc:mysql://appmanager:3306/APPMANAGERDB AppModules TopoDB-MapDB-EventDB-AlertDB-PollDB-PolicyDB-USERSTORAGEDB-ApplnDB

username admin AppModules TopoDB-MapDB-EventDB-AlertDB-PollDB-PolicyDB-USERSTORAGEDB-ApplnDB

# password appmanager AppModules TopoDB-MapDB-EventDB-AlertDB-PollDB-PolicyDB-USERSTORAGEDB-ApplnDB

 

Note: If your MySQL does not require a password to connect, the password line in <database_params.conf > should be commented as shown in the above example using the #. Otherwise instead of commenting the password line in the <database_params.conf> file, just replace the string appmanager with the password of the your mysql.

 

startMySQL.bat ( for windows )

rem mysqld-nt --defaults-file=%MYSQL_HOME%\my.ini -u root -b .. --standalone --
port=13326


stopMySQL.bat ( for windows )

rem mysqladmin -pappmanager -u root --port=13326 shutdown

startApplicationsManager.sh ( for Linux )

# if [ $? != 51 ]; then

# . $NMS_HOME/bin/stopMySQL.sh

# fi

Top

Starting the Failover Setup

Managed Server Failover Setup

 

The general setup of Admin Server will work in the above flow. With regards to Managed Server, you need to configure the multiple managed servers as against the single Admin Server.

Steps

Replication

For setting up failover support using replication, please refer this link.

Top

<< Prev

Home

Next >>

Enterprise Edition - Managed Server

Anomaly Profile