Page History

...

[domain name] - the NLB FQDN for the web application. When deploying the CardioLog Analytics SharePoint feature for usage tracking, there is no need to edit these keys (the default value is "/_layouts").
[SharePoint version] - MOSS2007, SP2010 or  SP2013

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

...

1. Install the CardioLog Analytics Tracking Agent Feature as detailed here OR add  manually add the Tracking Agent JavaScript Code (located in the [CardioLog Installation Folder]\CardioLogAgent\sp_js_tracking_code.txt file) to each SharePoint WFE. The tracking code should be placed in a SharePoint common .js  js file.
   
   Edit the [ca.src] and [script.src] values (copy the values from your current code) -:
    
   [ca.src]:
   ca.src='http://[server name]:[port]/CardioLogAgent/ca.aspx?_random='+Math.random();
   [script.src]:
   tt.src='http://[server name]:[port]/CardioLogAgent/AgentEmbed.aspx?env=[SharePoint version]&r='+Math.random()*100000;
   http://[server name]:[port]/: 'http://cardiolog server /server name:port/'
   [SharePoint version]: MOSS2007, SP2010 or SP2013
   
   
2. Verify that the CardioLog user account has read permissions to the SharePoint databases and the TEMPLATE folder on the backup farm.
3. Keep an alternate Web.config file for the CardioLog [SP20XXTree] web application (where XX -  is 07 for MOSS 2007, ; 10 for SharePoint 2010, ; 13 for SharePoint 2013), which includes the proper configuration settings for connecting to the SharePoint backup farm servers: 
              
   • Edit the SharePoint database connection string in the web.config file accordingly:
     
     <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] - edit the SharePoint config database name
     
              
   • [SharePoint Database Server Name] - edit the SharePoint database server name
     
     
   • Edit the following keys in the web.config file:
     
     <add key="includedWebApps" value="[SharePoint web application root URL]" /
   ><add
   • ><add key="SharePointTemplatePath" value="[SharePoint TEMPLATE path]" />

              
              [SharePoint web application root URL] - a A '*' separated list of the monitored SharePoint web applications in the farm
              [SharePoint TEMPLATE path] - edit Edit the SharePoint TEMPLATE folder path: 
              \\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 and ; 15 for SharePoint 2013)

4. Test the configuration of the alternate Web.config file by dropping the file to the [SP20XXTree] directory and browsing to http:// [CardioLog server name]/[SP20XXTree]/default.aspx. Verify  and verify that you get an XML response displaying the portal tree structure.
5. In case of a failover, drop the alternate Web.config file into the [SP20XXTree] directory.
   [SP20XXTree] -  SP2007Tree for MOSS 2007, SP2010Tree for SharePoint 2010 or SP2013Tree for  Where XX is 12 for MOSS 2007; 14 for SharePoint 2010; 15 for SharePoint 2013