How to Copy a Project to Another Server
From Business Process Management, BPM and Workflow Automation Wiki | BizAgi BPMS
<keywords content="keywords"> copy project, move project, change server, move process, copy process, how to copy a project </keywords>
How to Copy a Project to Another Server
Sometimes users want to change a project from server or maybe to have a local copy of somebody else's project. This is a simple procedure if the project is copied from a Development environment and a Deployment has not been executed.
Important recommendations
Before you copy a Project to another server it is necessary to review this recommendations carefully to avoid problems.
The first recommendation that needs to be taken into consideration is that a general set of tests needs to be done since the movement implies a complex set of tasks.
It is also important to have security copies of the environments, including database and website backups. If, in addition, there are special directories configured for the documents, they need to have a backup as well.
To be able to make a backup it is necessary to have the SQL Server Management Studio. The SQL Server Express Edition installer does not include this tool, but it can be downloaded here.
Please keep in mind that once the Bizagi installation process is finished, the fixes sent to the project to correct bugs need to be updated. The easiest way to do this is to overwrite the bin folder with the files from the original environment.
If the processes interact with interfases, these systems need to have a backup if their platform is going to be changed.
Do not forget that the licenses may need some changes or movements that can apply. You should contact the support deppartment of Bizagi in such a case.
Finally, if you are using Letters you need to move your documents once the porject has been moved. Just copy and paste all documents in the same folder path. Click for more information about where letters are saved.
Instructions to copy a project to another server
The following are the steps to perform the copy with the above restrictions.
|
Note: For a project in Production Environment there is the option to move the project to another server. |
In the target server, open Bizagi Studio and select the option to create a new Bizagi project.
Give the project a name, it may be the same it had on the other server, or any other name that is not already been used in the destination server.
If this is the first Bizagi Xpress project on the server, the database information is asked. Select the instance where the project database would be created and enter the login and password.
After the project is created, close Bizagi Studio and restore the recently created project's database using the backup of the source project (learn how to restore a database).
|
IMPORTANT!! In Bizagi is necessary that the server and databases collation match, as well as the collation of the database servers in each environment. Before restoring the database check that the destination SQL Server instance has the same collation as the source server. |
The project's database can be distinguished because it has the same name as the project; the path of the database usually is C:\Bizagi\Xpress\Projects\$PROJECT_NAME$\Database
|
Note: To avoid errors, both, source and destination projects, must be in the same version of Bizagi. Otherwise when opening the project in the destination server with Bizagi Studio a message informing this is shown. This message is like: "Error Bizagi database version DbBuild XXX is not supported. This Bizagi version (9.1.X.XXXX) only supports DbBuild XXX (Project: _______)" |
<comments />
