...
This document makes the following assumptions (in no particular order):
| Info |
|---|
Note: The reason for these assumptions is that EngageIP uses encrypted connection strings which will need to be replaced and cannot be edited. |
A recent backup of the EngageIP databases was made and backed up off server / off site (including: Boss, BossCollector, BossRate, EngageIP Master)
The new server IP addresses are the same as the original IPs that EngageIP was using
The SA username and password used by EngageIP is the same
The databases are restored using the same names
EngageIP Billing directory was fully backed up including:
CDR Usage data
Usage Importer and Rater
Any custom customer portal files used
EngageIP Billing is installed in the same directory on the webserver
You have recorded the full license key for EngageIP
You have a backup copy of the EngageIP 8 billing installer executable for the version that was installed on the server
EngageIP Billing services (EngageIP Billing, EngageIP Event Manager)
The EngageIP registry is backed up
[HKEY_LOCAL_MACHINESOFTWAREEngageIPParameters]
[HKEY_LOCAL_MACHINESOFTWAREHawki4Parameters]
...