Configuring an auxiliary EPM server

Last Updated : Jun 05, 2026 |

About this task

The auxiliary EPM server:

  • Can assign outgoing calls made with the Application Interface web service to an available MPP server. Avaya Experience Portal does not provide load balancing or failover, however. You must use a third-party product for these purposes.

  • Shares Application Logging web service requests when the primary EPM server is in service.

    Note:

    When using the Application Logging web service, Orchestration Designer provides failover and load balancing between the primary and auxiliary EPM servers. Applications written with other tools must provide their own load balancing and failover mechanisms for this web service.

  • Handles all requests when the Primary EPM is down.

  • Does not include the EPM web interface, therefore it cannot be used to administer the system or monitor the status of the MPP servers.

Procedure

  1. To reset the password for the vpcommon PostgreSQL account:
    1. Log on to Linux on the Experience Portal Primary EPM server.

      • If you are an Avaya Services representative, and use Avaya Enterprise Linux, or if the Avaya Service accounts are installed on this server, log on to the local Linux console as root.

      • Otherwise, log on remotely as a non-root user, and then change the user to root by entering the su - root command.

    2. Navigate to the Support/Security-Tools directory by entering the cd $AVAYA_HOME/Support/Security-Tools command.

      $AVAYA_HOME is the environment variable pointing to the name of the installation directory specified during the Experience Portal software installation. The default value is /opt/Avaya/ExperiencePortal.

      Tip:

      This script is also available in the Support/Security-Tools directory of the Experience Portal installation DVD.

    3. Enter the bash SetDbPassword.sh update_primary_vpcommon command.
    4. Type the password for the vpcommon PostgreSQL account and press Enter.

      After the password is accepted and updated, the script prompts a message indicating the services to be restarted and asks if the user wants to proceed.

      Note:

      The script will not list the service that is not impacted by changing the user password.

      Example:

      The following services will be restarted automatically:
- postgresql
- vpms
- mmsserver
- avpSNMPAgentSvc
Do you wish to proceed? [Y/n]
    5. Type one of the following:

      • Y to restart the services that are listed.

      • n to cancel the restarting services.

        Note:

        If you cancel restarting the services, you should manually restart the services for the changes to take effect.

  2. Install the auxiliary EPM software on the new server as described in the Optional: Installing the EPM software on the auxiliary EPM server topic of the Implementing Avaya Experience Portal on multiple servers guide.

    When you get to the Database Login Check for Auxiliary EPM installation screen, make sure you specify the password for the vpcommon PostgreSQL database user account.

  3. When the installation has finished, add the server to the Experience Portal system:
    1. Log on to the EPM web interface.

      If Avaya Services is maintaining this system and you are an Avaya Services representative, log on to EPM by using the init EPM account that is created during the EPM software installation.

      Otherwise, log on to EPM by using an account with the Administrator user role.

    2. On the EPM main menu, select System Configuration > EPM Server.
    3. On the EPM Servers page, click Add.
    4. On the first Add EPM Server page, enter the appropriate information and click Continue.
    5. On the second Add EPM Server page, enter the appropriate information.
    6. Click OK.