Documentation

bpm'online sales enterprise
PDF

Server-side system requirements

Server performance affects speed and productivity of bpm’online - the more powerful your hardware configuration is, the smoother bpm'online operation is going to be.

To work with bpm’online, you will need to deploy the following required components:

  • Application server

  • Database management system (DBMS)

  • The session storage server (Redis)

Optional components include:

  • Version control system server (SVN)

  • Load balancer

  • Containerization (operating-system-level virtualization)

System requirements may vary depending on the number of users who will access the system and system fault tolerance requirements.

General requirements for the servers

All system components should be functional in a virtual environment. The list of officially supported cloud/virtual platforms:

  • Amazon Web Services

  • Microsoft Azure / Hyper-V

  • VMware vCloud Director / vSphere

Note

Compatibility with other cloud / virtual platforms is not guaranteed.

Active system component instances must be placed in a single location (data center / server room / office building, etc.). Placing backup components in remote locations when implementing protection against catastrophic events is acceptable.

All components should function in their dedicated operating systems. Merging components is possible, but not recommended.

To organize a DBMS cluster, you can use either a shared file storage or separate disk space of cluster nodes.

The version control server (SVN) is optional. It is needed only in case of configuration version control.

The load balancer is an optional component, which may be useful, if:

  • there is an increased network load on the application servers

  • application servers are deployed in a fault-tolerant configuration (web farm)

The load balancer may be either hardware or software. To work in fault-tolerant mode, the HTTP/HTTPS traffic balancer is used with support for so-called “sticky sessions", and the WebSocket protocol. The application was tested on HAproxy and MS ARR (Microsoft Advanced Request Routing) software load balancers. There are known cases where other balancers like Citrix, Cisco, NginX, FortiGate were successfully implemented.

Connection channels

IIS – SQL:

  • the capacity of 10Mb/sec per 100 active users

  • delays no more than 15-20 ms

IIS – user:

  • minimum 256 Kb/sec per 1 active user

  • recommended 512 Kb/sec per 1 active user

  • formula: 30kByte/sec * (total number of users working at a time) * 10%

Input/output:

  • IIS; 100 IOPS per 1000 active users

  • SQL: 1000 IOPS per 1000 active users

Software requirements

Component

Software

Web server

Windows 2012 R2,2016,2019; IIS: .Net framework 4.7.2

Database server

Windows 2012 R2,2016,2019; MSSQL 2016

Caching server

Linux Debian 8-9; Redis

Load balancer server

Linux Debian 8-9; HAproxy

Version control system server (SVN)

Linux Debian 8-9; SVN

Containers

Linux Debian 8-9; Docker; Kubernetes

Contents

System requirements for 1 - 50 users

System requirements for 50 - 100 users

System requirements for 100 - 300 users

System requirements for 300 - 500 users

System requirements for 500 - 1000 users

System requirements for 1000 - 3000 users

System requirements for 3000 - 5000 users

System requirements for 5000 - 7000 users

System requirements for 7000 - 10000 users

Containerization (operating-system-level virtualization) requirements

Did you find this information useful?

How can we improve it?