System Redundancy

One of the benefits of using CardioLog Analytics on-premise is a complete ownership of your own data, on your own servers, which allows you to control both privacy and security. This also means that redundancy for the CardioLog server is the customer's responsibility to maintain. This article contains several recommendations for optimal operation.

Contents

• How to Configure NLB for Usage Data Collection
• How to Install the CardioLog Data Collection Web Applications on a WFE
• How to Configure CardioLog in the Event of a SharePoint Farm Failover

How to Configure NLB for Usage Data Collection

For portals with 5 million events or more per month, we recommend using network load balancing (NLB) for usage data collection. Data collection is still handled by the EventCollector and CardioLogAgent web applications, but multiple instances of these web applications can work in parallel. Each instance will simultaneously write its own data into the CardioLog database.

The architecture for NLB should be as follows:

1. Main server hosting a full CardioLog installation.
2. At least one additional web front end (WFE) that hosts the EventCollector and CardioLogAgent web applications.

Note: You can use the SharePoint WFEs or dedicated servers to host the EventCollector and CardioLogAgent web applications. When deploying the CardioLog Analytics SharePoint feature for usage tracking, the CardioLogAgent web application is automatically installed on your SharePoint WFEs under each SharePoint web application _layouts folder. You can install the EventCollector web application in the same location.

How to Install the CardioLog Data Collection Web Applications on a Web Front End (WFE)

1. Create a new EventCollector web application on your WFE. For the new web application, create a dedicated application pool. Set ASP.NET version to 4.0 and grant the application pool account the "db_owner" role on the CardioLog database. Set the web application authentication method to Anonymous access (disable Windows Authentication).
2. Copy the files from the CardioLog server [CardioLog Installation Directory]\EventCollector to the new directory.
3. Create a new CardioLogAgent web application on the WFE. For the new web application, create a dedicated application pool and set ASP.NET version to 4.0. Set the authentication method of the web application to Windows Authentication (disable Anonymous access).

4. Copy the files from the CardioLog server [CardioLog Installation Directory]\CardioLogAgent to the new directory.
   Note: When deploying the CardioLog Analytics SharePoint feature for usage tracking, there is no need to create a new CardioLogAgent web application.
   

5. Edit the following keys in the CardioLogAgent\web.config file, located in the <appSettings> section and enter the NLB FQDN, where [domain name] is the NLB FQDN for the web applications.

   <add key="EventCollectorPath" value="http[s]://[domain name]/EventCollector/monitor.aspx" />
   <add key="CardioLogAgentRoot" value="http[s]://[domain name]"/> 

   
   Note: When the EventCollector and CardioLogAgent web applications are installed on your SharePoint WFEs under each SharePoint web application _layouts folder, edit the following keys in the CardioLogAgent\web.config file, located in the <appSettings> section, where [domain name] is the SharePoint web application FQDN.

   <add key="EventCollectorPath" value="http[s]://[domain name]/_layouts/EventCollector/monitor.aspx" />
    <add key="CardioLogAgentRoot" value="/_layouts"/>

6. Edit the following keys in the Java Script tracking code:

   cad.src = 'http[s]://[domain name]/CardioLogAgent/getCAData.aspx?r='+Math.random();
   ca.src = 'http[s]://[domain name]/CardioLogAgent/ca.aspx?u='+document.location.href;
   tt.src = 'http[s]://[domain name]/CardioLogAgent/AgentEmbed.aspx?env=[SharePoint version]';

   
   Note: When deploying the CardioLog Analytics SharePoint feature for usage tracking, there is no need to edit these keys (the default value is "/_layouts").
   
   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
   
   The code is located at the end of the file, between these comments: //Intlock tracking code start, and //Intlock tracking code end
   
   [domain name] - the NLB FQDN for the web application.
   [SharePoint version] - MOSS2007, SP2010 or  SP2013

An Active-Active configuration for the entire CardioLog solution is not supported.

An Active-Passive configuration for the entire CardioLog solution is available at an additional cost (the dormant server requires a production license).

How to Configure CardioLog in the Event of a SharePoint Farm Failover

Assuming that the SharePoint backup farm has an identical, redundant set of portal URLs to the live farm, follow this procedure to prepare for a SharePoint farm failover: