Bizagi Engine has an architecture which offers the necessary components to set up a high availability solution or standard solution.
When setting your processes to run in a JEE platform, having a high availability architecture, consider the following aspects for your configuration.
Main elements to configure within your Bizagi system architecture when running in a JEE platform are:
•Database Server (Data access layer).
For mission critical applications and for a high availability schema, it is recommended to set up more than 1 node for the Database Server, in order to rely on a failover cluster.
Failover capabilities (i.e, an active-passive schema) is provided by the different Database engines.
•Bizagi Server (Digital process layer).
For mission critical applications and for a high availability schema, it is recommended to set up more than 1 node for Bizagi server, in order to provide load balancing capabilities.
For this set up, configure the JEE Application server in your cluster according to Configuring a JEE Application server to work with Bizagi.
•Load balancer (for Bizagi)
For load balancing, you may use either a software or hardware load balancer.
It is recommended the use of a hardware load balancer (i.e, F5), and note that Bizagi does not provide the load balancer.
Bizagi supports any load balancing algorithm, and the only requirement for the load balancer configuration is that sticky sessions are enabled.
You will need to use and configure a load balancer for a high availability architecture.
For an example on the load balancer configuration, refer to Configuring a load balancer, in which an Apache HTTP Server is used to illustrate the high availability architecture.
Consider the additional elements which can be involved in your Bizagi solution:
An optional proxy for internet access
For projects in which end users need to work on the processes via internet from any device, an optional Server can be consider to provide reverse proxy capabilities.
This reverse proxy is set in the DMZ and can be set through an instance of Apache HTTP Server, in order to allow internet access to processes while keeping the Bizagi server restricted.
For more information about this option, refer to Setting Bizagi for Secure Internet Access.
External databases integrated to the solution
If your project integrates external data sources through Bizagi Data Virtualization and Data Replication features, you will need to configure these external data sources at the Application server, as described at Configuring Replication or Virtualization.
If your project integrates external web services, or other systems used for authentication purposes (for instance, an LDAP. or an identity provider system featuring federated authentication), you will need to ensure that these services are accessible by Bizagi and compliant to its configuration.
You will need to validate as well that you can connect Bizagi to your corporate SMTP server in order to send out process notifications.