Deploying the application into Weblogic

<< Click to Display Table of Contents >>

Navigation:  Bizagi Engine > Bizagi system administration > Bizagi server configuration > Bizagi Engine JEE platform configuration > Deploying into a JEE Application Server >

Deploying the application into Weblogic

Overview

This section describes how to generate Bizagi Work Portal in Weblogic (deploy the application into this JEE Application Server).

The following instructions applies for both: Deployments in clustered configurations (when using more than 1 Weblogic node), and deployments in standalone setup (standard configuration).

 

 

Prerequisites

Ensure you meet both:

Having already used Bizagi Advanced Deployment to publish Processes from the Development Database into the Test or Production Database.

Having Weblogic properly configured to work with Bizagi. Weblogic should be in a started mode.

For more information refer to Configuring Weblogic.

Having access to the .ear file delivered as <CONFIGURATION_INPUTS>\Bizagi-ear-Weblogic.ear.

This path and file is referred to when configuring Weblogic.

Having installed Bizagi JEE Console. This local path is referenced in this guide as <JEECONSOLE_HOME>.

 

 

What you need to do

You will need to:

1. Configure the project template XML file.

2. Generate the .EAR file.

3. Install the Work Portal.

 

 

Procedure

The following steps describe in detail how to deploy the application into Weblogic.

 

1. Configure the project template XML file.

In order to generate the final .EAR file, you need to first configure the XML file for your project's environment.

The template file to configure this setting, is delivered within the Bizagi JEE Console, and it is found as <JEECONSOLE_HOME>\ProjectTemplate.xml.

 

Therefore, make sure you copy this XML template file and paste it to create a new one for your project.

 

note_pin

Take into account:

1. That paths are separated by using the slash character ("/").

2. That this XML file should not contain commented lines.

The commented lines are included in the template to provide configuration example.

3. That you rename the XML configuration file so that it is named after your project (as it will be referenced later on through commands in the JEEConsole).

 

For Weblogic, make sure that the project template file has the required Weblogic elements:

 

WEBL_projecttemplate

 

note_pin

If you are using a Database cluster, which relies on Oracle RAC (for your Oracle Database), then you will need to make sure that the <isRac> property is set to true, and that your specified connection details consider your RAC.

 

Console_isRAC

 

2. Generating the .EAR file

Once you have set the project template file, run the following command with Bizagi JEE Console:

 

In a Unix-like OS such as Linux, use:

sh <JEECONSOLE_HOME>/bin/JEEConsoleManager.sh createproject -f <CONFIG_PATH>

 

In a Windows OS, use:

<JEECONSOLE_HOME>\bin\JEEConsoleManager.bat createproject -f <CONFIG_PATH>

 

Consider that <CONFIG_PATH> is the path where the configuration XML file is located.

Notice that this command will create the following directory: <JEECONSOLE_HOME>\projects\[PROJECT_NAME]

 

 

Once this command is successful, run the predeploy command with Bizagi JEE Console:

 

In a Unix-like OS such as Linux, use:

sh <JEECONSOLE_HOME>/bin/JEEConsoleManager.sh predeploy -o <OUTPUT_PATH> -p [PROJECT_NAME] -f <FILE_PATH>

 

In a Windows OS, use:

<JEECONSOLE_HOME>\bin\JEEConsoleManager.bat predeploy -o <OUTPUT_PATH> -p [PROJECT_NAME] -f <FILE_PATH>

 

Consider that:

<OUTPUT_PATH> is the optional path to specify where the EAR file will be generated. Do not use -o if this information is not to be included (by default, the output file will be generated as <JEECONSOLE_HOME>\projects\[PROJECT_NAME]\dist\BizAgi-ear-Weblogic.ear) .

[PROJECT_NAME] is the project's name as specified in the XML at the <CONFIG_PATH>. Using -p for this parameter is mandatory.

<FILE_PATH> is the optional path where the basic .EAR distribution file is located (which needs to be referenced to generate the final .EAR).

This file is initially delivered within the configuration inputs as <CONFIGURATION_INPUTS>\BizagiBPMJEE\Bizagi-ear-Weblogic.ear.

Do not use -f if this information is not to be included (when not specified, the location will be taken from the projectemplate.xml.)

If your Weblogic configuration uses more than 1 node (cluster set up), you will need to use -c to specify that the predeploy should run with cluster considerations. Absence of this parameter will indicate that no cluster is involved (standalone set up).

 

 

note_pin

You may find additional information about how to use Bizagi JEE Console at its local Readme-console.txt file.

 

Development environment considerations

If you are using Weblogic in your development environment (authoring) instead of using the JBoss instance that comes bundled with Bizagi Studio, there is the option to refresh the application's cache memory to avoid re-generating the application in some scenarios:

 

This option is to use the cleancache command provided by the JEE administration console. This command will refresh information when simple changes are carried out, and strictly no changes have been made to the data model.

For instance, when making minor editions in rules or in forms appearance, you may use this command as described:

cleancache -p [PROJECT_NAME] -host [SERVER] -port [PORT]

 

For its use, consider:

PROJECT_NAME: The project's name. Its definition is required along with the -p parameter.

SERVER: The name of the server (or its IP address) on which we want to refresh the cacheed information. Its definition is required along with the -host parameter.

PORT:  The port number being used by the Application Server. Its definition is required along with the -port parameter.

 

 

 

 

3. Installing the Work portal

The steps required to install Bizagi Work portal apply for both scenarios: When Weblogic is configured to use more than 1 node (cluster setup) or when it is running as a standalone server (standard configuration).

The only difference in the Work portal installation procedure is in the step where you configure the scope (Target) of the installation.

 

 

1. Log on to the Administration Console and using the navigation pane go to Domain Structure – Deployments.

Keep in mind that if this is not the first deployment, then you will prior need to uninstall (delete) the existing Bizagi application to install the newly one.

Click Install for the new one once you ensure you don't have an existing one.

 

2. Browse into the <CONFIGURATION_INPUTS>, where the EAR file for Weblogic was generated.

Select this file (Bizagi-ear-Weblogic.ear).

 

WEBL_deploy01

 

3. Use the Choose targeting style option to select the option Install this deployment as an application and click Next.

 

WEBL_deploy02

 

4. If you have your Weblogic set up in a cluster, make sure you mark the cluster checkbox and include the All servers in the cluster option to apply this configuration to all your nodes (under Select Target).

Then click Finish.

 

WLCluster_Data01

 

On the other hand, if your Weblogic configuration runs in standalone mode, just click Finish.

 

It is recommended that you restart the application once changes are updated.

 

 

To verify that the Work Portal was installed correctly, enter the following address into any browser (keep in mind that this URL is case sensitive):

http://localhost:7001/BizAgi-war/

 

Additional step

If your project is set up for a test or production environment, and it uses Virtualization or Replication, you will need to register in your JEE Application Server, the external data source involved in this integration.

For more information about this, refer to How to configure Replication or Virtualization in a JEE Application Server.

 

You may also set up Bizagi ODS in order to improve the performance and availability of your Bizagi server.

For more information, refer to Configuring Bizagi ODS for Process Analytics.