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]\SP20XXTreeSP2007Tree\Web.config (Where XX is 07 for MOSS 2007; 10 for SharePoint 2010; 13 for SharePoint 2013, 16 for SharePoint 2016)
- [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. 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 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 - 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 respecitvelyrespectively:
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
...
- In the Administration pane, click System Configuration, and then select SharePoint Tree Adaptor.
- Select your SharePoint farm.
- 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)
- Click Apply.
- Select the web applications you would like to monitor, then click Save.
- 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, 16 for SharePoint 2016):
<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, 16 for SharePoint 2016)
<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, 16 for SharePoint 2016)
Anchor | ||||
---|---|---|---|---|
|
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.