Versions Compared

Old Version 2

changes.mady.by.user Paul Berkowitz

Saved on

compared with

New Version 3

changes.mady.by.user Paul Berkowitz

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

In order to upgrade CardioLog Analytics, you must uninstall your current version before installing the new version. Uninstall does Uninstalling the application will not stop usage data collection. Contact us to receive the detailed upgrade procedure and

...

license codes required for

...

your new version. 

Note: Support is provided for product versions released within the past 18 months. Please review the Intlock Support Policy.

...


Anchor
install
install
Running the Install Wizard

  1. Open CardioLog-Analytics-2.0.XXX.XXX.exe
  2. Follow the Installation Wizard steps.
  3. Start CardioLog Scheduling Service and CardioLog Diagnostics Service
  4. Perform IISRESET Run the IISReset command on the CardioLog application server and check the status to confirm that IIS stopped and restarted.

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:

  1. Microsoft .NET Framework 3.5 Service Pack 1
  2. Microsoft Chart Controls for Microsoft .NET Framework 3.5
The download links can be found here.

Microsoft provides these downloads here

Note: If you are upgrading from versions lower than 1.19.158.0:

For Windows Server 2003 x64 with IIS 6.0, make sure IIS runs in 64in 64-bit mode.
For Windows Server 2008 x64 with IIS 7.0, make sure that the CardioLog application pool runs in 64-bit mode:

  1. Open IIS Manager > go to Application Pools > Right , and right-click CardioLogApplicationPool
  2. Select Advanced Settings >  from the contextual menu > Click Enable 32-bit Applications and select False
  3. Click OK > Right-click CardioLogApplicationPool and  again, and then select Recycle


Anchor
upgrading
upgrading
Upgrading the Tracking Agent

If you have customized the Tracking Agent code in your environment (i.e. customized search)environment, which is often done if you use a custom search feature on your site, please contact us before upgrading your product.

For SharePoint Online, see how to update the tracking code on all for SharePoint Online site collections.  

Anchor
tracking code
tracking code
Updating the tracking code:

  1. Backup the Java Script tracking code .
    by manually saving a copy in a separate folder. By default, the Java Script JavaScript tracking code is embedded within a common Java Script JavaScript file on all of your SharePoint WFEs -(Web Front Ends), which typically is one of the following locations relevant to your software versions: 


    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 tracking code is located at the end of the file, between these comments: "//Intlock tracking code start" , and "//Intlock tracking code end".
     

  2. Replace the Java Script tracking code with the one in CardioLog/found in your CardioLog application or SharePoint Marketing Suite > . In the navigation pane, go to Administration > System Configuration > Usage Tracking Code (select your SharePoint version).

    For "the CardioLog Analytics " SharePoint Feature only:
    Edit the Java Script tracking code - replace all the occurrences of http://[server name]:[port]/ (This will be the name of your CardioLog server name and port number) with /_layouts/.

Anchor
tracking agent
tracking agent
Updating Remote Tracking Agent Files:

If you have tracking agents which agent files that reside on your SharePoint WFEs (i.e. Usually located under "_layouts" when using if you use the " CardioLog Analytics " SharePoint Feature), update the CardioLog tracking agent files:

  1. Create a backup of the CardioLogAgent directory (, located on the all of your SharePoint WFEs), by saving the directory to a separate folder or disk.
  2. Copy the all installation files from [CardioLog Installation Directory]\CardioLogAgent to the existing CardioLogAgent directory, except the web.config file and customized custom files (if . If you have customizations in customized the Tracking Agent code in your environment, i.e. customized which is often done to enable custom search, please contact us before replacing the files).
  3. 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"/> 

  1. 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 hereSee Tracking Agent Configuration for more information):

  1. Delete the following key from the CardioLogAgent\web.config, located under the <appSettings> section -:

<add key="GetUserNameCustom" value=" function GetUsername() { __trace(&quot;GetUsername&quot;); var currentUsername = __readCookie(&quot;_userid&quot;); var currentUserId = __readCookie(&quot;spUserid&quot;); if (typeof(_spPageContextInfo) != &quot;undefined&quot;) { if (!currentUserId || currentUserId != _spPageContextInfo.userId) { currentUsername = null; __saveCookie(&quot;spUserid&quot;, _spPageContextInfo.userId, 1000, element.CookieDomain); } } var useridInput = this.document.getElementById(&quot;userid&quot;); if (useridInput &amp;&amp; useridInput.value != &quot;&quot;) { currentUsername = useridInput.value; } else if (currentUsername == null || currentUsername == &quot;&quot;) { if (typeof (getSPUserAccount) != &quot;undefined&quot;) { currentUsername = getSPUserAccount(); } else { currentUsername = &quot;Anonymous_&quot;+Math.random()*100000; } } __saveCookie(&quot;_userid&quot;, currentUsername, 1000, element.CookieDomain); __trace(&quot;GetUsername return: &quot;+currentUsername); return currentUsername; }"/>

  1. Edit the following key in the CardioLogAgent\web.config, located under the <appSettings> section - section:

<add key="UseSPAuth" value="true"/>