Resetting report data positions using external databases

About this task

Use this procedure to reset report data positions in external databases after the restore scripts are run.

Though the script that is mentioned in the procedure is executed always on the primary EPM, the script may need to be executed multiple times. You will need to specify different EPM names each time it is restored. If you restore multiple EPMs then the script needs to be run once for each of those EPM names.

	Note:
	The Email and SMS report data is not collected from the primary or auxiliary EPM, if the procedure is not run on the primary EPM.

Procedure

Log on to Linux on the Experience Portal primary EPM server as a user with root privileges.
To navigate to the appropriate directory, run the cd $AVAYA_HOME/Support/VP-Tools command.
On the primary EPM, for each configured EPM name that has an SMS or Email processor, run the following command: ./ResetEmailSMSExtDB “<Database_URL>” <JDBC_Driver> <Database_User_Name> <Experience_Portal_Name> <EPM_Name>
Where,
- “<Database_URL>” is the URL of the external database as it appears on the Report Database Settings page of the EPM web interface.
- <JDBC_Driver> is the JDBC driver for the external database as it appears on the Report Database Settings page of the EPM web interface.
- <Database_User_Name> is the user name for the external database as it appears on the Report Database Settings page of the EPM web interface.
- <Experience_Portal_Name> is the name of the Experience Portal system as it appears on the EPM Settings page of the EPM web interface.
- <EPM_name> is the name of the Primary or Auxiliary EPM as it appears on the EPM Servers page of the EPM web interface.
Reboot the Primary EPM server.