Deployment Scenarios
Cloud
Azure PaaS
Loome Publish can be deployed to Microsoft Azure. In this scenario the application runs on top of Azure PaaS infrastructure, making use of App Service and SQL DB. This scenario is the easiest to manage and scale.
In this scenario the application is deployed to Azure App Service and Azure SQL Database. Additional requirements require that an Azure app registration is configured for the application.
The portal can happily serve up to 100 concurrent connections on the lowest standard plans for both the App Service and SQL database, but can be scaled up to match your needs.
| Layer | Provider |
|---|---|
| Platform | Microsoft Azure |
| Web | Azure App Service |
| Database | Azure SQL Database |
| Identity Provider | Azure Active Directory Graph API |
| Directory Services | Azure Active Directory |
Additional considerations;
- If you are using source system syncing to on-premises SSRS and Power BI Report Servers, you will need to ensure you have configured an appropriate gateway technology. The simplest way to get up and running with this is to configure a Hybrid Connection on your Azure App Service, the entire process takes around 15 minutes.
- If you are making use of a custom domain, you will need to supply your own SSL certificate, we recommend using a public provider as this ensures the greatest browser compatibility.
- Additional configuration is required via Azure App Registrations to support Power BI embedding, this scenario supports both Power BI Pro and Power BI Premium embedding.
Click here for the Azure PaaS installation instructions
On-Premises
When deployed on-premises, we support 3 scenarios. These scenarios are entirely based on the identity provider used.
In all cases, the portal can serve numerous concurrent connections on a single server hosting IIS and SQL Server, we would recommend running 8GB of memory and a standard 4 core processor. Disk usage depends upon how much data is stored in the portal, generally speaking this will be quite small, but will be influenced by factors such as logging and usage retention periods.
On-premises with Azure Active Directory
In this scenario, we deploy Loome Publish on to your own windows O/S based environment. We make use of IIS and SQL Server to deliver the portal, but we still make use of Azure AD for authentication.
We recommend this scenario if you have access to Azure AD but want to make use of your own hardware investments. You can still embed other services from Azure (such as PowerBI.com), while passing through your users to these services.
| Layer | Provider |
|---|---|
| Platform | Windows Server 2012 R2 and above |
| Web | Internet IIS 8.5 and above |
| Database | SQL Server 2016 and above |
| Identity Provider | Azure Active Directory Graph API |
| Directory Services | Azure Active Directory |
Additional considerations;
- You will need to supply your own SSL certificate, we recommend using a public provider as this ensures the greatest browser compatibility.
- Additional configuration is required via Azure App Registrations to support Power BI embedding, this scenario supports both Power BI Pro and Power BI Premium embedding.
Click here for On-premises with Azure Active Directory installation instructions
On-premises with Loome Identity
In this scenario, we deploy Loome Publish on to your own windows O/S based environment. We make use of IIS and SQL Server to deliver the portal. We make use of Active Directory via our own Identity Provider software.
| Layer | Provider |
|---|---|
| Platform | Windows Server 2012 R2 and above |
| Web | Internet IIS 8.5 and above |
| Database | SQL Server 2016 and above |
| Identity Provider | Loome Identity |
| Directory Services | Active Directory |
Additional considerations;
- You will need to supply your own SSL certificate, we recommend using a public provider as this ensures the greatest browser compatibility.
- Additional configuration is required via Azure App Registrations to support Power BI embedding, this scenario only supports Power BI Premium embedding.
- Loome Identity is an ASP.NET based web application that uses IIS and SQL Server. You can host it on the same server as Loome Publish, and will need to supply an additional SSL certificate for its front end.
Click here for On-premises with Loome identity installation instructions
On-premises with Active Directory Federated Services
In this scenario, we deploy Loome Publish on to your own windows O/S based environment. We make use of IIS and SQL Server to deliver the portal. We make use of Active Directory via ADFS. This scenario is recommended where you already have identity services provided by an existing ADFS server.
| Layer | Provider |
|---|---|
| Platform | Windows Server 2012 R2 and above |
| Web | Internet IIS 8.5 and above |
| Database | SQL Server 2016 and above |
| Identity Provider | Active Directory Federated Services |
| Directory Services | Active Directory |
Additional considerations;
- You will need to supply your own SSL certificate, we recommend using a public provider as this ensures the greatest browser compatibility.
- Additional configuration is required via Azure App Registrations to support Power BI embedding, this scenario only supports Power BI Premium embedding.
Click here for On-premises with Active Directory Federated Services installation instructions
