Page History
...
- Verify that there is a full backup of the CardioLog database on a separate drive.
- Stop the CardioLog windows services including CardioLog Diagnostics Service and CardioLog Scheduling Service on the CardioLog application server.
- Stop IIS on the CardioLog application server to stop data collection and HTTP requests to the CardioLog application during the move.
- Detach the CardioLog database from the origin server.
- Copy the database files (data + log) to the destination server.
- Attach the CardioLog database to the destination server.
- 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. - 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.
- 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="Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=CardioLog;Data Source=[database server name];MultipleActiveResultSets=True"" providerName="System.Data.EntityClient" />
<add name="CardioLogEntities" connectionString="metadata=res://*;provider=System.Data.SqlClient;provider connection string="Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=CardioLog;Data Source=[database server name];MultipleActiveResultSets=True"" providerName="System.Data.EntityClient" />[database server name] - Edit the database server name to match the new server that now hosts the CardioLog database.
- [CardioLog Installation Folder]\CardioLog\Web.config
- Restart both CardioLog Windows services, CardioLog Diagnostics Service and CardioLog Scheduling Service, on the CardioLog application server.
- Start IIS on the CardioLog application server.
...
- 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
- 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. - Import the CardioLog registry key to the new server by copying the *.reg file to the new server and double clicking on it.
- Disable both CardioLog windows services, CardioLog Diagnostics Service and CardioLog Scheduling Service, on the old CardioLog application server.
- Run the CardioLog installer on the new server using the credentials of your CardioLog service account. Follow the Installation Wizard steps.
- 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).
- 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 - 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
...