Installation Guide
  • 07 Nov 2022
  • 6 Minutes to read
  • Dark

Installation Guide

  • Dark

After referring to the Installation Requirements, follow the walkthrough below to install Decisions on an Application Server or PC.

While this example installs a self-hosted instance with an MS SQL database connection, configuration for the other supported databases: AWS, Azure, and Postgres, is also provided.


  • Download and install the latest .NET 6 Runtime (x64).
  • Download and install the latest .NET 6 Hosting Bundle. 
    • With Windows Server 2022, users will still need to download and install the Hosting Bundle.
  • Download the desired v8.x version.
  • Connection to a supported database.

Selecting an Installation Type 

  1. Right-click the downloaded DecisionsServerInstaller.exe and select Run as administrator.
  2. Click INSTALL to begin.
  3. Review the terms, check the I accept the terms of the License Agreement box, then click Next.

  4. In the Select Installation Type window, choose the appropriate type.

    Refer to the chart below for further information on each installation type:
    Standard Server (Prod and Non-Prod)The most common Server Installation type.

    Installs an instance for both Production (live) and Non-Production (development) purposes. Allow other machines to access the server.
    Failover (HA) ServerInstalls an instance that only lives once triggered after the primary instance shuts down.

    Once installed, it will be available but will not run jobs or events on startup.
    Designer RepositoryInstalls an instance for storing entities and managing version builds and releases.

    It does not run live applications.
    Multi-Tenancy Server (Control)
    Installs a Control instance for hosting Tenants. Use this if utilizing multi-tenancy.
    Multi-Tenancy Server (Tenant)
    Installs a Tenant to an existing Control instance. Use this if utilizing multi-tenancy.

    Advanced Settings

  5. If desired, enable Show Advanced Settings, then click Next. If Advanced Settings is not enabled, Hosting Options will not be displayed, and the Hosting Type will default to Self-Hosted.

    Use Settings FileEnables a field to select a previously saved Settings file. 
    Change Destination Folder for InstallationDiverts installation from the default install folder, "C:\Program Files\Decisions".
    Pick Alternate SourceSelect an alternate installation file source via URL or file directory. 
    Show the Service SettingsCustomizes the Service account username and password. 
    Skip DB Connection Testing - Not RecommendedSkips the database connection test at the end of the installation wizard.

  6. In the Service Setting, select Local System Account for the Service Account. Click Next to proceed.

Database Setup

The app server and the Database Server need to be set to the same time zone.

MSSQL Connection


  • When installing on MSSQL, the maximum table limit for a user-defined type is 128 characters.


  1. Select MS SQL for Database Type.
  2. Under Connection Type, select Basic and enter the corresponding database server and name in DB Server and DB Database, respectively.

    If the database server does not exist, the platform installer will attempt to create it for MSSQL connections.
  3. Under Connection Settings, select MS SQL Server Security and enter the appropriate User ID and Password. Click Test to verify a successful database connection.

    Alternatively, MSSQL installations may use Windows Integrated Security for added security.
  4. Click Next to proceed.

AWS Connection


  • Create an AWS RDS Database for Microsoft SQL Server. Select either a SQL Server SE or SQL Server EE engine. Refer to Installation Requirements for specifications.
  • Launch an EC2 instance.
  • Configure the RDS Security Groups and/or VPC to allow SQL connections from the internal IP address of the EC2 application server. Add an inbound rule for the security group to allow MSSQL from EC2 instance's internal IP address.


  1. Select MS SQL for Database Type.
  2. Under Connection Type, select Basic. For DB Server, enter the endpoint address of the RDS instance. and DB Database respectively. For DB Database, enter the desired name e.g. "decisions".
  3. Under Connection Settings, select MS SQL Server Security. Enter the specified master Username and Password for the created RDS database in UserID and Password respectively.
  4. Click Next to proceed.

Azure Connection


SQL Specifications

DB level of at least DTU S4 or P1 should be used since the lower levels greatly restrict transactions per minute, causing timeouts for Decisions SQL queries, especially during installation. Some workloads may require higher throughput, which can be achieved with higher Premium Azure SQL tiers.

D-SeriesD4s v3
D4s v3
D4s v3
VCPU4 or 8 for Advanced Specifications4
Memory16 GB or 32 GB for Advanced Specifications16 GB
16 GB
HDD Storage150 GB100 GB100 GB


  1. Select Azure SQL for Database Type.
  2. Under Connection Type,  select Basic and then provide the Azure DB Server's Public Address and the database server's name in DB Server and DB Database, respectively.
  3. Under Connection Settings, select MS SQL Server Security, then provide the appropriate User ID and Password for the Azure Admin. Click Test to verify a successful connection.
  4. Click Next to proceed.

Postgres Connection


  • When installing on Postgres, the maximum table limit for a user-defined type is 64 characters.


  • Download Postgres v12 or 13. For v8.0 installs, keep the default UserID/Username aka "postgres" for Decisions to properly query Postgres. 
  • In Postgres, create a new database for Decisions. Upgrading from SQL is not supported, so a new database is required.


  1. Select PostgreSQL for Database Type.
  2. Under Connection Type, choose Basic and then enter "localhost" for the DB serverthe created Postgres database for DB Database, and "5432" for DB Port. This is the default port number for Postgres databases.
  3. Under Connection Settings, select PostgreSQL Server Security.
    For v8.0 installs, enter the default Postgres user credentials aka "postgres" and its respective password.
    For v8.1+ installs, enter either the default Postgres user credentials or any other created admin user in Postgres.

    Click Test to verify a successful connection.
  4. Click Next to proceed.

Hosting Options

  1. View the SQL Full-Text Warning, then click Next screen. 
  2. Select the appropriate Installer Hosting Option. This example selects Self Hosting. Click Next

Self Hosting 

  1. From the Portal Base Url window, select the desired Http/Https configuration with Certificate path and Password if applicable, and specify the desired Port that Decisions will install to.

    Afterward, leave Override Portal Base URL unchecked to allow the installer to create a Portal Base URL using "localhost" as the domain, with the input Port value, and either Http or Https as chosen. Otherwise, enable Override Portal Base URL to provide a custom value.

    This example keeps the default values ("http://localhost: 80"). Different ports must be opened via Windows Firewall first. Click Next.

IIS Hosting

  1. Provide the Portal Base URL then click Next. 
  2. Set a required Application (App) Pool or click Create New. Click Next.

Email Server, Encryption Keys, and File Storage

  1. Select an Outbound Email Server option. For local installs, select SMTP Direct Server. To specify a mail server address, select SMTP Server. Click Next once done.

  2. In the Encryption Keys window, the installer will detect any existing encryption keys on the connected database. A prior key and its data can be restored via the Restore Key File by entering its key value.

    For a fresh installation and if not wishing to restore any existing keys, select Next to continue. Even if keys are found, restoring is optional.

  3. Confirm the File Storage Path where Decisions will reside. The default path is C:\Program Files\Decisions\FileStorage. Click Next once done.
  4. Review any warnings in the System Requirements Check before clicking Next to proceed.

    Local PC installations will likely run into an OS warning due to production environments requiring Windows Server OS. This does not prevent successful installation, so installation may proceed if this occurs.
  5. The Review Install Options panel the installation's configuration. Check these settings for accuracy.

    To save these settings for future reference or recovery, click the Save Install Settings To File checkbox before clicking Next.
  6. Installation automatically begins. Click Show Details to see the installation's progress step-by-step.
  7. After installation completes, enable the Launch Decisions Portal checkbox, then select Finish.
  8. When Decisions launches, from the Login screen, click on the Decisions Software License Agreement link. 
  9. Review the Terms of Service, then click CLOSE. 
  10. Click the I agree to the terms and conditions... checkbox, then log in to the platform by providing the admin Username and Password, and clicking the LOGIN button. By default, these values are "" and "admin".

    These values can be altered during installation via the Change Default System Administrator, Username and Password setting found in the Advanced Settings table.

    In the event of the "license expiration" message, contact to request the appropriate license for the corresponding Server Type

For further information on Installation, visit the Decisions Forum.

Was this article helpful?