Page History
...
- Application server hosting the CardioLog Analytics application.
- Database server hosting the CardioLog database.
- Two or more web servers that host the Usage Data Collection components (EventCollector and CardioLogAgent web applications).
Note: You can use the existing SharePoint WFEs or dedicated servers to host the Usage Data Collection components. By default, 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 assuming the SharePoint WFEs have sufficient resources to handle the additional web requests. - SharePoint WFEs hosting the CardioLog Analytics JavaScript tracking code. By default, when deploying the CardioLog Analytics SharePoint feature for usage tracking, the JavaScript tracking code is hosted in the CardioLogAgent web application which is automatically installed on your SharePoint WFEs under each SharePoint web application _layouts folder.
CardioLog Analytics On-Premise High Availability Architecture - with usage data collection components installed on the SharePoint WFEs
CardioLog Analytics On-Premise High Availability Architecture - with usage data collection components installed on dedicated web servers
...
| CardioLog Standard Edition | CardioLog Professional Edition | CardioLog Enterprise Edition |
Platform | 64-bit | 64-bit | 64-bit |
Operating System | Windows 2008 R2/ 2012/2012 R2/2016/2019/2022 Server Standard Edition (fully patched) | Windows 2008 R2/ 2012/2012 R2/2016/2019/2022 Server Standard Edition (fully patched) | Windows 2008 R2/ 2012/2012 R2/2016/2019/2022 Server Standard Edition (fully patched) |
Application Memory | 4 GB | 8 GB | Minimum* - 8 GB Recommended - 12 GB |
Processors | 4 Cores | 4 Cores | 4 Cores |
Additional Software & Services |
|
|
|
...
Disaster Recovery for the CardioLog Analytics Application
An Active-Active DR configuration for the entire CardioLog solution, including the reporting user interface, is not supported.
An Active-Passive DR configuration for the entire CardioLog solution is available at an additional cost (the dormant server requires a production license).
...
Assuming the SharePoint backup farm has an identical, redundant set of portal URLs to identical content to the live farm (identical content URLs and SharePoint IDs) and CardioLog is importing the tree structure directly from the SharePoint database (supported on SharePoint 2013 or lower), follow this procedure to prepare for a SharePoint farm 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; 16 for SharePoint 2016) - Click Apply, and then click Save.
SharePoint Adaptor System Configuration Preference Window