Bonita cluster installation and configuration

Ensure that you meet the requirements.

Create the database.

In case you use Business data, create a database for the Business Data.

Download a Bonita Tomcat bundle and unzip it at some place of your choice.

Edit file setup/database.properties and modify the properties to suit your databases (Bonita internal database & Business Data database). Beware of backslash characters.

Edit the file setup/platform_conf/initial/platform_engine/bonita-platform-sp-custom.properties: Uncomment and set the bonita.cluster property to true, as follows: bonita.cluster=true

Edit the file setup/platform_conf/initial/platform_engine/bonita-platform-sp-custom.properties: In order to keep consistency between nodes, the Hibernate cache must be disabled: Uncomment and change the line: #bonita.platform.persistence.use_second_level_cache=true change it to: bonita.platform.persistence.use_second_level_cache=false

Edit the file setup/platform_conf/initial/platform_engine/bonita-platform-sp-cluster-custom.properties: uncomment and set the bonita.cluster.name property to a name of your own, e.g. myBPMCluster, This name must be unique on the local network if you are using multicast

Edit the file setup/platform_conf/initial/platform_engine/bonita-platform-sp-cluster-custom.properties: set to true one of bonita.platform.cluster.hazelcast.multicast.enabled or bonita.platform.cluster.hazelcast.tcpip.enabled or bonita.platform.cluster.hazelcast.aws.enabled, as follows: Uncomment the # properties and set only one of them to true, set the others to false depending on how you want your nodes to discover each others. Example:

bonita.platform.cluster.hazelcast.multicast.enabled=false
bonita.platform.cluster.hazelcast.tcpip.enabled=true
bonita.platform.cluster.hazelcast.tcpip.members=ipServer01,ipServer02

Copy licenses of all your nodes in setup/platform_conf/licenses.

Run setup.sh init or setup.bat init as described in the platform setup tool page.

Once you have done all the steps from section Create and initialize the database for Bonita Platform above, run setup.sh configure or setup.bat configure as described in the Bundle configuration to have your Tomcat bundle configured to point to the right database.

Once the bundle is configured, and to avoid unsynchronized versions of the configuration files between several nodes, you are advised to delete the folder [TOMCAT_DIRECTORY]/setup and its entire content. Note: if you want to keep it for future configuration changes, just move the folder [TOMCAT_DIRECTORY]/setup and its entire content outside the [TOMCAT_DIRECTORY] to use it as your main platform setup tool.

If your Bonita installation is behind a proxy or is installed inside a Docker container (mainly in TcpIp or Aws discovery modes), you must declare its public address by adding the following property: -Dhazelcast.local.publicAddress=publicaddress, this property should be added in the [TOMCAT_DIRECTORY]/setup/tomcat-templates/setenv.sh or [TOMCAT_DIRECTORY]/setup/tomcat-templates/setenv.bat

When the installation is complete, start Tomcat on the node. This starts Bonita Platform:

./start-bonita.sh

Then start the cluster in the load balancer.

<Engine name="Catalina" defaultHost="localhost" jvmRoute="node01">

Check that the log file contains messages of the following form:

March 22, 2016 5:07:07 PM INFO: com.hazelcast.cluster.ClusterService [10.0.5.3]:5701 [myBPMCluster]

Members [1] {
        Member [10.0.5.3]:5701 this
}
[...]
March 22, 2016 5:09:18 PM INFO: org.apache.catalina.startup.Catalina start Server startup in 30333 ms

Then deploy a basic process and check that it runs correctly, to validate the installation.

Copy the entire Tomcat directory to another machine.

If Hazelcast Node discovery is configured with TCP, update the configuration in database using the platform setup tool, as follows:

Start the Tomcat on the new node, running ./start-bonita.sh script

Update the load balancer configuration to include the new node. The log file will contain messages of the following form:

March 22, 2016 5:12:53 PM INFO: com.hazelcast.cluster.ClusterService [10.0.5.17]:5701 [myBPMCluster]

Members [2] {
        Member [10.0.5.3]:5701
        Member [10.0.5.17]:5701 this
}
[...]
March 22, 2016 5:12:28 PM INFO: org.apache.coyote.http11.Http11Protocol start Starting Coyote HTTP/1.1 on http-7280
March 22, 2016 5:12:28 PM INFO: org.apache.catalina.startup.Catalina start Server startup in 30333 ms

Update the load balancer configuration so that no further work is directed to the node. All work that is already in progress on the node that will be shutdown will continue until completion. Do not remove the node completely, because the load balancer needs to be informed when current work is finished.

Allow current activity instances to complete.

Stop the Tomcat server: run ./stop-bonita.sh

Update the load balancer to remove the node from the cluster.

Disable processes.

Allow current activity instances to complete.

When each node has finished executing, stop it.

When all nodes have been stopped, update the load balancer to remove the cluster.