Page History
It is the customer's responsibility to maintain redundancy for the CardioLog server. To ensure optimal operation, follow the following procedures:
Contents
- How to configure NLB for usage data collection
- How to install Install the CardioLog data collection web applications Data Collection Web Applications on a WFE
- How to configure Configure CardioLog in the event Event of a SharePoint farm Farm Failover
| Anchor | ||||
|---|---|---|---|---|
|
For large portals, those with over 5 million events per month, Intlock recommends using NLB for usage data collection.
...
- Main server hosting a full CardioLog installation.
- Additional WFE/s which host 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 already installed on your SharePoint WFEs under each SharePoint web application "_layouts" folder. You can install the EventCollector web application in the same location.
| Anchor | ||||
|---|---|---|---|---|
|
...
Install the CardioLog
...
Data Collection Web Applications on a WFE
- Create a new EventCollector web application on the WFE. For the new web application, create a dedicated application pool, set ASP.NET version to 2.0 and grant the application pool account the "db_owner" role on the CardioLog database. Set the authentication method of the web application 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 2.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 the CardioLogAgent\web.config file, located in the <appSettings> section and enter the NLB FQDN -
...
An Active-Passive configuration for the entire CardioLog solution is available at an additional cost (the dormant server requires a production license).
| Anchor | ||||
|---|---|---|---|---|
|
...
Configure CardioLog in the
...
Event of a SharePoint
...
Farm Failover
Assuming that the SharePoint backup farm has an identical set of portal URLs to the live farm, follow this procedure to prepare for a SharePoint farm failoverfailover:
- 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 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. Example: "SharePoint_Config"
- Authentication - database authentication type (windows integrated or SQL authentication).
- SharePoint TEMPLATE Directory - this is the full path for the SharePoint 'TEMPLATE' directory. Example: "\\<sharepoint server name>\C$\Program Files\Common Files\Microsoft Shared\Web Server Extensions\XX\TEMPLATE\" (XX - 12 for MOSS 2007, 14 for SharePoint 2010, 15 for SharePoint 2013) - Click Apply, then click Save.
In versions lower than 2.0.8.0,
...