Page History
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 recommedations recommendations for optimal operation.
Contents
...
- Create a new EventCollector web application on your WFE. For the new web application, create a dedicated application pool. Set ASP.NET version to 24.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).
- Copy the files from the CardioLog server [CardioLog Installation Directory]\EventCollector to the new directory.
- 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 24.0. Set the authentication method of the web application to Windows Authentication (disable Anonymous access).
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.Edit the following keys in
thethe CardioLogAgent\web.config
filefile, located in
thethe <appSettings>
sectionsection and enter the NLB FQDN
-, where [domain name] is the NLB FQDN for the web applications.
Info icon false <add key="EventCollectorPath" value="http[s]://[domain name]/EventCollector/monitor.aspx" />
<add key="CardioLogAgentRoot" value="http[s]://[domain name]"/>
Where [domain name] is the NLB FQDN for the web applications.
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.
Info icon false <add key="EventCollectorPath" value="http[s]://[domain name]/_layouts/EventCollector/monitor.aspx" />
<add key="CardioLogAgentRoot" value="/_layouts"/
...
Where [domain name] is the SharePoint web application FQDN.
>
Edit the following keys in the Java Script tracking code
.
...
:
Info icon false 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.
...
| Anchor | ||||
|---|---|---|---|---|
|
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:
- Install the CardioLog Analytics Tracking Agent Feature on the backup farm as detailed here
- Verify that the CardioLog user account has read permissions to the SharePoint databases and a TEMPLATE folder on the backup farm.
- In case of a failover,
- Go to Administration > System Configuration > SharePoint Tree Adaptor > click on your SharePoint farm
- In the SharePoint Tree Adaptor dialog, fill out the following fields for the backup farm:
- 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 is 12 for MOSS 2007; 14 for SharePoint 2010; 15 for SharePoint 2013) - Click Apply, and then click Save.
SharePoint Adaptor System Configuration Preference Window
...
...
...
[SharePoint version]: MOSS2007, SP2010 or SP2013
...
...
[SharePoint web application root URL] - A '*' separated list of the monitored SharePoint web applications in the farm
[SharePoint TEMPLATE path] - 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; 15 for SharePoint 2013)
...