MSSQL - IP Changes/Database Migration

Summary

When changing IP addresses or moving databases there are many details that need to be reviewed and confirmed regarding EngageIP functionality.  This article provides an overview of the required checks that need to be performed during the transition.

Moving Databases

1. Backup the databases (Note: that these may not be named as below, but in most cases are):

   • Boss

   • EngageIP Master

   • Bosscollector

2. Copy the databases to the new server

3. Restore the databases with the same names

4. Create the database user account

   • Make sure to login to SQL studio management with this account to confirm that access permissions are adequate

5. If the IP address is to be the same, no registry or connection string updates are required

6. Copy any usage directories over for telecom usage importing

7. Install the Event Manager service and EngageIP Billing service if required. In the case of a clustered environment, see Installing Clustered Services

8. Reset IIS on the webserver

9. Confirm you can login to the AdminPortal

Changing SQL Server IP

When changing IPs there are connection strings and config files that may need to be updated (if you are not using a hostname for example). The best practice is to use a hostname or something other then an IP address so that any direct IP changes will simply be address via the DNS.

1. Update IP addresses on the server

2. On Web server, update the registry hive for EngageIP (requires encrypted connection string)

3. CDR System Specific: Update hawki4 registry hive if telecom is installed (update clear text IP address*)

4. Update adminportal/web.config (requires encrypted connection string*)

5. Update adminportal/rating/voip/web.config (requires encrypted connection string*)

6. CDR System Specific: Update any other connection string files that may be used for Telecom, Importer, Rater, etc.

7. You may need to update user specific workstation tools such as printing tool. (requires encrypted connection string*)

• This requires LogiSense Customer Care in order to generate the encrypted key. Please request this before proceeding with any server changes.