Bizagi Engine supports process execution in a JEE platform.
When running your processes in a JEE platform, and in order to setup your processes for a Test or Production environment, you will need to follow the steps in this section.
For projects running in the Development environment, there is no need to carry out any configuration or application deploy step.
Bizagi automatically performs both the configuration and deploy steps by using a bundled JBoss Server.
What you need to do
For the Test or Production environments of Bizagi running in a JEE platform, you will need to deploy your Processes to the Test or Production Databases.
After the automation phase of a Bizagi project has been completed and the Processes have been verified in the Development environment, you promote the processes by using Bizagi's Advanced Deployment.
The advanced deployment tool allows you to publish those Processes from the Development Database into the target Database.
Once you have the changes updated in the Test or Production Database, generating the Work Portal needs to be done (by deploying the application) in the JEE Application Server.
For this, ensure you have: A JEE Application Server properly configured, and Bizagi's JEEConsole Manager installed.
In summary, all required steps are:
1. Performing a Bizagi Deployment.
For Bizagi processes running in a JEE platform, use the Advanced Deployment Tool for this Bizagi Deployment.
2. Configuring your test or production JEE architecture.
Ensure you have a JEE Application Server configured to work with Bizagi. Supported JEE Application Servers is JBoss.
For this step you need Bizagi Engine for JEE files.
More information at Configuring a JEE Application Server.
3. JEE application deployment.
Generate Bizagi Work Portal by deploying processes as JEE application into your Application server.
This is done in an assisted manner through a JEE console provided by Bizagi (for this step you need Bizagi Engine for JEE files).
More information at Deploying the application into a JEE Application Server.
Each time you publish changes into your test or production environment you will need to carry out this step.