Click here to download the latest documentation for Connect Hosting Requirements:
This document will provide very high-level recommendations for Connect’s hosting hardware requirements. Many of the recommended configurations and detailed technical specifications are dependent on the frequency and amount of expected traffic to the application. Additional information is also available during the project discovery process, during which a customized network diagram and security analysis can be generated.
Connect serves to integrate data between business applications. Connect runs as a standalone application. Your individual ERPs can thus be hosted externally or in a DMZ for example while Connect can be hosted internally within a LAN or behind a separate firewall, if desired.
Most Clients will configure the Connect to run behind some level of increased physical security. Figure 1 & Figure 2 show examples of how Connect is typically configured. Many Clients will install Connect on a server that also runs other connector/integrations, etc. It’s possible to implement Connect though on the same physical hardware instance(s) as your ERP (although this isn’t recommended for security purposes).
With regards to hardware / networking resource allocation, typically the needs of the Connect are roughly 25% of the ERP. In general, a very minimal instance of Windows Server (following the recommendations here: Connect Requirements).
\
Please see below for hardware recommendations noting that these recommendations are very high level with the traffic estimate data below as well as general experience with Connect driving the recommendations. This is by no means intended as a final set of recommendations, but is intended to begin the discussions.
\
*NOTE – items with asterisk (*) may have much lower HD space requirements based on actual usage.
Summary: Connect server (with the option to scale as needed).
Hard drive: Raid 5/6, at least 20GB for db and files* & 50GB+ OS.
CPU: Recommended 2 cores for VM or more.
· RAM: 4GB or more.
Recommended Environment: Windows Server 2016, SQL Server 2016, .NET Framework 4.72
\
Estimated Configuration / Setup Time
Infrastructure team: 2-4 hours
Security team: 2-4 hours
ERP team: 2-4 hours
Figure 1 - Simple Configuration with external Application and Internal Connect
Scenario 2 –Azure Hosted High Level Recommendations for Production Server Hardware – Cloud & Virtualized
*NOTE – items with asterisk (*) may have much lower HD space requirements based on actual usage.
Single App Service with Failover/Load Balanced options - [Cloud Hosting]
Summary: App Service with SQL server database (service model).
Hard Drive: Recommend SSD with at least 50GB for App Service.
CPU: At least 2 virtual cores.
· RAM: At least 6GB.
\
Infrastructure team: 4-6 hours
Security team: 2-4 hours
ERP team: 2-4 hours
\
In order to setup a Connect application you need to have the following requirements met:
Recommended Environment
Windows Server 2016+ // IIS 10+ // SQL Server 2016+ // .NET Framework 4.72
Supported Operating Systems
Windows 7 (Local development)
Windows 8 (Local development)
Windows 10 (Local development)
Windows Server 2008 / 2008 R2
Windows Server 2012 / 2012 R2
Windows Server 2016+
Linux (the application is a .Net Core application and can run in Linux environments.)
Supported Web Servers
Microsoft IIS 7.0, 7.5, 8.0, 8.5, 10.0+
Apache (the application is a .Net Core application and can run in an Apache web server.)
Supported Database Servers
Microsoft SQL Server 2008 / 2008 Express
Microsoft SQL Server 2012 / 2012 Express
Microsoft SQL Server 2014 / 2014 Express
Microsoft SQL Server 2016 / 2016 Express
Microsoft SQL Server 2017+ / 2017+ Express
Microsoft SQL Server Azure
MySQL (the application is a .Net Core application and can run in an Apache web server.)
Supported .NET Framework
4.0, 4.5, 4.6, 4.7+, .Net Core