Page History
To
| Table of Contents |
|---|
Hardware and Software Requirements
- CardioLog Analytics Enterprise Edition - it is required to install (a) CardioLog application on a dedicated server and (b) CardioLog database on a dedicated SQL Server instance***
- CardioLog Analytics Standard & Professional Editions - to ensure optimal operation,
...
- it is recommend to install (a) CardioLog application on a dedicated server and
...
- (b) CardioLog database on a dedicated SQL Server instance***
...
- The installer prerequisites can be found here
...
Inspect the following table to assure that your system meets the minimum hardware and software requirements:. These system requirements apply to daily operations of CardioLog Analytics and do not include any custom actions, such as product upgrades, migration tasks, importing IIS logs, executing scripts provided by Intlock etc. These type of actions may require additional resources. Please note that executing custom scripts against the CardioLog Analytics database is not supported.
| Free/Standard Edition | Professional Edition | Enterprise Edition | ||
Platform | 64-bit | 64-bit | 64-bit | ||
Operating System | Windows 2008/2012 Server or Windows 2008 R2/2012 R2 2016/2019/2022 Server Standard Edition (fully patched) | Windows 2008/2012 Server or | Dedicated Windows Server 2008/2012 or 2008 R2/2012 R2 2016/2019/2022 Server Standard Edition (fully patched)
| ||
Application Memory* | Minimum - 4 GB Recommended - 8 GB | Minimum** - 8 GBRecommended - 16 GB | Minimum** - 16 GBRecommended - 32 GB | ||
Processors* | 1xQUAD4 Cores | 2xQUAD | Minimum** - 2xQUAD Recommended - 4xQUAD | 8 Cores | 16 Cores |
SQL Server Edition | Microsoft SQL Server 20082014/2008 R22016/20122017/2014 2019/2022 Standard Edition (fully patched) | Microsoft SQL Server 20082014/2008 R22016/20122017/2014 2019/2022 Standard Edition (fully patched) | Microsoft SQL Server 20082014/2008 R22016/2012/2014 2017/2019/2022 Standard or Enterprise Edition (fully patched) | ||
SQL Instance Memory | 4 GB | Minimum** - 4 16 GB | Recommended Minimum** - 8 32 GB | Minimum 16 GB | |
SQL Server Processors | 1xQUAD4 Cores | 2xQUAD | Minimum** - 2xQUAD Recommended - 4xQUAD | 8 Cores | 16 Cores |
SQL Server Storage: |
|
|
| ||
| SQL System Disk (Mirrored) | 10 GB | 10 GB | 10 GB | ||
| SQL Page File Disk | 10 GB | 10 GB | 10 GB | ||
| SQL Database Disk | 20 GB per year | 60 GB per year A separate physical hard disk, formatted with 64K blocks, or RDM on storage LUNs | Maximum 600 GB per year A separate physical hard disk, formatted with 64K blocks, or RDM on storage LUNs | ||
| SQL Transaction Log Disk | 1 GB | 5 GB A separate physical hard disk, formatted with 64K blocks, or RDM on storage LUNs | Minimum** - 50 GB Recommended - 100 GB A separate physical hard disk, formatted with 64K blocks, or RDM on storage LUNs | ||
| SQL Temp Database Disk | 20% of Database Disk size | 20% of Database Disk size Recommended - A separate physical hard disk, preferably solid-state drive (SSD) | 20% of Database Disk size Recommended - A separate physical hard disk, preferably solid-state drive (SSD) | ||
| SQL Temp Database Log Disk | 1 GB | 5 GB | 5 GB | ||
| SQL RAID | RAID 10 or similar | RAID 10 or similar | RAID 10 or similar | ||
| Additional SQL Settings |
|
|
| ||
Additional Software & Services |
|
|
| ||
| Supported Browsers |
| Internet Explorer 9.0 or higher
|
|
| |
| Supported Authentication Methods |
|
|
|
* This refers to hardware allocated for the CardioLog application pool and services, not for the CardioLog SQL server
** Up to 1,000,000 SharePoint content items and/or 2,000,000 page views events per month.
*** The CardioLog application and database can be installed on-premise on physical servers or virtual machines, or hosted on Microsoft Azure virtual machines (which meet the above hardware and software requirements). When hosting CardioLog Analytics on Microsoft Azure virtual machines (IaaS) and tracking a SharePoint on-premise farm, a site-to-site VPN is required.
Note: Intlock supports merely products and/or solutions within third party vendor’s Mainstream Support policy, including but not limited to Windows (OS), Windows Server, SQL Server databases, browsers, etc. Intlock support for products and/or solutions under third party vendor’s Extended Support policy, might requires further efforts based on professional services, which will be priced separately by Intlock upon Client’s request. Intlock at its sole discretion might not provide any support services whatsoever to any third party vendor products and/or solutions that are not being included under third party vendors' Mainstream or Extended Support policies.
The amount of resources needed for the and the time it takes for the CardioLog Scheduling Service nightly processing depends jobs to complete depend on -
- Number of content items (websitesWebsite , lists, list items, documents etc.)
- Content size
- Number of events (traffic)
- Number of scheduled reports
- The timeframe for the reports (yearly reports for 365 days demand more resources then reports for 30 days)
- The number of events (traffic) coming in from the portal at the time of report processingwidgets per report
Importing large websites that consist of millions of items, user information for hundreds of thousands users, and generating hundreds of daily reports will consume most of the CardioLog application server resources. The import process for large environments may take a few hours up to a few weeks, depending on the import method (direct database access vs. API calls), import mode (full vs. changes only) and the environment size.
The more resources allocated, the better.
| Anchor | ||||
|---|---|---|---|---|
|
...