- 07 Jul 2022
- 2 Minutes to read
- Updated on 07 Jul 2022
- 2 Minutes to read
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
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
|Production Server||3.0 GHz 4-Core CPU||16 GB RAM||100 GB|
|Non-Production Server||4-Core CPU||8 GB RAM||100 GB|
|Repository||4-Core CPU||8 GB RAM||100 GB|
|Production Server||D-Series D4s v3 | 3.0 GHz 4-Core vCPU||16 GB RAM||150 GB|
|Non-Production Server||D-Series D4s v3 | 4-Core vCPU||16 GB RAM||150 GB|
|Repository||D-Series D4s v3 | 4-Core vCPU||16 GB RAM||100 GB|
Amazon Web Services (AWS) Specifications
|Production Server||M4 Instance - m4.xlarge | 4-Core CPU||16 GB RAM||100 GB|
|Non-Production Server||M4 Instance - m4.xlarge | 4-Core CPU||16 GB RAM||50 GB|
|Repository||M4 Instance - m4.xlarge | 4-Core CPU||16 GB RAM||50 GB|
|Operating System||.NET Core||Hosting Type|
|Windows Server 2016 - 2019 or newer, 64-bit||.NET Core 6.0 x64||Self-Hosting Considerations|
|*.NET Core 6.0 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
|Database Server Type||Server Version Required||Additional Information|
|SQL||SQL 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.
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
|Postgres||Postgres 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 Type||SQL Port|
To modify the SQL port number, update the connection string syntax (myPortNumber) as follows:
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.
|80||Assigned for HTTP connections|
|443||Assigned for HTTPS connections|