<< Click to Display Table of Contents >> System Requirements for Production and Test Environments |
Overview
Automation Server executes your processes and delivers them to the desktops and mobiles of every business user.
Automation Server supports setup in a .NET platform.
For introductory information about Automation Server, refer to Automation Server.
Requirements
The following requirements are narrowed down by database server, Bizagi server, and other infrastructure assets.
Database server
For a high availability system architecture, at least two nodes for the database are recommended.
Each node should consider the following requirements:
REQUIREMENTS FOR EACH NODE FOR THE DATABASE SERVER |
|||
---|---|---|---|
|
Component |
Production Environment |
Test Environment |
HARDWARE |
RAM |
•16 GB minimum. •It is strongly recommended to consider the most RAM you can use to provide the best performance. |
8 GB minimum. |
Hard Disk |
•Two disks in RAID 1 (optional). •Each disk having 80 GB minimum. •It is strongly recommended to use high-speed disk drives. |
40 GB minimum. |
|
Processor |
•64-bit. •4 cores minimum. •3GHz or higher. |
•64-bit. •2 cores minimum. •2.4GHz or higher. |
|
Additional recommendations |
•Two NIC - Dual port 1GB. •Redundant Power Supply (optional, recommended). |
||
SOFTWARE |
Database Engine |
Standard or higher editions of: •Microsoft SQL Server 2019 (Ensure you meet the SQL Server system requirements). •Microsoft SQL Server 2017 •Microsoft SQL Server 2016 SP1 or higher •Microsoft SQL Server 2014 •Microsoft SQL Server 2012 •Oracle Database 19c •Oracle Database 12c •Oracle Database 11g R2 |
Standard or higher editions of: •Microsoft SQL Server 2019 (Ensure you meet the SQL Server system requirements). •Microsoft SQL Server 2017 •Microsoft SQL Server 2016 SP1 or higher •Microsoft SQL Server 2014 •Microsoft SQL Server 2012 •Oracle Database 19c •Oracle Database 12c •Oracle Database 11g R2 |
Bizagi server
For a high availability system architecture, at least two nodes for a Bizagi cluster are recommended.
Each node should consider the following requirements:
REQUIREMENTS FOR EACH NODE FOR THE BIZAGI SERVER |
|||
---|---|---|---|
|
Component |
Production Environment |
Test Environment |
HARDWARE |
RAM |
16 GB minimum. |
8 GB minimum. |
Hard Disk |
•Two disks in RAID 1 (optional, recommended). •Each disk having 10 GB minimum. |
40 GB minimum. |
|
Processor |
•64-bit. •4 cores minimum. •3GHz or higher. |
•64-bit. •2 cores minimum. •2.4GHz or higher- |
|
Additional recommendations |
•Two NIC - Dual port 1GB •Redundant Power Supply |
||
SOFTWARE |
Operating System |
•Windows Server 2019 •Windows Server 2016 •Windows Server 2012 R2 These operating systems should have the latest Service Pack installed. |
•Windows Server 2019 •Windows Server 2016 •Windows Server 2012 R2 •Windows 10 •Windows 8.1 •Windows 8 (all editions except Windows 8 SL). These Windows versions must have the latest Service Pack installed. |
Web Server |
•IIS 10 •IIS 8.5 |
•IIS 10 •IIS 8.5 |
|
Additional Components |
•Automation Server, which also installs Microsoft .NET Framework 4.8 (and this one includes in turn, other components such as Visual C++ 2010, 2008 Redistributable). •Oracle Data Provider for .NET component (applies to projects that connect to an Oracle database). |
•Automation Server, which also installs Microsoft .NET Framework 4.8 (and this one includes in turn, other components such as Visual C++ 2010, 2008 Redistributable). •Oracle Data Provider for .NET component (applies to projects that connect to an Oracle database). |
Sites requirements
If you are using Bizagi Sites, you need any of the following versions of .NET Core:
•.NET Core 2.1.1
•.NET Core 2.2.104
•.NET Core 2.2.3
Bizagi Studio server installer includes the 2.1.1 version by default.
Other relevant infrastructure assets
Consider the following infrastructure requirements and other relevant recommendations:
1. Load balancer
For the load balancing for Bizagi servers, you may use either a software or hardware load balancer.
Bizagi does not provide the load balancer.
It is recommended the use of a hardware-appliance load balancer such as f5.
2. File server (optional)
Files and documents uploaded through your processes, are not stored in the database.
You may choose to integrate your corporate ECM/DMS system as a documents repository that store such files and documents; or alternatively, you may rely on a file server (i.e., a shared network drive). Bizagi does not provide the file server or ECM/DMS system.
It is important that all nodes of your Bizagi server cluster have access to such file server.
Such file server needs no specific requirements, save having the sufficient hard disk capacity to store your documents and files.
You will need to calculate and perform a sizing analysis based on the expected amount of files and their file size.
3. Reverse proxy server (optional)
In case you choose to set up a secure access to your processes via Internet, it is recommended to use two nodes for a reverse proxy server in a high availability system architecture (configuring a load balance cluster at this layer).
Bizagi does not provide the reverse proxy server.
Each node should consider the following requirements, involving an Apache HTTP Server:
REVERSE PROXY SERVER |
||
---|---|---|
HARDWARE |
Hard Disk |
1 GB. |
Additional recommendations |
•Two NIC - Dual port 1GB. •Redundant Power Supply. |
|
SOFTWARE |
Reverse proxy module |
Apache HTTP Server. Requisites to set an Apache HTTP Server instance can be reviewed at Apache HTTP project official's documentation according to the specific version and platform. |
End users and testers
Bizagi Work portal is a web-based application and therefore, end users only need a browser or Bizagi's app installed for mobile devices.
Bizagi presents several optimization measures featured by its own product architecture, focused on mobile devices support, so that the best user experience is provided without the need of demanding requirements (for instance, Bizagi has been tested with 3G and 4G internet).
Even though Bizagi does not demand a high speed in the network for end user connectivity, consider that there are factors which are beyond Bizagi's control, and which may affect overall end user experience.
End users on mobile devices would be communicating over the internet. This communication will inherently depend upon factors such as: A higher latency in data transmission, fluctuations, interference and congestion affecting the speed of the channel, or the quality of the networks used during transmission, among others. We strongly recommend using the mobile application. If a browser is t be used in mobile devices, we recommend using the Mobile view, where the minimum resolution is 700px.
REQUIREMENTS FOR END USERS |
||
---|---|---|
DESKTOP (PC) OR LAPTOPS |
Screen resolution |
1024 x 768 or higher. |
Browsers |
•Chrome 24 or higher. •Firefox 19 or higher. •Microsoft Edge 79 (with chromium) or higher. |
|
MOBILE DEVICES (tablets, smartphones) |
Devices / OS |
•iOS iPad, iPhone: 9 or higher. Browser: Safari (Private browsing mode not supported) •Android smartphones and tablets: Lollipop (5.0) or higher. Browser: Chrome. |
Important
Consider the following notes:
1. Operating systems installed in Turkish language are not supported.
All involved servers will need to be set with regional settings different to those for Turkish language and culture (tr, tr-TR).
2. Consider recommended guidelines when installing and configuring Bizagi.
These guidelines include a sizing estimation for best performance, as well as relevant infrastructure aspects in the overall system architecture.
For instance, there are recommendations regarding the network or when setting up the above servers in virtual machines.
For more information about these recommendations, refer to the Optimizing performance chapter.
Further information about infrastructure configurations
Refer to the following articles for further information for different setups in your test or production environments:
1.For a high availability architecture on a production environment, refer to High availability setup.
2.For a standard architecture on a production environment, refer to Standard setup.
3.For a standard setup on a test environment, refer to Test environment setup.