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

Contents

How to Migrate the CardioLog Database

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

  1. Verify that there is a full backup for the CardioLog database.
  2. Stop the CardioLog windows services (CardioLog Diagnostics Service, CardioLog Scheduling Service) on the CardioLog application server.
  3. Stop IIS on the CardioLog application server (in order 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 in:
  8. "DATABASEINSTANCE"="[database server name]"
    [database server name] - edit the database server name (the server that hosts the CardioLog database)

  9. Edit the database connection string in the following configuration files (located in the CardioLog Installation Folder - the default path is C:\Program Files\Intlock\CardioLog):
  10. Edit the database connection string in the following configuration file (located in the CardioLog Installation Folder - the default path is C:\Program Files\Intlock\CardioLog):

  11. Start the CardioLog Windows services (CardioLog Diagnostics Service, CardioLog Scheduling Service) on the CardioLog application server.
  12. Start IIS on the CardioLog application server.

How to Migrate the CardioLog Application

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 > Product License.

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

  1. Export the CardioLog registry key to a *.reg file:
  2. Edit the CardioLog registry key (*.reg file):

    "DATABASEINSTANCE"="[database server name]"

    "TARGETDIR"="[CardioLog Installation Folder]"

      [database server name] - edit the database server name (the server that hosts the CardioLog database)
      [CardioLog Installation Folder] - edit the CardioLog installation folder (the folder that will contain the CardioLog application files on the new application server)

  3. Import the CardioLog registry key to the new server (copy the *.reg file to the new server and double click on it to add it).
  4. Disable the CardioLog windows services (CardioLog Diagnostics Service, 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 (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]')

    [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 WFEs, edit all instances of the CardioLog server name (http://[CardioLog server name:port]/) in the /_layouts/CardioLogAgent/web.config file, located on the SharePoint WFEs:

    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

    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 these comments: "//Intlock tracking code start", "//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

How to Configure CardioLog When Migrating a SharePoint Farm

To configure the CardioLog application in case of a SharePoint Farm migration, follow these steps:

1) Configure the SharePoint Farm Tree Structure

  1. In the Administration pane, click System Configuration, and then select SharePoint Tree Adaptor.
  2. Select your SharePoint farm.
  3. In the SharePoint Tree Adaptor dialog, edit the following fields:

    -      Database Server - the SharePoint database instance name.
    -      SharePoint Configuration Database Name - the SharePoint configuration database name. Example: "SharePoint_Config"
    -      Authentication - database authentication type (windows integrated or SQL authentication).
    -      SharePoint TEMPLATE Directory - this is the full path for the SharePoint 'TEMPLATE' directory. Example: "\\<sharepoint server name>\C$\Program Files\Common Files\Microsoft Shared\Web Server Extensions\XX\TEMPLATE\" (XX - 12 for MOSS 2007, 14 for SharePoint 2010, 15 for SharePoint 2013)
  4. Click Apply.
  5. Select the web application/s you want to monitor, then click Save.
  6. After the next run of Portal Tree Updates, the updated tree structure will be displayed in Analysis Center (Object Explorer).


System Configuration - SharePoint Tree Adaptor

In versions lower than 2.0.8.0, follow these steps:
  1. If the SharePoint databases are moved to a new server, edit the SharePoint database connection string in the [CardioLog Installation Folder]\SP20XXTree\Web.config file  (XX - 07 for MOSS 2007, 10 for SharePoint 2010, 13 for SharePoint 2013):

           [SharePoint Configuration Database Name] - edit the SharePoint config database name
           [SharePoint Database Server Name] - edit the SharePoint database server name

  1. If the SharePoint web application root URL was modified and/or the SharePoint web application is hosted on new WFE servers, edit the following keys in the [CardioLog Installation Folder]\SP20XXTree\Web.config file (XX - 07 for MOSS 2007, 10 for SharePoint 2010, 13 for SharePoint 2013)

           [SharePoint web application root URL] - a '*' separated list of the monitored SharePoint web applications in the farm
           [SharePoint TEMPLATE path] - edit the SharePoint TEMPLATE folder path: 
           \\SharePoint WFE server name\C$\Program Files\Common Files\Microsoft Shared\Web Server Extensions\XX\TEMPLATE\ (XX - 12 for MOSS 2007, 14 for SharePoint 2010 and 15 for SharePoint 2013) 

2) Configure Event Collection

Install the CardioLog Analytics Tracking Agent Feature as detailed here OR add the Tracking Agent JavaScript Code to each SharePoint WFE. The tracking code should be placed in a SharePoint common .js  file.

In the Administration pane, click System Configuration, select Usage Tracking Code and then select your SharePoint version.