Upgrading the Auxiliary Experience Portal software interactively

Last Updated : Jun 05, 2026 |

Before you begin

  • Upgrade the Primary EPM server before you upgrade the Auxiliary EPM server.

  • Complete the Auxiliary EPM server upgrade worksheet and have it available to help answer the questions raised during the upgrade.

  • Before you install the software, read the Avaya Experience Portal Release notes on the Avaya Support site. These release notes contain information about the product that is not included in the formal documentation set.

  • If upgrading from Avaya Experience Portal 6.x or 7.x, the upgrade is treated as a fresh install where the same IP and Auxiliary EPM name, used in Avaya Experience Portal 6.x or 7.x, must be configured.

  • If upgrading from Avaya Experience Portal 6.x or 7.x, it is important to know the Primary EPM password for the vpcommon database account. This password is provided during the original installation of the primary EPM. If the password is not known, you need to reset the password before upgrading the Auxiliary EPM. For more information on resetting the password, see the Changing PostgreSQL user account passwords section in the Administering Avaya Experience Portal document.

  • Download any patches for Avaya Experience Portal Release 8.1 from the Avaya Support website at http://support.avaya.com.

  • Ensure that you upgrade the server operating system as described in Operating system upgrade overview.

  • Ensure that you complete the software upgrade prerequisites described in Prerequisites checklist for upgrading Experience Portal.

  • If you have installed a managed application, contact the provider of the managed application to check if you need to perform any additional steps as part of the Experience Portal upgrade.

  • Ensure that you download the Avaya Experience Portal ISO file from the Avaya Support web site and burn it to a DVD if required.

Procedure

  1. Log in to the server on which you want to upgrade the Auxiliary EPM software.

    If you are an Avaya Services representative, and use Avaya Enterprise Linux, the Avaya Service accounts will not be available after the Avaya Enterprise Linux upgrade. The Avaya Service accounts will be available through EASG configuration during the Experience Portal upgrade.

    • Log on to the local Linux console as root.

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

    Note:

    Ensure that you upgrade using the same Linux account that was used during the prior installation. If you upgrade an Experience Portal system by using a Linux account that is different than the account used during the previous install or upgrade, the upgrade might fail.

    This applies to RHEL (software-only) customers. It does not apply to the root and sroot users in Avaya Linux.

  2. Insert the Avaya Experience Portal 8.1 software installation DVD into the DVD drive of the server.
    Tip:

    These instructions assume that you are going to access the Experience Portal installation DVD by mounting the appropriate DVD drive on the target system. If you want to access the installation DVD files from a shared network directory or a local directory, you can copy the Experience Portal installation ISO image to that directory. However, that directory must be readable by all users on the system. If the directory is only readable for root users, the installation script will encounter errors and will not complete successfully.

  3. Mount the Avaya Experience Portal 8.1 software installation DVD. The mount command depends on the server's hardware and operating system.

    • If you are working with Avaya Enterprise Linux, mount the DVD by entering the mount /mnt/cdrom command, where /mnt/cdrom is the mount point typically associated with the DVD drive in the fstab file.

    • If you are working with a supported version of Red Hat Enterprise Linux Server, to mount the DVD:

      • Run the mkdir -p /media/cdrom command.

        Note:

        This command is required only if the /media/cdrom mount point does not exist.

      • Run the mount -o ro /dev/cdrom /media/cdrom command.

      Warning:

      When Red Hat Enterprise Linux Server automatically mounts the DVD, the files on the DVD are not executable. You must manually mount the Experience Portal installation DVD using the commands shown above.

  4. Change to the mount point directory.
  5. Enter the bash aepinstall.sh command and press Enter to start the installation script.

    The bash aepinstall.sh script checks to make sure the calling user has root privileges.

  6. Press Enter to continue.
  7. Read through the end user license agreement and select Y to accept the terms of the license agreement.

    Experience Portal automatically starts the PVI checker, which analyzes your system’s hardware and operating system configuration. The PVI checker does the following:

    • Checks to ensure that a non-root user account has been created.

    • Asks the user to confirm that one of these accounts is the non-root account the user has configured, and to set the password.

    • Checks for any missing pre-requisite RPMs and installs any if missing.

    • Creates a log file in /opt/Avaya/InstallLogs/pvicheck.log.

    • Checks if default umask is set to 027. If it is not set to 027, the installer asks if you want to set it to 027. If you select 'yes', the installer applies this setting to the OS. If you select 'no', the installer exits.

  8. After the configuration analysis is complete, the PVI checker displays a message stating whether all prerequisite checks passed followed by the first Prerequisite Status page.
  9. Press Enter to end the installation script.

    During the installation process, Experience Portal creates several log files that you can use to verify what happened during installation. When the installation process is complete, Experience Portal moves these logs to the standard log directory and displays the exact path on the screen. You can view the detailed logs at $AVAYA_HOME/logs/install_<date>.

  10. Experience Portal begins installing the software. During the install, it displays messages indicating its progress.

    The installation process can appear completed or stopped even though it is still processing and installing the software.

    Please wait until the aepinstall.sh script completes installing and displays the message:

    
20210402-17:15:15 Finished Installation

    The aepinstall.sh script creates a log file at /opt/Avaya/InstallLogs/ aepinstall.log

  11. To unmount and eject the DVD:
    1. Change the directory to a location that is outside the mount point. For example, enter the cd / command to change to the root directory.
    2. Unmount the DVD as described in the server documentation.
    3. To eject the Experience Portal installation DVD, press the button on the DVD drive or enter the eject command.
  12. Load the environment variables created during the installation by logging out of Linux and then logging back in.
    1. Log out of the Linux system.
    2. Log back in to the Linux system.

      • Log on to the local Linux console as root.

      • Or log on remotely as a non-root user and then change the user to root by enter the su - root command.

  13. Check the status of the vpms service and all other services by running the following command:

    systemctl is-active vpms tomcat sl activemq

    A list appears for each service. If the vpms service is running properly, the command displays active for all the services in the list.

Next Steps

  • To verify if the installation or upgrade was successful, go to http://EPM-Server/VoicePortal and log into the Experience Portal web interface.

    Where, EPM-server is the hostname or the IP address of the system where the primary EPM logon using EPM Administrator account.

  • Install any required patches that you download from the Avaya online support website, http://support.avaya.com.

  • Do the following to re-establish the link between the Primary EPM and the Auxiliary EPM:

    Note:

    If you are upgrading from Avaya Experience Portal 6.x or 7.x, the trust relationship may already be established, therefore the following steps may not be required.

    1. Log in to the EPM web interface using an account with the Administration user role.

    2. On the EPM main menu, click System Configuration > EPM Servers.

    3. Click the name of the Auxiliary EPM server.

    4. On the Change EPM Server page, navigate to the Auxiliary EPM Certificate section and select the Trust new certificate check box if the check box is visible.

    5. Click Save.

  • Upgrade the MPP software on the MPP servers as described in Upgrading the MPP software interactively.

    Note:

    If you log in to the upgraded EPM before you upgrade the MPPs, all MPPs in the system might display Restart Needed in the State column on the System Monitor and MPP Manager pages. EPM automatically updates the state after you upgrade the MPP software and reconnect the upgraded MPP servers with the EPM.

  • Install the Avaya Service Account authentication file. For more information about installing the Avaya Service Account authentication file, see Troubleshooting Avaya Experience Portal.

  • If you see a Restart Needed status on the EPM Manager page, do the following:

    • Run the /opt/Avaya/ExperiencePortal/Support/Security-Tools/SetDbPassword.sh script on the Auxiliary EPM.

    • Update the password for the vpcommon user of the Primary EPM by running the update_primary_vpcommon option.