In order to upgrade CardioLog Analytics, you must uninstall your current version before installing the new version. Uninstall does not stop usage data collection.
Contact us to receive the detailed upgrade procedure and the license codes required for the new version.
Note: Support is provided for product versions released within the past 18 months. Please review the Intlock Support Policy.
Contents
Running the Uninstall Wizard
- Stop CardioLog Scheduling Service and CardioLog Diagnostics Service
- Go to the Windows Start menu and open All Programs, right-click CardioLog Analytics and select Uninstall.
- Follow the Uninstall Wizard steps.
Running the Install Wizard
- Open CardioLog-Analytics-2.0.XXX.XXX.exe
- Follow the Installation Wizard steps.
- Start CardioLog Scheduling Service and CardioLog Diagnostics Service
- Perform IISRESET on the CardioLog application server.
Note: If you are upgrading from versions lower than 2.0.3.0:
Upgrade your product to version 2.0.3.0 first.
Note: If you are upgrading from versions lower than 2.0.2.0:
Install the following components on the CardioLog server:
- Microsoft .NET Framework 3.5 Service Pack 1
- Microsoft Chart Controls for Microsoft .NET Framework 3.5
For Windows Server 2003 x64 with IIS 6.0, make sure IIS runs in 64-bit mode.
For Windows Server 2008 x64 with IIS 7.0, make sure that the CardioLog application pool runs in 64-bit mode:
- Open IIS Manager > Application Pools > Right click CardioLogApplicationPool
- Select Advanced Settings > Click Enable 32-bit Applications and select False
- Click OK > Right click CardioLogApplicationPool and then select Recycle
Upgrading the Tracking Agent
If you have customized the Tracking Agent code in your environment (i.e. customized search), please contact us before upgrading your product.
For SharePoint Online, see how to update the tracking code on all SharePoint Online site collections.
Updating the tracking code:
- Backup the Java Script tracking code.
By default, the Java Script tracking code is embedded within a common Java Script file on your SharePoint WFEs -
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 MOSS 2007 with "CardioLog Analytics" SharePoint Feature only:
C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\TEMPLATE\LAYOUTS\CardioLogAgent\CardioLogAgent.js
For SharePoint 2010 with "CardioLog Analytics" SharePoint Feature only:
C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\LAYOUTS\CardioLogAgent\CardioLogAgent.js
For SharePoint 2013 with "CardioLog Analytics" SharePoint Feature only:
C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\TEMPLATE\LAYOUTS\CardioLogAgent\CardioLogAgent.js
OR
C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\TEMPLATE\LAYOUTS\CardioLogAgent\CardioLogAgent.js
The code is located at the end of the file, between these comments: "//Intlock tracking code start", "//Intlock tracking code end".
- Replace the Java Script tracking code with the one in CardioLog/SharePoint Marketing Suite > Administration > System Configuration > Usage Tracking Code (select your SharePoint version).
For "CardioLog Analytics" SharePoint Feature only:
Edit the Java Script tracking code - replace all the occurrences of http://[server name]:[port]/ (CardioLog server name and port) with /_layouts/.
Updating Remote Tracking Agent Files:
If you have tracking agents which reside on your SharePoint WFEs (i.e. under "_layouts" when using the "CardioLog Analytics" SharePoint Feature), update the CardioLog tracking agent files:
- Create a backup of the CardioLogAgent directory (located on the SharePoint WFEs).
- Copy the installation files from [CardioLog Installation Directory]\CardioLogAgent to the existing CardioLogAgent directory, except the web.config file and customized files (if you have customizations in the Tracking Agent code in your environment, i.e. customized search, please contact us before replacing the files)
- Edit the following keys in the CardioLogAgent\web.config file, located under the <appSettings> section -
<add key="CardioLogAgentRoot" value="/_layouts"/>
<add key="version" value="2.0.8.3"/>
- Add the following keys to the CardioLogAgent\web.config file, located under the <appSettings> section -
<add key="UseSPAuth" value="false"/>
<add key="FixClaimsUserAccountRegex" value="^(.*[|])(.*)$"/>
If your tracking agent is configured to identify authenticated users by retrieving their sign-in user name from SharePoint (as detailed here):
- Delete the following key from the CardioLogAgent\web.config, located under the <appSettings> section -
<add key="GetUserNameCustom" value=" function GetUsername() { __trace("GetUsername"); var currentUsername = __readCookie("_userid"); var currentUserId = __readCookie("spUserid"); if (typeof(_spPageContextInfo) != "undefined") { if (!currentUserId || currentUserId != _spPageContextInfo.userId) { currentUsername = null; __saveCookie("spUserid", _spPageContextInfo.userId, 1000, element.CookieDomain); } } var useridInput = this.document.getElementById("userid"); if (useridInput && useridInput.value != "") { currentUsername = useridInput.value; } else if (currentUsername == null || currentUsername == "") { if (typeof (getSPUserAccount) != "undefined") { currentUsername = getSPUserAccount(); } else { currentUsername = "Anonymous_"+Math.random()*100000; } } __saveCookie("_userid", currentUsername, 1000, element.CookieDomain); __trace("GetUsername return: "+currentUsername); return currentUsername; }"/>
- Edit the following key in the CardioLogAgent\web.config, located under the <appSettings> section -
<add key="UseSPAuth" value="true"/>