Print

EPM screen not displayed after restoring Experience Portal on a new server

EPM screen is not displayed after restoring Experience Portal on a new server. This problem typically occurs when the postgres password on the new EPM server is different from the password configured on the primary EPM server.

Proposed Solution

Before you begin

  • Ensure you have a backup of Experience Portal data on the backup server

  • Make sure you have restored the Experience Portal backup data on a new server.

  • Verify if EPM and Tomcat application server are running.

Procedure

  1. Log on to Linux on the Primary or Auxiliary EPM server.

    If you are an Avaya Services representative and are using 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. So,

    • Log on to the local Linux console as root.

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

  2. Enter the cd $AVAYA_HOME/Support/Security-Tools command, where $AVAYA_HOME is an environmental variable pointing to the name of the installation directory specified during the Experience Portal software installation.
  3. Enter the bash SetDbPassword.sh update -u username command, where username is the name of the user account whose password you want to change. The username in this case is vpcommon.
  4. Type the password you want to use for this account and press Enter.

    After the password is accepted and updated, the script will display a message prompt indicating the services will be restarted and ask if the user wants to proceed.

    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.

      noteNote:

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