Bizagi system administration consists of procedures and guidelines, recommended practices, and descriptive information that is useful for you to plan and execute these types of tasks:
•Setting up Bizagi Engine in a production environment.
•Configuring other components that make part of your corporate system architecture, in order to work with Bizagi Engine.
•Deploying processes and new versions (business-driven improvements).
•Administration and maintenance tasks (concerning operations), and monitoring recommendations for Bizagi Engine.
Bizagi System components
Keep in mind that a Bizagi System considers the following components, which are involved in a Bizagi project:
1. A process repository.
Namely a RDBMS in which Bizagi stores the processes model and information.
The process repository is set as a database in a Database Server and can be set with additional fault tolerance measures.
2. Bizagi Work portal.
A web-based portal for end users to log in and work on processes.
Bizagi Work portal is set as a Web application in the Digital process layer.
For a high availability solution, a Bizagi server configuration considers the use of more than node in a cluster.
3. Bizagi Scheduler.
An agent run by Bizagi as a service, in charge of running system maintenance, offline and asynchronous tasks, all which you can schedule.
4. Additional infrastructure.
Each project may rely on several other hardware or software options for the system setup, such as:
•A fault tolerance setup for the database tier, either to support an active-active or active-passive scheme.
•An ODS set for best availability and performance of the Bizagi Work portal.
•A load balancer for high availability of the solution (as a scalability measure in a cluster setup).
•An additional HTTP server to provide reverse proxy capabilities (for internet access to Bizagi) or to store static web resources.
5. Additional integrated systems.
External systems integrated into the solution include:
•An LDAP server providing integrated authentication.
•An SMTP server used for notifications.
•An ECM system used as the documents repository.
•An ESB providing integration services.
Or, one or more independent systems publishing Web services used by Bizagi processes.
•One or more SAP system integrated directly by means of Bizagi SAP connector.
•One or more databases integrated through Data Virtualization or Data Replication.
•Other applications, or external folders and files used directly by APIs or libraries registered in Bizagi through the Component library feature.
In order to run system administration tasks, the following profiles are usually involved and recommended:
1. A database administrator (DBA).
Should have specific expertise in the employed database engine (SQL Server or Oracle).
2. A platform administrator.
Should have specific expertise in the Application server used by the solution (WebSphere, Weblogic, JBoss, or IIS), as well as expertise regarding the operating system on which the Application server runs (e.g, a Windows OS, or a Unix-like OS such as Linux).
Similarly, this profile should be able to handle, redirect or escalate subjects related to any additional infrastructure or systems involved, such as the load balancer's configuration, a proxy server, etc.
3. A business administrator.
Should know about the implemented processes and all parameters and variables affecting the Bizagi operating environment.
Should lead the deployment plan of processes as well as their upgrade into new versions and, have full rights in Bizagi for the administration options.
This role can be taken by a leading business analyst or architect.
Refer to the chapters in this section for information related to requisites, configuration and administration of the Bizagi System:
1. For information about the requisites, configuration and options for your Database Server, refer to Database server configuration (applies for all environments: Development, Test, Production).
2. For information about the configuration involved for the servers for Bizagi, refer to Bizagi server configuration.
3. For additional infrastructure options, such as setting up a reverse proxy to access Bizagi securely through internet or at a cloud hosted environment (e.g Amazon AWS, Azure), refer to Other infrastructure options.
4. For information about deploying processes (i.e, publishing and promoting processes to production, or new versions of processes featuring continuous improvement) so that business requirements are aligned with IT expectations, refer to Deployment of processes and new versions.
5. For information about guidelines for maintenance and administration tasks in Bizagi projects and regarding the Bizagi System, refer to Maintenance and administration.