Steps to configure Azure PostgreSQL Database as Applications Manager's back-end

Steps to configure Azure PostgreSQL Database as Applications Manager's back-end

Applications Manager comes bundled with PostgreSQL. If you want to use your own PostgreSQL instead, follow the steps mentioned below:


  1. A compatible PostgreSQL database should be accessible from Applications Manager installation. To know the supported versions and database user permissions, click here.

  2. A PostgreSQL User with privileges to login, create database, and has full control over the tables in that database.


1. Install Applications Manager with bundled PGSQL backend. It is recommended that you do not launch the application during the installation set up after choosing bundled Postgres as the backend. This avoids creating APM related tables in the bundled PGSQL database.

2. Create an Azure PostgreSQL database in the Azure portal.
Ensure that DB port 5432 is open to ensure that proper connection to the database can be made from Applications Manager server.

3. Get the following information from the database to connect to it:

  •      Azure PostgreSQL Database Server name [Hostname]

  •      Database port number

  •      Database admin username

  •      Database password

4. Connect to the server in which Applications Manager is installed and modify the below files to change the database configuration settings from bundled PgSQL to Azure PostgreSQL database.

  1. Edit AppManager\conf\ file using a text editor (like wordpad or vi or sublime) and make the following changes:

    Replace am.dbport.check=true with am.dbport.check=false.
    Replace am.db.port=15432 with am.db.port=<PostgreSQL port> (ex:  am.db.port=5432)

  2. Modify AppManager/working/conf/database_params.conf file:

  • Change the host and port details:
    Replace localhost:5432 with AzurePGSQLServer:<port number> 
    From this,

    It should now look like this

  • Change the database username:
    Replace the default <username> with <username@host> where the username is AzurePGSQL username and host is the AzurePGSQL hostname.
    From this,

    It should now look like this:

  • Change the database password
    Replace the keyword encryptedpassword with password and type the AzurePGSQL database password next to it.
    From this,

    It should now look like this:

  • Once you implement the above changes, save the file. Then, copy and replace the file in the following directory: AppManager/working/conf/database_params.conf.

5. Take a backup of AppManager\working\bin\startPGSQL.bat/.sh file and AppManager\working\bin\stopPGSQL.bat/.sh file and then extract patch from this link under <AppManager_Home> directory.

6. Start Applications Manager.

          • Related Articles

          • Connecting to Applications Manager's bundled database

            How can I connect to Applications Manager's back-end database? Note: Take a backup of the AppManager directory before modifying anything in the database. Check am.dbserver.type value in <Applications Manager Home>\conf\ file to ...
          • ManageEngine Applications Manager High Availability setup with dual database (MySQL).

            Apart from the Failover setup,  which uses a single database and dual Application Server, we also support a failover with dual database and Application Server. Failover support requires you to configure Applications Manager Secondary (Standby server) ...
          • Error message while performing database backup of Applications Manager

            While performing a database backup operation of Applications Manager build with Pgsql backend, you may encounter the following error, especially when your database size has grown bigger with a large number of tables.   pg_dump: WARNING: out of shared ...
          • Microsoft Azure VM - Enabling Diagnostics extension for Windows & Linux VMs

            Steps to enable Diagnostics extension for Windows VMs 1.Log in to Azure Portal ( using the credentials of 'Administrator'. 2.Navigate to your virtual machine. 3.Click on 'Diagnostics settings' on the vertical pane. Select ...
          • Azure SQL Database - FAQ

            1. Why have we removed the Diagnostic Settings dependency in Azure SQL Database monitor? Till APM v15240: Azure SQL Database was using Diagnostic Settings to perform data collection. Prerequisites had to be fulfilled to turn on Diagnostic Settings ...