Introduction
Welcome to Kepion! This overview explains everything you need to set up and know before you start installing Kepion to your environment. Carefully review the information below to ensure your installation goes smoothly.
Kepion environment
A typical Kepion deployment consists of three core components and two service accounts. You may install the components on a single machine or distribute them across multiple servers. If the service accounts (Kepion SI and SSAS SI) and their target machines span multiple servers, ensure they are all within the same Active Directory domain.
Components:
- Web Server: Hosts IIS and the Kepion web application.
- SQL Server: Hosts the relational SQL Server Database Engine.
- SSAS Server: Hosts the SQL Server Analysis Services (SSAS).
Service accounts:
- Kepion SI: A credential that determines the running context for the web server. A dedicated domain account is recommended.
- SSAS SI: A credential that determines the running context for the SSAS service.
Software requirements
You must have installed everything in the following list to set up and use Kepion. We recommend you first install all the required software and then perform a single reboot to register everything at once.
-
Relational SQL Server
- Microsoft SQL Server 2016 (or later 2017, 2019*, 2022)
- Edition: Enterprise, BI, Standard**
-
OLAP SSAS Server
- Microsoft SQL Server Analysis Services 2016 (or later 2017, 2019*, 2022)
- Edition: Enterprise, BI, Standard**
-
Web Server
- Microsoft IIS 7.0
- .NET Framework 4.8
- SQL Components based on the installed SQL version:
- Microsoft® SQL Server® Analysis Management Objects
- Microsoft® SQL Server® ADOMD.NET
- (If using SQL Server 2014-2019) Microsoft® SQL Server®2012 Native Client
- (If using SQL Server 2022) Microsoft OLE DB Driver for SQL Server
* If you are downloading SQL Server 2019, please also download the SQL Server 2019 Cumulative Update.
** Learn more about Kepion SQL Standard Support.
Memory requirements
To ensure optimal performance, you should review the memory configurations for the SQL and SSAS servers. By default, SQL and SSAS servers consume all available memory on a server. Total memory consumption can lead to unexpected behavior and poor performance.
The tables below provide recommendations for memory allocation in a typical environment. If each server is on its own machine, ensure that the host OS also has at least 2 GBof memory. We will cover this information in further detail during the setup process.
Production Environment
| Number of Users | Web Server | SQL Server | SSAS Server |
|---|---|---|---|
| Small < 10 | 2+ GB | 4+ GB | 4+ GB |
| Medium < 50 | 4+ GB | 6+ GB | 6+ GB |
| Large > 50 | 6+ GB | 8+ GB | 8+ GB |
Development Environment
| Number of Users | Web Server | SQL Server | SSAS Server |
|---|---|---|---|
| Small < 10 | 2+ GB | 3+ GB | 3+ GB |
Required permissions for setup
Ensure you have the necessary permissions to configure the three components across the various servers within the environment.
| Machine | Required Permission | Purpose |
|---|---|---|
| Web Server | Machine Administrator | To install and configure IIS. |
| SQL Server | sysadmin | To create the Kepion SI login and manage databases. |
| SSAS Server | SSAS Administrator | To grant Kepion SI as an administrator on SSAS. |
Tip: To configure the SQL and SSAS Server, view the Configure SQL and SSAS article.
Kepion SI consideration
The Kepion SI account determines the running context of the Kepion Web Server. Use the following guidance based on your environment type:
-
Production or development environment
- Use a dedicated domain account (recommended).
- Example: Domain\KepionSI
-
Sandbox, demo, or prototyping environment
- You may use your own machine credential, if you have SQL sysadmin access.
- Example: MachineName\UserName
SSAS SI consideration
The SSAS SI account determines the running context of the SSAS service. Choose the option that matches your environment setup:
-
Single-Server setup (SQL + SSAS on the same machine)
- You can typically keep the default SSAS service account.
- Example: NT SERVICE\MSOLAP$Instance
-
Multi-Server setup (SQL and SSAS on separate machines)
- You must use a domain account, as local/virtual accounts cannot authenticate to a remote SQL Server. Please request a dedicated domain account and configure SSAS to run under it.
- Example: Domain\SSASSI
Next steps
If your system meets all the requirements above, you can begin installing Kepion. We have split up the setup process into three parts:
- Part 1: Configure SQL and SSAS
- Part 2: Standard Installation (Recommended) OR Manual/Multitenant Installation
- Part 3: Set Database Permissions for SSAS SI
- (Recommended but optional) Go through the Setup Checklist to ensure proper installation
Note: All users will complete part 1 in the same way. However, part 2 can be completed the standard way (highly recommended for most users) OR manually for single-machine or multi-tenant setups.