System requirements for Jitterbit App Builder
Introduction
An App Builder instance consists of a web server and a database server. You can run these on any of the following:
-
On-premises physical or virtualized hosts, paid for and managed by you.
-
Cloud instances offered by Amazon Web Services (AWS), Google Cloud Platform (GCP), and Microsoft Azure, subscribed for and managed by you.
-
Jitterbit hosting, commissioned and managed on your behalf by Jitterbit and its partners.
Important
The infrastructure for these servers should meet or exceed the specifications on this page, which are general recommendations to guide your initial planning. Your specific requirements will ultimately depend on the unique demands of your environment. This includes factors such as the number of concurrent users, the complexity and number of your App Builder apps, and how much data is stored and transferred. For optimal performance and resource allocation tailored to your operational context, you should consult with your systems architecture engineers to determine the most appropriate hardware specifications.
The specifications are organized into the following distinct system profiles, each representing a typical environment or usage pattern:
-
Development: A development system, for up to 10 developers and the same number of app users or testers.
-
QA: A QA system, for up to 10 app users or testers.
-
Production: A production system, for up to 500 app users.
-
Production — high concurrency (HC): As for production, but able to support more than 500 concurrent app users.
-
Production — high concurrency, high availability (HCHA): As for production (HC), but also providing high availability (HA), defined as 99.99% uptime. (In this configuration, the web server is scaled according to the load.)
The hosts' operating systems must be either Microsoft Windows Server, or Linux (Debian or Red Hat), and the databases must be one of Microsoft SQL Server, MySQL, or PostgreSQL.
Recommendations
-
Run servers on separate hosts.
-
Don't run other applications on server hosts.
-
Use UTC timezones on all hosts, and keep them synchronized.
Hardware
For all hosts, the web server host's architecture must be x64. (The database server host can be any architecture.)
x64 (On-premises)
The following table shows the minimum required on-prem hardware requirements for App Builder's web and database server hosts:
| System profile | Web server | Database server | | | | | ||||
|---|---|---|---|---|---|---|---|---|---|---|
| Disk size (GB) | Memory (GB) | CPU cores | Disk size (GB) | Memory (GB) | CPU cores | |||||
| Development | 150 | 16 | 4 | 150 | 16 | 4 | ||||
| Production | 150 | 16 | 4 | 150 | 16 | 4 | ||||
Cloud
The following tables show the minimum required cloud provider instance classes for App Builder's web and database server hosts on each system profile:
| System profile | Web server | Database server | | | | | | | | | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Disk size (GB) | Instance class | | | Disk size (GB) | Disk performance (IOPS) | Throughput (MB/s) | Instance class | | | |||||||||
| Amazon | Azure | Amazon | Azure | |||||||||||||||
| Development | 150 | t3.medium | B2s | e2-medium | 50 | 3000 | 150 | db.t3.medium | B2s | e2-medium | ||||||||
| QA | 150 | t3.large | B2ms | e2-standard-2 | 200 | 4000 | 250 | db.t3.large | D2s v3 | n1-standard-2 | ||||||||
| Production | 150 | m5.large | D2s v3 | e2-standard-2 | 200 | 4000 | 250 | db.m5.large | D2 v3 | n1-standard-2 | ||||||||
| Production (HC) | 200 | m5.xlarge | D4s v3 | n2-standard-4 | 200 | 4000 | 250 | db.m5.xlarge | D4 v3 | n1-standard-4 | ||||||||
| Production (HCHA) | 200 | m5.xlarge | D4s v3 | n2-standard-4 | 200 | 4000 | 250 | db.m5.xlarge | D4 v3 | n1-standard-4 | ||||||||
For the production (HCHA) profile, the database server should use a cache with the following specifications:
| Disk size (GB) | Amazon | Azure | |
|---|---|---|---|
| 32-1000 | cache.t3.micro (Redis) | Azure Cache for Redis | Cloud Memorystore for Redis |
For all profiles, the servers indicated should use the following cloud provider features:
| Feature | Web server | Database server | Amazon | Azure | |
|---|---|---|---|---|---|
| Auto-scaling | Auto Scaling | Virtual Machine Scale Sets | Managed Instance Groups | ||
| Load balancing | Application Load Balancer | Application Gateway | Cloud Load Balancing | ||
| SSD-based storage | gp3 | Standard SSD | Balanced Persistent Disk (pd-balanced) |
||
| Storage encryption | Server-size encryption | Service encryption | Disk encryption | ||
| Backup | AWS Backup | Automated backups in Azure SQL Database | Cloud SQL backups |
Software
Supported operating systems
You can run App Builder's web server or database server on any of the following supported operating systems:
| Operating system | Version | Additional required software | Additional optional software |
|---|---|---|---|
| Microsoft Windows Server1 | 2016 R2 (x64) 2019 2019 Datacenter 2022 2022 Datacenter 2025 |
Internet Information Services (IIS)2 (8.5 or later) ASP.NET Core Runtime Hosting Bundle (8.0) |
Crystal Reports (SP21 to SP32) SQL Server Management Studio |
| Linux | Debian 11 Red Hat 8 |
.NET (8.0) OpenSSL (3.0+) GNU C library (2.36+) zlib compression library (1.2+) libicu International Components for Unicode libraries (72.1+) |
|
| Red Hat 8 | Kerberos GSSAPI |
Notes
1 Windows Server Core is not supported.
2 You must enable the following Internet Information Services (IIS) server roles:
| Web Server (IIS) | Web Server | Common HTTP Features | (Important: Do not select WebDAV publishing.) |
| Health and Diagnostics | HTTP Logging | ||
| Performance | (Select all) | ||
| Security | Request Filtering | ||
| Application Development | Application Initialization | ||
| WebSocket Protocol |
Windows antivirus
Windows antivirus (AV) software can affect the operation and performance of App Builder. To avoid this without compromising server security, you should configure your AV solution to ignore the following directories and files:
| Description | Default |
|---|---|
| App Builder installation folder | C:\inetpub\wwwroot |
| ASP Net Core Module file | %SystemRoot%\system32\inetsrv\aspnetcore.dll |
| .NET framework |
Windows Defender
If you are using Windows' built-in Windows Defender as your only AV solution, the only additional exclusion you should add manually is the C:\inetpub\wwwroot\vinyl.exe file. All other AV exclusions are configured when selecting the IIS Web Server role. To read more, see Microsoft Windows Defender exclusions for web applications and Antivirus Exclusion List for ASP.NET applications hosted on IIS (Microsoft IIS Support Blog).
Supported database servers
| Database | Edition | Versions | Features |
|---|---|---|---|
| Microsoft SQL Server1 | Standard (x64) | 2016 2017 2019 2022 |
Database Engine services. Default and named instances. Default collation sequence ( SQL_Latin1_General_CP1_CI_AS).Mixed mode authentication. |
| Enterprise (x64) | |||
| Amazon RDS for Microsoft SQL Server | Web2 | ||
| Standard | |||
| Enterprise | |||
| MySQL | Enterprise | 8.0 or later | Default collation sequence (utf8mb4_0900_ai_ci). |
| PostgreSQL | Stable | 14 or later |
Notes
1 SQL Server LocalDB is not supported.
2 Recommended minimum for all systems.
Network
The host network must allow two-way traffic on the following ports:
| Port | Description |
|---|---|
| 80 | HTTP |
| 443 | HTTPS |
The database server must be accessible from the web server.