Best practices in the production environment

<< Click to Display Table of Contents >>

Navigation:  Bizagi Engine > Bizagi system administration > Maintenance and administration >

Best practices in the production environment

Overview

Production is the environment where your business Processes are actually put on operation by end users. In this environment your Processes must work at their best to avoid disruptions, ensure the accuracy and availability of the information and provide a the best user experience. Here there are some recommendations you have to take into account to ensure a proper operation of your Processes in Production environment:

 

1. Optimize performance

2. Do not affect end users when performing maintenance tasks

3. Enforce continuous improvement
 

 

1. Optimize performance

 

Turn traces off

When setting up your Production environment, make sure that Bizagi traces are disabled by default.

Traces provide a measure to follow up issues (should they arise) and, therefore, these should be active only when needed. Having these logs and traces disabled will provide better performance. Traces in the Production environment are not recommended since logs can grow a lot creating performance problems.

 

If you need traces in Production just leave on the components you need and turn off all others.

 

Avoid using virtual machines for databases

When setting up your production environment, it is recommended to use a real machine as the database server. Similarly, you should make sure that a fast connection is guaranteed between the Bizagi server and the database server. Using a virtual machine may not present optimal performance (it may not provide an optimal disk speed among other variables).

 

 

2. Do not affect end users when performing maintenance tasks

 

Synchronize LDAP at NON-working hours

When using LDAP synchronization to import your users into Bizagi, make sure that the LDAP Server responds in a timely fashion. All configuration must occur out of work hours or at a time of least throughput (especially when synchronizing more than 1000 users).

 

You should always use both: proper filters in your configuration for the LDAP synchronization, and as a good practice, to schedule this synchronization at non-working hours. When scheduling this job, make sure you track that it is completed according to an expected threshold (before working hours start again).

 

Other maintenance tasks at NON-working hours

Similarly, any other maintenance tasks should be carried out in an appropriate time frame which does not affect the system's busy hours.

Such tasks can involve: process deployments, version upgrades, database tuning, platform updates and patches, archiving information, etc.

 

 

3. Enforce continuous improvement

Continuous improvement is a key part of Bizagi evolution for the Customer. There are 2 types of improvements:

Minor changes that do not affect the work flow or a change in the data model that does not affect the logic of the process

Changes affecting the work flows or changes that impact the process logic.

 

Actions:

New process version:

oRecommendation: Create a new version of the process if it's been deployed in production environments and you're not sure how the new changes will affect the current cases running in production environments.

oRecommendation: Create a new version of the process if the workflow changes.

oRecommendation: Create a new version of the process if the Data Model changes.

 

New Form versions:

oRecommendation: Create a new version of the forms if the data model changes and new data is required.

oRecommendation: Create a new version of the forms if the rules using the form data change.

 

Do not create a new versions of the process, or forms, if the changes are considered minor and you are sure that these changes will not create side effects on cases running in production environments.