To upgrade your Bizagi project to the latest Bizagi 11.1 release, follow the described recommendations and procedure in this section.
Before you start
It is mandatory that you upgrade to this release from a Bizagi project already in a 11.0 version.
Before upgrading your project, we recommend to:
1. Take backups of your Database and of your application's folders.
This means creating a Database backup file, and creating a copy of the folders and files (by default at C:\BizAgi\Projects\[your_project]\WebApplication and C:\BizAgi\Projects\[your_project]\Scheduler\).
Although you may create your own backups of the project's environments, Bizagi already automatically generates a backup of: the Database, the Scheduler and the WebApplication files before performing the upgrade.
In case you need these backup files, they will be stored at the backup path (in a SQL Server local setup, this would be: C:\Bizagi\Projects\[your_project]\Backups), as shown in the image below:
When having the SQL Server Database remotely, this path for will be usually set as: C:\Program Files (x86)\Microsoft SQL Server\[MSSQL_instance]\MSSQL\Backup\.
In projects using Oracle as the Database, the backup path will be as defined for that given Oracle instance (during project creation).
2. Always upgrade first your Development environment.
In this exercise, it is recommended to perform unit tests to verify that existing Processes behave as expected.
Once this is done, upgrading your Test environment and performing user-acceptance tests on this environment should be done as well.
After verifying that Processes work OK both in the Development and the Test environment and depending on how critical your Processes are, you may create a Production-replica environment.
In this way, in the Production-replica environment you can perform an upgrade and test your Production environment Processes with live instances.
After ensuring that the Production-replica environment Processes and instances are OK, upgrade your real Production environment.
A Production-replica environment is a Bizagi project which has the Production backup restored into it.
It is not the real Production environment because it would require that Production parameters and other relevant information are modified (for instance, the actual e-mail addresses of users, the SMTP Server or other URLs involved in integration points in the Processes, etc).
All environments should be upgraded, otherwise it will not be possible to carry out Deployments to publish your processes.
3. Plan the Development environment's upgrade and coordinate it with your team.
A version upgrade should be carried out with prior coordination, so that it is done at the Bizagi servers, strictly when other team members are not working on the project.
4. Plan the Production environment's upgrade to be carried out at non-working hours.
A version upgrade will temporarily stop services (for approximately 3 minutes).
5. Do not upgrade your version if you have a pending Release Candidate to deploy into Production.
You will need to have first applied that Release Candidate or to cancel it.
To upgrade your Bizagi version, recall that you will need to upgrade first your development environment.
For this, upgrade your Bizagi Studio installation (downloadable from our official www.bizagi.com). and then run it in your development environment server.
Notice that you should upgrade the Bizagi project directly at the development server (the server hosting the project, especially when talking about a teamwork collaboration setup).
Upgrading Bizagi Engine
Once you have successfully verified that your processes behave as expected in the development environment, you may upgrade your other environments (first test, then the production replica environment if you use it, and finally, production).
If you are running your processes in a .NET platform, then for the test and production environments, the upgrade is done by following a similar procedure to that one carried out in development, and under the same recommendations.
The overall procedure would be:
•Take backups and plan the upgrade previously.
•First install Bizagi Engine in its release that matches the Bizagi Studio used by your development environment.
Take into account that after upgrading the Bizagi Engine version, you should always reboot the server.
•Upgrade the project by using Bizagi Management Console.
•Verify that the processes behave as expected.
If you have manually installed and configured Bizagi in a test or production environment (as described at Configuring Bizagi operating environment), then you should contact our support team to carry out your version upgrade (which will be a manual procedure).