Jet Analytics Deployment Options
There are several ways to deploy Jet Analytics.
It is recommended to work with a technical consultant to determine the best deployment model for your organization.
Key components involved in a deployment
-
Jet Data Manager (JDM)
The Jet Data Manager is a .NET application that resides on a Windows Server. The Jet Data Manager (JDM) is the back-end development tool that is used to build the underlying data model.
-
SQL Server Databases
Jet Analytics leverages SQL Server to store and process relational data. These databases can be hosted on-premise or in the cloud via Azure SQL Database.
-
Analysis Services
Jet Analytics leverages Analysis Services to process and store cubes. Cubes are analytical databases that are optimized for read access and rich data analysis.
There are various different configurations available for Analysis Services:
SSAS Multidimensional
SSAS Tabular
- Can be used if using on-premise active directory
- Can be used if using Hybrid identity model
- Azure Analysis Services
- Cloud option
- Required if using Azure AD cloud-only identify model
Required if using on-premise active directory only
Each configuration has its own pros and cons, and the best choice will depend on various factors such as cost, in-house expertise, and existing infrastructure
Jet Hub (Optional Component)
-
Storing an easily accessible report repository
Single location to store Jet Reports and Dashboards
Simplifies sharing of reports with others within the organization, along with scheduling options
Allows for simplified administration of users and data source access
-
Jet Reports (Optional Component)
Jet Reports is a front-end client tool. This tool is used to consume data from one or more sources. This tool is usually installed on a client’s local machine and allows users to pull live data from Cubes/DWH to Excel.
-
SQL Server Management Studio
Access to SQL Server Management Studio is required during the installation and is useful during development.
The Jet Hub is an internal IIS website that is used to facilitate multiple features such as:
Methods to deploy Jet Analytics
- Method 1: On-Premise Deployment
-
Single Box – Deployment
In this configuration, we have a dedicated server for all the Jet components.
- Jet Data Manager
-
SQL Server
- Database Engine
- SSAS Multidimensional or SSAS Tabular
- SQL Server Integration Services
- Jet Hub
- Excel / Jet Reports
- SQL Server Management Studio
-
Scaled out – Deployment
In this configuration the components are scaled out among multiple servers.
SQL Box
-
SQL Server
- Database Engine
- SSAS Multidimensional or SSAS Tabular
- SQL Server Integration Services
-
App Server
- Jet Data Manager
- Excel / Jet Reports
- SQL Server Management Studio
-
SQL Server
- Method 2: Cloud Deployment
-
Azure VM to host the Jet Data Manager
- Excel / Jet Reports would also reside on Azure VM
- SQL Server Management Studio
- Azure SQL Database(s)
- Azure Analysis Services
- Microsoft Entra ID
-
Method 3: Hybrid Deployment
An organization can also opt for a hybrid deployment. In this setup, some components will reside on-premise, while others will be hosted in Azure.
-
On-Premise components
On-premise windows server for:
- Jet Data Manager
- Jet Hub
- Excel / Jet Reports
- SQL Server Management Studio
-
Azure Components
- Azure Analysis Services
- Azure SQL Databases
The on-premise deployment option is ideal for organizations with existing local resources. For instance, if an organization already has a SQL Server instance or servers that can be repurposed, this option is advantageous. It is also suitable for organizations not yet prepared to utilize Microsoft Azure.
Following are the components of On-Premise Deployment:
The cloud deployment option is ideal for organizations lacking local resources. For instance, if an organization prefers not to invest in local hardware or licensing, Microsoft Azure is a suitable choice
Following are the components of Cloud Deployment:
Following are the components of Hybrid Deployment: