Installation Requirements
  • 09 Jul 2024
  • 3 Minutes to read
  • Dark

Installation Requirements

  • Dark

Article summary

Please select from the following articles to review important considerations:

The Application Server specifications outlined in this article are based on these server types:

  • Production Server: a live environment where created processes are leveraged by end-users (customers) 
  • Non-Production Server: non-customer facing environment used for testing and development to assess production readiness
  • Repository Server: non-customer-facing environment used to help maintain version control and migrate projects between servers

Browser Compatibility

ChromeChromium Edge icon Edgefirefox icon Firefoxsafari icon SafariIE 11 icon Internet Explorer

Hardware Specifications

Consult expertise ahead of server deployment. The deploying organizations' Senior Database Administrator (DBA) should be involved in recommending resources.

Advanced specifications consider the following circumstances:

  • Data-heavy environments
  • Organizations with long procurement/change request cycles
Server TypeProcessingMemoryStorage
Production 3.0 GHz 4-Core CPU16 GB RAM100 GB
Non-Production 4-Core CPU8 GB RAM100 GB
Repository4-Core CPU8 GB RAM100 GB
Enterprise 8-Core CPU32 GB AMUse case dependent

Azure Specifications

Server TypeProcessingMemoryStorage
Production D-Series D4s v3 | 3.0 GHz 4-Core vCPU16 GB RAM150 GB
Non-Production D-Series D4s v3 | 4-Core vCPU16 GB RAM150 GB
RepositoryD-Series D4s v3 | 4-Core vCPU16 GB RAM100 GB

Amazon Web Services (AWS) Specifications

Server TypeProcessingMemoryStorage
Production t3.xlarge | 4-Core CPU16 GB RAM100 GB
Non-Production t3.xlarge | 4-Core CPU16 GB RAM50 GB
Repositoryt3.xlarge | 4-Core CPU16 GB RAM50 GB

Minimum Cores and Memory:
For optimal performance of a Decisions server, it is advisable to configure the server with at least 4 cores and 16 GB of RAM.

Software Requirements

SSL Certificates
While not required for a successful install, SSL certificates are recommended for enhanced HTTP2 support and product performance. Self-signed certificates are accepted.

.NET Versions for Decisions: Since Decisions is built using .NET, it is mandatory to install the required .NET applications before installing Decisions.

.NET Core SDK: The application also utilizes the .NET Core 6.0 SDK to create Internal and External Web Service References, but it is important to note that this SDK is not necessary for running Decisions.

Database Server and Configuration

Repositories must match the back end of their connected Server
For example, an Application Server wishing to use a Repository must connect to one that also uses SQL. See Installing and Configuring Designer Repository for more information.
Database Server TypeServer Version RequiredAdditional Information
SQLSQL Server 2012 SPI Standard or newerSupported by v8.0 to v8.11.
SQL Server 2016 SPI Standard or newerSupported by v8.12 to v8.19.
SQL Server 2017 SPI Standard or newerRequired for v8.20 and above. 


  • All versions and patches of SQL Server 2019 are compatible with Decisions. This includes both Standard, Enterprise, and Express editions.
  • Standard installation with default collation (SQL_Latin1_General_CP1_CI_AS).
  • Instances may be named; the Instance Name does not need to remain its default value.
  • SQL Express should ONLY be used for Dev. Environment as it has a 10 GB limit.
AzureAll supported

DB level of at least S3 or P1 is recommended to prevent timeouts for Decisions SQL queries, especially during installation.


DB level T3 is recommended for installation.

PostgresPostgreSQL 12 or 13It is supported by all Decisions versions.
PostgreSQL 14 or 15Supported by v8.10 and above.
PostgreSQL 16Supported in v8.20 and above.

It is recommended that Microsoft's standard SQL maintenance plan is utilized for database maintenance.

DB Servers installation for Prod vs. Non-Prod environment
  • It is acceptable to install the DB servers and Decisions on the same machine only for development and testing purposes.
  • For the Production environment, it is strongly recommended to install the Decisions and DB servers on separate machines. It is advised to allocate at least 4 cores and 16 GB of RAM for the DB server.

Network Ports and Protocols

Depending on the chosen database server, Decisions uses the following default SQL port numbers to connect to the database server.

Database Server TypeSQL Port
MS SQL1433

To modify the SQL port number, update the connection string syntax (myPortNumber) as follows:
Server=myServerName,myPortNumber;Database=myDataBase;User Id=myUsername;Password=myPassword;

When installing locally, Decisions attempts to occupy the following default ports for users to host its service.
These port numbers may be configured during and after installation.

80Assigned for HTTP connections
443Assigned for HTTPS connections

It is recommended to run Decisions via HTTPS for added security. Refer to the Securing a Decisions Installation for additional security methods.

Was this article helpful?