Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 16 Next »

If you have an instance of your CardioLog database already configured on a specific server, you can transfer the database and application 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 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]\SP2007Tree\Web.config
    • [CardioLog Installation Folder]\SP2010Tree\Web.config
    • [CardioLog Installation Folder]\SP2013Tree\Web.config
    • [CardioLog Installation Folder]\SPTree\Web.config
    • [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.

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. 
Contact us to receive the latest CardioLog installer. 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:

  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 installation folder path to match the path that the CardioLog application will be installed on, on the new server.

  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 using the credentials of your CardioLog service account. Follow the Installation Wizard steps.
  6. Contact us to receive the required licenses for the new server and apply them using the License Admin tool (copy the Microsoft.Licensing.LicAdmin.exe tool from [CardioLog Installation Directory]\Setup Files\SLPS\ to [CardioLog Installation Folder]\CardioLogScheduleServices\ and execute it from there).
  7. In the CardioLog database, edit the server name in the tab_management and tab_global_settings tables by executing the following SQL script (edit the old and new CardioLog server name):

    Use CardioLog
    GO

    declare @oldName varchar(max) = 'CardioLog old machine name';
declare @newName varchar(max) = 'CardioLog new machine name';

--== 1. tab_management table
update tab_management
set 
	url = replace(url, @oldName, @newName), 
	serverName = @newName;

--== 2. Global settings
--== 2.1. CardioLog.Host
exec [dbo].[stp_global_settings_upsert] @Category = 'CardioLog', @Name = 'Host', @Value = @newName, @ReplaceIfExists = 1;

--== 2.2. PdfExport.CardioLogPdfRoot
declare @value varchar(max) = (select Value from tab_global_settings where Category = 'PdfExport' and Name = 'CardioLogPdfRoot');
if (@value is not null)
begin
	set @value = replace(@value, @oldName, @newName);
	update tab_global_settings set Value = @value where Category = 'PdfExport' and Name = 'CardioLogPdfRoot';
end
  8. 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 respectively:

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

How to Configure CardioLog When Migrating a SharePoint Farm

To configure the CardioLog application when migrating a SharePoint Farm from one location to another, follow these steps:

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. eg. "SharePoint_Config"
    • Authentication - Database authentication type: Windows Integrated, or SQL Authentication.
    • SharePoint TEMPLATE Directory - this is the full path for the SharePoint 'TEMPLATE' directory. eg. \\<sharepoint server name>\C$\Program Files\Common Files\Microsoft Shared\Web Server Extensions\XX\TEMPLATE\" (Where XX - 12 for MOSS 2007; 14 for SharePoint 2010; 15 for SharePoint 2013, 16 for SharePoint 2016)
  4. Click Apply.
  5. Select the web applications you would like to monitor, then click Save.
  6. After the next run of Portal Tree Updates, the updated tree structure will be available in the Analysis Center and Object Explorer.


    System Configuration - SharePoint Tree Adaptor

In versions lower than 2.0.8.0, follow these steps:
  • 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  (Where XX is 07 for MOSS 2007; 10 for SharePoint 2010; 13 for SharePoint 2013):

<connectionStrings>

<add name="configDB" connectionString="Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=[SharePoint Configuration Database Name];Data Source=

[SharePoint Database Server Name]" />

<add name="contentDB" connectionString="Integrated Security=SSPI;Persist Security Info=False;Initial Catalog={0};Data Source={1}" />

</connectionStrings>

           [SharePoint Configuration Database Name] - Your SharePoint configuration database name
           [SharePoint Database Server Name] - Your SharePoint database server name

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

<add key="includedWebApps" value="[SharePoint web application root URL]" />

<add key="SharePointTemplatePath" value="[SharePoint TEMPLATE path]" />

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

Configure Event Collection

You may either install the CardioLog Analytics Tracking Agent Feature, 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 and select Usage Tracking Code and then select your SharePoint version.

  • No labels