Page History

If you have an instance of your CardioLog database already configured on a specific server, you can transfer the whole collection database and application to a new server when needed. This page describes the process for most configurations.

...

1. Verify that there is a full backup for of the CardioLog database on a separate drive.
2. Stop the CardioLog windows services (including CardioLog Diagnostics Service , and CardioLog Scheduling Service ) on the CardioLog application server.
3. Stop IIS on the CardioLog application server (in order to stop data collection and http HTTP requests to the CardioLog application during the move).
4. Detach the CardioLog database from the origin server.
5. Copy the database files (data + log) to the destination server.
6. Attach the CardioLog database to the destination server.
7. Edit the following CardioLog registry key inaccordingly:
• 32-bit machine - HKEY_LOCAL_MACHINE\SOFTWARE\Intlock\CardioLog  
• 64-bit machine - HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Intlock\CardioLog
  
  "DATABASEINSTANCE"="[database server name]"
  [database server name] -
edit
• Confirm that the database server name
(
• is the server that hosts the CardioLog database
)
• .
  
  
8. Edit the database connection string in the following configuration files (. The files should be located in the CardioLog Installation Folder - the Folder. The default path is C:\Program Files\Intlock\CardioLog):
   
   • [CardioLog Installation Folder]\CardioLog\Web.config
   • [CardioLog Installation Folder]\CardioLogAPI\Web.config
   • [CardioLog Installation Folder]\CardioLogMonitoringServices\CardioLog.System.Monitoring.Services.exe.config
   • [CardioLog Installation Folder]\CardioLogScheduleServices\CardioLog.Services.exe.config
   • [CardioLog Installation Folder]\EventCollector\Web.config
   • [CardioLog Installation Folder]\VisitorSegments\Web.config
   • [CardioLog Installation Folder]\ADTree\Web.config
   • [CardioLog Installation Folder]\SP20XXTree\Web.config (Where XX -  is 07 for MOSS 2007, ; 10 for SharePoint 2010, ; 13 for SharePoint 2013)
   • [CardioLog Installation Folder]\VoiceOfCustomer\Web.config
   • [CardioLog Installation Folder]\Optimization\Web.config
   • [CardioLog Installation Folder]\Redirect\Web.config
   • [CardioLog Installation Folder]\WebsiteTree\Web.config
     
     <add key="connStr" value="Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=CardioLog;Data Source=[database server name]" />
     
     [database server name] - edit the Edit the database server name (to match the new server that will host now hosts the CardioLog database).
     
     
9. Edit the database connection string in the following configuration file ( located in the CardioLog Installation Folder - the Folder. The default path is C:\Program Files\Intlock\CardioLog):
   
   
   • [CardioLog Installation Folder]\CardioLog\Web.config
     
     
     <add name="VoiceOfCustomerEntities" connectionString="metadata=res://*;provider=System.Data.SqlClient;provider connection string=&quot;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=CardioLog;Data Source=[database server name];MultipleActiveResultSets=True&quot;" providerName="System.Data.EntityClient" />
     
     <add name="CardioLogEntities" connectionString="metadata=res://*;provider=System.Data.SqlClient;provider connection string=&quot;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=CardioLog;Data Source=[database server name];MultipleActiveResultSets=True&quot;" providerName="System.Data.EntityClient" />

     
     [database server name] - edit the  Edit the database server name (to match the new server that will host now hosts the CardioLog database).

10. Start the Restart both CardioLog Windows services (, CardioLog Diagnostics Service , and CardioLog Scheduling Service) , on the CardioLog application server.
11. Start IIS on the CardioLog application server.

...

If you have not upgraded your product to the latest release yet, it is highly recommended to do so prior to migrating the CardioLog application. Find out more about the latest version by viewing our site and our knowledge base. To find out what is current your product version, go to Administration in the navigation pane and click  > Product License.

To migrate the CardioLog application to another server, using the existing database, follow these steps:

...