Decisions Server Architecture

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. 

Basic Architecture 

In its essence, a Decisions Application is a Web Server/Web Service running on a Windows Server that runs on a SQL Database Backend. This application is then accessed by users via the Decisions Studio (for Designers/Admins) and Decisions Portal (for all User Accounts).

This in turn is presented to users via the Presentation Layer. This layer consists of the Decisions Studio (for Designers/Admins) and the Decisions Portal (for all User Accounts).

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 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. 

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.

Server Architecture Diagrams 

The following diagrams demonstrate the Server Architecture for a Single Server Self Hosted and IIS environment respectively.