Print

Upgrading the single server Experience Portal system on Red Hat Enterprise Linux Server

About this task

Perform the following procedure to upgrade a single server Experience Portal system that uses the customer provided Linux software.

Before you begin

Verify that the prerequisites have been met. For more information, see Prerequisites checklist for upgrading Experience Portal.

Procedure

  1. Log on to the EPM web interface.
  2. On the MPP Manager page, click Stop to stop the MPP.
  3. Schedule a report data download so that EPM collects all calls records from the MPP server.

    For more information, see Preventing loss of reporting data prior to upgrading MPP.

  4. Change the state of the MPP to Offline. For more information, see Taking an MPP offline using the EPM web interface.
  5. Create a backup of the Experience Portal system.

    Ensure that you save the backup folder on an external server that is not a part of the Experience Portal system. For more information, see Backing up data.

  6. If you upgrade to Experience Portal 8.1 from Experience Portal 6.x or 7.x, you must do a fresh installation of a supported version of Red Hat Enterprise Linux Server.

    For more information, see Upgrading Red Hat Enterprise Linux Server on the dedicated EPM server.

  7. If you upgrade to Experience Portal 8.1 from Experience Portal 6.x or 7.x, you must manually stage the database backup and configuration files on the fresh installation RHEL server.

    For more information on database backup and configuration files, see Backing up data.

    1. Rename the vp_backupaa backup file to vp_upgrade.export and copy the file to /var/lib/pgsql/vp_upgrade.export.
    2. Copy the version.xml file to /opt/Avaya/InstallAgent/config/version.xml.

      Create the directory if it does not already exist. For example, mkdir -p /opt/Avaya/InstallAgent/config/.

    3. Rename the voiceportal_info.jsp to voiceportal_info.php and copy to /var/www/html/voiceportal_info.php.

      Create the directory if it does not already exist. For example, mkdir -p /var/www/html/.

    4. Copy the PG_VERSION file to /var/lib/pgsql/data/PG_VERSION.

      Create the directory if it does not already exist. For example, mkdir -p / var/lib/pgsql/data/.

  8. Disable the firewall on the Experience Portal server.
  9. Configure a yum repository that has required Experience Portal packages.
  10. Install the Experience Portal 8.1 EPM and MPP software.

    For more information, see Upgrading the Experience Portal software interactively on a single server.

    importantImportant:

    You must use the interactive upgrade method by running the aepinstall script.

  11. If you are upgrading from Avaya Experience Portal 6.x or 7.x, and the MPP server status is displayed as Not Responding in the System Monitor page, do the following to complete additional steps to reestablish communication between the primary EPM and MPP:
    1. Log in to Linux on the MPP server.
    2. Run the setup_vpms.php script.
    3. Click System Management > MPP Manager.
    4. Delete the MPP server and add the MPP server back again, using the same name and IP.
    5. Click Trust new certificate.
    6. Click Save.
  12. Trust the new security certificate for the MPP if not already completed as part of the previous step. Do the following:
    1. Log in to the EPM web interface.
    2. On the EPM navigation pane, click MPP Servers.
    3. Click the MPP server name that you upgraded.

      The system displays the Change MPP Server page.

    4. Click Trust new certificate.
    5. Click Save.
  13. On the EPM navigation pane, click MPP Manager.
  14. Change the mode of the MPP to Online.
  15. Click Start to start the MPP.
Comments on this document?
August 2025
© 2022-2025, Avaya LLC All Rights Reserved.