Migration Guide to Bizagi 9.0

From Business Process Management, BPM and Workflow Automation Wiki | BizAgi BPMS

<keywords content="keywords"> migration, version 9 </keywords>

Migration Guide to Bizagi version 9.0

Objectives

Indicate the steps required to migrate from Bizagi V.8.6 (SQL) or V.2000 (Oracle) to V.9 in an application on the .NET platform.

List the points to be taken into account that can have a bearing on the project.

Requirements

Microsoft .NET Framework 1.1 – Visual Studio 2003

Database Update Script:

           For SQL Server: DBBuildUpgrade-SqlServer.sql

           For Oracle: DBBuildUpgrade-Oracle.sql

These files are located in the folder Upgrade\DBBuildUpgrade on the V.9 installation CD

Files provided corresponding to the V.9 Web Application

Steps for Migration

The following is a list of steps required to migrate an implementation from V.8.6 to V. 9.

1.      The version should be in 8.6x. If it is in a previous version, use the corresponding migration document and then migrate from 8.6x to V. 9.

2.      Run the integrity validation script in the database for V.8.6. If the results show any inconsistencies, they should be corrected in order to apply the corresponding dbBuildUpgrade.sql successfully.

3.      Run the dbBuildUpgrade.sql.

If the warning message BADBUpgrd-Upg-001 appears during execution, it means there is an entity for which the display attribute defined does not exist, which should be corrected before going on as this can cause errors in the web application.

4.      Install Bizagi Control panel.

5.      Create a new project using the Bizagi Control Panel and replace the website altogether, except for the document directory that contains the documents uploaded for the cases.

6.      It is important for the setup file of the Web.Config application not to have any Bizagi entries. That is to say, there should not be any of the configuration parameters that were used because they are now in the database.

That is to say, the only keys that should be in the web.config file are:

add key="DSNDB"

add key="DSNOLAP"

add key="PROVIDERTYPE"

add key="PasswordNotificationSubject"

add key="PasswordNotificationBody"

All other parameters should be configured as follows:

Start Bizagi Studio, then click on the advanced tab. Click on the parameter button at the top to access the global parameter configuration screen. There are also custom keys that can be added through the last tab in the configuration window (for further details, refer to the product manual)

7.      Compile the touch points and the existing components with the new references, as well as the assembly of the component library.

8.      The implementation file implementation.js should be entered through Bizagi Studio using the advanced options – javascript menu.  This code will be saved in the database and the file “implementation.js” will be replaced, therefore, it is not enough to copy the file to the web application directory.

9.      If a topic was created using workportal to apply on the site, due to changes in functionality, it should be created again using V.9.

10.     Uninstall the current Scheduler and install the V.9 Scheduler, which can also be done using the Bizagi Control Panel.  If the scheduler calls on external components for the execution of Bizagi jobs, these assemblies should be included in the bin of the new scheduler.

11.     In V.9, new authorization entries have been created for the new functionalities, for instance, the policies. By default, everyone has access, so if you want to restrict access to these functionalities, create the respective permissions.

12.     If there are any advanced customizations, inquire with technical personnel to define the action plan. <comments />