|
Perform the following steps to upgrade each Auxiliary EPM system that uses the customer-provided Red Hat Enterprise Linux Server.
Verify that the prerequisites have been met. For more information, see Prerequisites checklist for upgrading Experience Portal.
If upgrading from Avaya Experience Portal 6.x or 7.x, note the following:
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 in the Primary EPM UI.
While upgrading theAuxiliary EPM server, you are prompted for the following details related to the Primary EPM server:
IP address of the Primary EPM server: This IP address is required so that the system can retrieve the security certificate. To ensure that the system retrieves the updated certificate from the Primary server, first upgrade the Primary server.
vpcommon password: The vpcommon password specified during the Avaya Experience Portal 6.x or 7.x Primary EPM installation. With this user account, the Auxiliary EPM server has limited access to the main Experience Portal database.
 | Important: |
|
If upgrading from Avaya Experience Portal 6.x or 7.x and the vpcommon password is not known, you need to reset the password before upgrading the Auxiliary EPM. For more information on changing the user account password, see the Changing PostgreSQL user account passwords section in the Administering Avaya Experience Portal document. |
For more information, see Upgrading the Auxiliary Experience Portal software interactively.
| Important: |
|
You must use the interactive upgrade method by running the aepinstall script. Ensure that when you are prompted for the password to configure the Auxiliary EPM server, enter the same password that you used to upgrade the Primary 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. |