Installation Requirements
  • 16 Aug 2022
  • 2 Minutes to read
  • Dark
    Light

Installation Requirements

  • Dark
    Light

Upgrading?
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

Browsers not accounted for in the below chart will support the Portal, but not the Studio.


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



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 Server3.0 GHz 4-Core CPU16 GB RAM100 GB
Non-Production Server4-Core CPU8 GB RAM100 GB
Repository4-Core CPU8 GB RAM100 GB



Azure Specifications

Server TypeProcessingMemoryStorage
Production ServerD-Series D4s v3 | 3.0 GHz 4-Core vCPU16 GB RAM150 GB
Non-Production ServerD-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 ServerM4 Instance - m4.xlarge | 4-Core CPU16 GB RAM100 GB
Non-Production ServerM4 Instance - m4.xlarge | 4-Core CPU16 GB RAM50 GB
RepositoryM4 Instance - m4.xlarge | 4-Core CPU16 GB RAM50 GB



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.
Operating System.NET CoreHosting Type
Windows Server 2016 - 2019 or newer, 64-bit.NET Core 6.x x64Self-Hosting Considerations

.NET Core 6.x SDK*IIS Hosting Considerations

* = The .NET Core 6.0 SDK is only required for creating Internal and External Webservice References. It is not required to run Decisions.



Database Server and Configuration

Repositories must match the back-end of their connected Server
For example, an SQL 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 newer

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.

AzureAll supported

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

AWS-

DB level T3 is recommended for installation

PostgresPostgres 12 or 13-

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


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
MSSQL1433
Postgres5432

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.

PortUsage
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?