Reinstalling the primary EPM software on a dedicated EPM server

About this task

Follow this procedure if the primary EPM software resides on a dedicated server. If your EPM software resides on the same server as the MPP software, see Reinstalling the EPM and MPP software on a single server. If you want to reinstall the auxiliary EPM software, see Reinstalling the auxiliary EPM software.

Procedure

If your site uses customized scripts, do the following to ensure you do not lose those scripts when the installation procedure writes over the scripts for the Database Backup utility:
1. Navigate to the backup directory located in $AVAYA_HOME by entering the cd $AVAYA_HOME/Support/Database/DBbackup command.
2. Copy all the files in this directory to a temporary directory.
If you changed the values for event and alarm record retention in the Experience Portal database, do the following to ensure that you can correct those values after the installation procedure resets them to the default values:
1. From the EPM main menu, select System Configuration > EPM Servers > Alarm/Log Options.
2. On the Viewer Settings page, take note of the current values.
  The default for Purge Enabled is Yes for all record types, and the default retention times are:
  - 7 days for alarm records
  - 15 days for event records
  - 180 days for audit log records
Log on to Linux on the Experience Portal server with root privileges.
The reinstallation procedure is identical to the upgrade procedure because the installation script will find a previous version of the EPM on the server. The fact that the previous version is the same release as you want to install makes no difference to the installation script. You can reinstall the EPM software by running the aepinstall command. If you run the aepinstall command, you must do the following after installing the Experience Portal software:
1. Run the setup_vpms command to reauthorize the security certificate.
2. Reestablish the link between the MPP and the EPM by trusting the MPP's security certificate.
Note:

For more information about the aepinstall command, see Implementing Avaya Experience Portal on multiple servers.
If you copied your customized Database Backup utility scripts to a temporary location at the beginning of this procedure, copy your customized files back to the /var/lib/pgsql/DBbackup directory.

	Note:
	For more information about the aepinstall command, see Implementing Avaya Experience Portal on multiple servers.