Page History

...

1. Verify that there is a full backup 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 to stop data collection and 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 accordingly:
• 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] - 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 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, 16 for SharePoint 2016)
   • [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 database server name to match the new server that now hosts the CardioLog database.
     
     
9. Edit the database connection string in the configuration file located in the CardioLog Installation 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 database server name to match the new server that now hosts the CardioLog database.

10. 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.

...

1. Export the CardioLog registry key to a *.reg file:
   
   • 32-bit machine  - HKEY_LOCAL_MACHINE\SOFTWARE\Intlock\CardioLog  
   • 64-bit machine  - HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Intlock\CardioLog
2. Edit the CardioLog registry key (*.reg file):
   
   

   "DATABASEINSTANCE"="[database server name]"

   "TARGETDIR"="[CardioLog Installation Folder]"

     [database server name] - The database server name that currently hosts the CardioLog database.
     [CardioLog Installation Folder] - Edit the database server name to match the new server that now hosts the CardioLog application.

3. Import the CardioLog registry key to the new server by copying the *.reg file to the new server and double clicking on it.
4. Disable both CardioLog windows services, CardioLog Diagnostics Service and CardioLog Scheduling Service, on the old CardioLog application server.
5. Run the CardioLog installer on the new server (contact us to receive it). Follow the Installation Wizard steps.
6. Create a backup of the [CardioLog Installation Folder]\CardioLogScheduleServices\Settings.config on the new server.
7. Copy the [CardioLog Installation Folder]\CardioLogScheduleServices\Settings.config from the old server to the new server and edit all instances of the CardioLog server name to match your system (http://[CardioLog server name:port]/) and the CardioLog Installation Folder path.
8. In the CardioLog database, edit the URL and server name columns in the tab_management table by executing the following SQL script:
   
   Use CardioLog
   GO
   
   update tab_management set url = replace (url, '[Old URL]', '[New URL]'), servername = replace (servername , '[Old machine name]', '[New machine name]')
   
   For the respective fields, confirm that all names match your system:
   
   [Old URL] - http[s]://CardioLog-machine-name:port
   [New URL] - http[s]://CardioLog-new-machine-name:port
   [Old machine name] - CardioLog old machine name
   [New machine name] - CardioLog new machine name
   
   
9. If you have implemented the CardioLog Analytics SharePoint Feature on your Web Front Ends (WFEs), edit all instances of the CardioLog server name (eg., http://[CardioLog server name:port]/ ) in the /_layouts/CardioLogAgent/web.config file, located on the SharePoint WFEs respecitvely:
   
   

   For MOSS 2007 only:
   C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\TEMPLATE\LAYOUTS\CardioLogAgent/web.config
   
   For SharePoint 2010, 2013 only:
   C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\LAYOUTS\CardioLogAgent/web.config
   
   For SharePoint 2016 only:
   C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\16\TEMPLATE\LAYOUTS\CardioLogAgent/web.config
   
   Otherwise, edit the CardioLog Java Script tracking code embedded within a common Java Script file, located on your SharePoint WFEs. The code is located at the end of the file, between the comments: //Intlock tracking code start and  //Intlock tracking code end
   
   For MOSS 2007 only:
   C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\TEMPLATE\LAYOUTS\1033\core.js
   
   For SharePoint 2010 only:
   C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\LAYOUTS\1033\init.js
   
   For SharePoint 2013 only:
   C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\TEMPLATE\LAYOUTS\init.js
   
   For SharePoint 2016 only:
   C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\16\TEMPLATE\LAYOUTS\init.js
   

Anchor
migrate sp farm migrate sp farm

How to Configure CardioLog When Migrating a SharePoint Farm

...