Upgrading the Primary EPM software interactively

Before you begin

Ensure that you upgrade the operating system on the server as described in Operating system upgrade overview.
Complete the Primary EPM server upgrade worksheet and have it available to help answer the questions raised during the installation.
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, ensure that you have staged the required files as mentioned in Staging the Experience Portal 6.x or 7.x backup files on the Primary EPM before upgrading Experience Portal.
Download any patches for Avaya Experience Portal Release 8.1 from the Avaya Support website at http://support.avaya.com.
Ensure that you have completed the software upgrade prerequisites described in Prerequisites checklist for upgrading Experience Portal.
For disk space related information, see Space requirement for upgrading primary EPM on Red Hat Enterprise Linux and Space requirements for upgrading primary EPM on Avaya Enterprise Linux.
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.

	Note:
	You can run the prerequisite installer before installing Experience Portal. For more details, see Platform Vendor Independent Check

Procedure

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.

	Note:
	By default, the craft and sroot users are disabled in Avaya Experience Portal 8.1 Avaya Enterprise Linux fresh installations. Avaya Service Login accounts can only access the Avaya Experience Portal system if they are EASG protected.

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.

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.

Change to the mount point directory.
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.
Press Enter to continue.
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.
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.
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>.
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
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.
Check the status of the vpms service and all other services by running the following command:

systemctl is-active vpms tomcat sl activemq httpd postgresql epmcompmgr

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.
If upgrading from Experience Portal 6.x or 7.x, establish whether a new EP Signing Certificate needs to be generated:
- In the EPM web interface, navigate to Security > Certificates > EP Signing Certificate.
- Inspect the Security Certificate > Basic Constraints > CA entry. If the CA entry is set to false then do the following:
  - Create a new EP Signing Certificate: Navigate to Security > Certificates > EP Signing Certificate > Certificate tab and select Generate.
  - Manually reboot the EPM: SSH onto the EPM server and initiate a reboot via the Linux command line For example, reboot.
  - Remove and re-add the MPP server, using the same name and IP. After the MPP is added, select the Trust new certificate option.
  - Click Save.
To use an EPM 8.1 server with an older version of MPP server, run the setup_vpms.php script on the MPP server to authorize the security certificate, and restart the MPP.
Reestablish the link between the MPP and the EPM as described in Reestablishing the link between the EPM and the MPP.
Navigate to the MPP Manager page in EPM and restart the MPPs
If the Auxiliary EPM has outcalls in progress, do not run setup_vpms.php script on the Auxiliary EPM server.
Upgrade the Auxiliary EPM. For more information, see Auxiliary EPM software upgrade overview.
Important:

If you are running outcalls during the upgrade, you must upgrade the Auxiliary EPM before upgrading the MPPs.

If you wish to change the postgres database password specified by the upgrade utility, run the SetDbPassword.sh script.

Important:

If Proactive Outreach Manager is installed on this system, then you must run the script SetDbPassword.sh to change the password for the database user postgres. The Experience Portal upgrade program automatically generates a new password for the database user postgres. However, Proactive Outreach Manager is already configured to use the old password. To keep Proactive Outreach Manager working, you must change the password for the database user postgres back to the value that you have configured in Proactive Outreach Manager. For more information about configuring the PostgreSQL database user accounts, see Administering Avaya Experience Portal.

Experience Portal 7.2.0.0.x and 7.1.0.0.x includes WebLM Server 7.0 which mandates EULA acceptance for all installed licenses. Due to this, WebLM licenses will need to be re-installed or re-allocated if the system that was upgraded was using a co-residing WebLM server and an Experience Portal version older than 7.1.0.0.x.

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

	Important:
	If you are running outcalls during the upgrade, you must upgrade the Auxiliary EPM before upgrading the MPPs.