Installation Guide


Installation Demo

Editions of Applications Manager

Meet your specific monitoring and business objectives by choosing the right edition of ManageEngine Applications Manager. Applications Manager is available in these editions:

  • Free Edition
  • Professional Edition (Trial/Registered)
  • Enterprise Edition (Trial/Registered)

Free Edition

The Free Edition allows you Five monitors (excluding the Monitors added by default). The Free Edition never expires and you get most of the functionality of Professional Edition. Compare the Free and the Professional Edition.

Professional / Enterprise

You can avail 30 days of evaluation with no restrictions on the number of monitors. The Professional Edition allows you to monitor up to 250 monitors. The Enterprise Edition allows you to monitor more number of servers and applications in a distributed setup. You can configure independent Applications Manager installations to monitor resources and then collectively view the data of all the independent Applications Manager installations ("Managed Server") from a single central installation ("Admin Server").After your 30-day free trial ends, your installation will automatically convert to the free edition unless you apply a commercial license.

This is the registered version of the product. ManageEngine provides the Registered user file after you purchase the product. To get the registered user file, e-mail to sales@manageengine.com.

To know the comprehensive differences between Free, Professional and Enterprise Edition features, visit our website - Feature Comparision.

Note: You can upgrade the Professional Edition / Enterprise Edition , Trial and Free Edition to Professional / Enterprise Edition. This is applicable, if you have purchased ManageEngine Applications Manager and hold the registered license key. To upgrade your license, refer Licensing Applications Manager

Installing Applications Manager in Windows (.exe)

Download and execute theManageEngine_ApplicationsManager.exe file. The Installation Wizard is displayed and will guide you through the setup process.

  1. Click Next at the Welcome Screen to proceed.
  2. Read the license agreement and click Yes if you accept the terms.
  3. Select the language in which you wish to install Applications Manager.
  4. The next screen prompts you to select the product edition (Free Edition, Professional Edition, Enterprise Edition):
    • If you select Enterprise Edition, specify if you want to install Applications Manager as an Admin Server or a Managed Server. If you wish to install Applications Manager as a Managed Server, enter the associated admin server Host name and SSL port number. If a proxy server is needed to contact the admin server from the Managed Server machine, enter the Host name, Port number, username and password of the proxy server.
    • If you have choosen to install the Free or Professional Edition, continue to step 7.
  5. Provide the location where Applications Manager should be installed on your machine. Also, specify the name of the new Applications Manager Folder in the installation location. Click Next.
  6. Specify the Webserver port (9090 by default) and the SSL Port (8443, by default).
  7. You can enter your details to Register for Technical Support. Click Next.
  8. If you have chosen to install the Professional Edition of Applications Manager, you can opt for either the 30 day Trial Edition or the Registered version. If you select Registered User, the next screen will prompt you to select the registered license file from your system.
  9. Select the Database back-end support:
    • PostgreSQL - PostgreSQL comes bundled with your download of Applications Manager from Build 11000. We support PostgreSQL versions up to 10.12 (for 32-bit installation) and 11.7 (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.
      • CREATE DB
      • LOGIN
      • REPLICATION
      • NO ROLE CREATION
      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.
      • LOGIN/CONNECT
      • SELECT PRIVILEGES

      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.

    • Microsoft SQL Server (version 2005, 2008, 2012, 2017) - If you select Microsoft SQL Server, you need to select if it is based on SQL Authentication or Windows Authentication. If it is based on SQL Authentication, enter the Host Name, Port Number, Database Name, User Name, Password of the SQL Server. If it is based on Windows Authentication, enter the Host Name, Port Number, Database Name of the SQL Server and the User Name , Password of the machine in which SQL Server is running. Also provide minimum privileges required - The user account should be the DB_Owner of the created database.

      From build 15000 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.

    • Note:
      • Access to the master database is required for the backend database.
      • Password field should not contain the special character [ \ ] for MS SQL backend database.

Prerequisites for using SQL AlwaysOn Availability Groups as Database back-end support :

Applications Manager supports SQL AlwaysOn availability groups as database backend. To connect to the SQL Always On, you will need to provide the SQL availability group 's DNS name & listener port (usually 1433 ) in the place of the database details during installation.

Setup completes the installation of Applications Manager.

Note
To install Applications Manager as service in a system, you must have administrative privileges in that system. More Information on 'Manually Installing Applications Manager as Service'.

Installing Applications Manager in Linux (.bin)

  1. Download the product for Linux.
  2. Execute the downloaded file. The Installation Wizard is displayed. Click Next to continue. Read the license agreement and click Next.
  3. The next screen prompts for the product edition (Free Edition, Professional Edition, Enterprise Edition). Select the preferred edition to install.
    • If Professional Edition is selected, follow the below given steps from 4 to 9.
    • If you had selected Free License, follow the steps from 4 to 9.
    • If you had selected Enterprise Edition, choose if you want install applications manager as Admin server or Managed server.
      • If you had selected Enterprise Edition - Admin Server, next you have to enter the Admin server host name, Port number and SSL Port number. Then follow the steps from 4 to 9.
      • If you had selected Enterprise Edition - Managed Server, enter the associated Admin server Host name and SSL port number. If a proxy server is needed to contact the admin server from the Managed Server machine, click on the proxy server check box. In the next screen, enter the Host name, Port number, User Name and Password of the proxy server. Then follow steps from 4 to 9.
  4. Select the language in which you wish to install Applications Manager. The options are English, Simplified Chinese, Japanese, Vietnamese, French, German, European Spanish, Korean, Hungarian and Traditional Chinese.
  5. Choose whether it is trial or registered. If registered, the next screen will prompt you to select the registered license file from your system.
  6. Specify the port at which web server has to be started. By default, it is 9090. This is the port at which you will connect the web client.
  7. Select the Database back-end support:
    • PostgreSQL - PostgreSQL comes bundled with your download of Applications Manager from Build 11000. We support PostgreSQL versions up to 10.12 (for 32-bit installation) and 11.7 (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.
      • CREATE DB
      • LOGIN
      • REPLICATION
      • NO ROLE CREATION
      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.
      • LOGIN/CONNECT
      • SELECT PRIVILEGES

      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.

    • Microsoft SQL Server (version 2005, 2008, 2012, 2017) - If you select Microsoft SQL Server, you need to select if it is based on SQL Authentication or Windows Authentication. If it is based on SQL Authentication, enter the Host Name, Port Number, Database Name, User Name, Password of the SQL Server. If it is based on Windows Authentication, enter the Host Name, Port Number, Database Name of the SQL Server and the User Name , Password of the machine in which SQL Server is running. Also provide minimum privileges required - The user account should be the DB_Owner of the created database.

      From build 15000 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.

    • Note:
      • Access to the master database is required for the backend database.
      • DB Name, Username and Password fields should not contain any special characters for MS SQL backend database, except the following:
        • DB Name    - [ @ . , _ = ^ # - ]
        • User Name - [ @ . , _ = * ^ # - \ ]
        • Password    - [ @ . , _ = * ^ # - ]
  8. Provide the location where the Applications Manager should be installed in your machine. Click Next.
  9. Current Settings is displayed in the next screen. If you need to make changes, click Back, else click Next to continue installation.
  10. Click Finish to complete the installation process.
  11. You have an option to fill up a registration form for Technical Support.
  12. Finally, select if you want to view the ReadMe file or click Finish to launch Applications Manager immediately.
Note :
  • You can install Applications Manager via Command Line also by executing the following command in the command line:
    ./<fileName>.bin -i console
    For example, if the name of the file is 'ManageEngine_ApplicationsManager.bin', then the command should be as follows:
    ./ManageEngine_ApplicationsManager.bin -i console
  • Execution of the above command would take you through the installation process. However, to execute .bin type of files, users should require Execute permission.
  • When installing Applications Manager in a Linux machine, make sure that the installation is done using a non-root user account with admin privileges.

Troubleshooting an Installation process

In case of problems during installation in a Linux system, follow the steps given below to produce the logs files:

  1. Create a text with the same name as that of the installer and with extension as ".sp". i.e, For <fileName>.bin, create a text file named <fileName>.sp. For example, if the file name is ManageEngine_ApplicationsManager.bin, create a text file named ManageEngine_ApplicationsManager.sp
  2. Open the ".sp" text file in an editor, add is.debug=1 as the content.
  3. Save the ".sp" text file in the same directory where the binary file resides.
  4. Change to the directory where the binary file is present by executing cd command
  5. Invoke the installer as ./<fileName>.bin -is:javaconsole -is:log log.txt
  6. The above command will create the log file named log.txt. Mail the log file to appmanager-support@manageengine.com.
Note
If the execution of the installation command throws an error such as "there may not be enough temporary space available in the temp folder", then execute the file with the argument as
For Windows: <fileName>.exe -is:tempdir $DIRNAME
For Linux: ./<fileName>.bin -is:tempdir $DIRNAME
where $DIRNAME is the absolute path of any existing directory.

 

Troubleshoot: For more Installation Troubleshooting, refer Troubleshooting page on our website.

Uninstalling Applications Manager

Windows

  • Shut Down Applications Manager (Make sure that the ManageEngine ApplicationsManager service is stopped if installed as a Windows service)
  • Open a command prompt as an administrator [ Command Prompt → right click → Run as administrator], go to Applications Manager Home directory and execute the following commands:

    shutdownApplicationsManager.bat
    shutdownApplicationsManager.bat -force

  • Exit out of the command prompt and close all files, folders opened in the <Applications Manager Home> directory
  • Click Start → Programs → ManageEngine Applications Manager → Uninstall Applications Manager
  • Also from Control Panel → Add/Remove Programs.

Linux

For Applications Manager v15980 and above, follow the steps given below to manually uninstall Applications Manager in Linux:

  • From the command line, go to <Applications Manager Home> directory (by default it is /opt/ManageEngine/AppManager) and execute the below commands:

    sh shutdownApplicationsManager.sh
    sh shutdownApplicationsManager.sh -force

  • Exit out of the command prompt and close all files, folders opened in the <Applications Manager Home> directory.
  • Execute the command ./uninstallApplicationsManager from the <Applications Manager Home> directory.
  • Click Uninstall in the pop-up screen.

Note: You can uninstall Applications Manager via Command Line also. Type the following command in the command prompt:
./uninstallApplicationsManager -i console
Execution of this command would take you through the uninstallation process.

Here's how you can manually uninstall Applications Manager

 

Frequently Asked Questions (FAQs)

Question: How can perform a "Silent Installation" of Applications Manager?

Solution: To perform silent installation of Applications Manager, refer to the following links:

 

Question: I downloaded the .bin file to install Applications Manager in my Linux machine. When I tried to execute the file I got a dialog box displaying "Could not display the file. File is of an unknown format".

Solution: You must change the permission for the downloaded file. To do so, execute the following command to provide the permission for executing the downloaded file:

chmod +x <nameofbinary>.bin

Example: chmod +x ManageEngine_ApplicationsManager_64bit.bin

After executing the above command, you will be able to install Applications Manager in Linux machine.

Troubleshooting

For troubleshooting tips on installation and setup, go to our support portal.