Decisions Server Architecture
- 25 Jan 2022
- 1 Minute to read
- Print
- DarkLight
This documentation version is deprecated, please click here for the latest version.
Decisions Server Architecture
- Updated on 25 Jan 2022
- 1 Minute to read
- Print
- DarkLight
Article summary
Did you find this summary helpful?
Thank you for your feedback
Overview
The following document provides a brief look at and explains the Server Architecture of a Single Server Decisions installation and how each part works with the other to provide users access to the additional functions and Integrations.
v.7x instances do NOT CURRENTLY SUPPORT Multi-Tenant (MT)
v8.x instances expect to support MT. Please plan upgrades accordingly or contact Support for assistance.
Note on Document
Note that the following document discusses the Server Architecture for a Single Server v.7 installation.
Version 7.x .NET Architecture Change:
Versions 7.0.1 - 7.1 require .NET Core 3.1
Versions 7.2 - 7.9 require .NET 5
Versions 7.10+ require .NET 6
Versions 7.0.1 - 7.1 require .NET Core 3.1
Versions 7.2 - 7.9 require .NET 5
Versions 7.10+ require .NET 6
Impact on Upgrades:
- ALL custom libraries will need to be recompiled for the new .NET architecture.
- Custom assemblies will need to be re-written.
- Modules may require reinstallation or design refactoring.
Basic Architecture
In its essence, a Decisions Application is a Web Servers/Web Services that runs on a Windows Server on a SQL Database Backend.
Additional Information on SQL Backends
Decisions 7.x can operate off of one of the following SQL-based Backends.
- Microsoft SQL Server
- Azure
- AWS
This in turn is presented to users via the Presentation Layer. This layer consists of the Decisions Studio (for Designers/Admins), Decisions Portal (for all User Accounts), and the Native Mobile Application.
Utilization of the Presentation Layer provides users the ability to utilize the Application Layer (Decisions Platform). The Application Layer allows users to leverage the power of tools such as the SDK, Reporting Engine, Flow Engine, etc...
This Architecture then works in conjunction with a local Windows File Storage location that is determined by Microsoft SQL Server Management Studio. This location allows users the ability to read and write files from the Local System.
Note on Load Balancing
If the Decisions installation is installed on a Server Cluster instead of a Single Server, a Load Balancer may be used to evenly distribute data across servers. For more information, see About Load Balancing.
In addition, by accessing the Application, users may utilize Decisions’ Service Layer (API Management, Database Connectors, REST Integration, etc…) which provides the ability to interact with additional External Systems, Databases, and Interfaces.
Additional Information
The following diagram demonstrates the overarching Architecture of a v.7 Decisions installation.
Additional Server Architecture Diagrams
The following diagrams demonstrate the Server Architecture for a Single Server Self Hosted and IIS environment respectively.
Was this article helpful?
