Configuring Token synchronizer with actors

<< Click to Display Table of Contents >>

Navigation:  Automation Server for JEE > Automation Server JEE configuration and administration > Automation Server for JEE installation > Automation Server JEE platform configuration > Setting up the system architecture >

Configuring Token synchronizer with actors

Overview

As asynchronous task are executed in all cluster nodes, it is necessary to have a coordination mechanism between all cluster members to close the process, for example when a BPM End task is a token collector, the last token must close the process.

 

Configuration

To support singleton actors follow the next configuration:

 

1. Check that port 2552 is available in all the machines where cluster nodes are installed.

If it is not available, set an available port in property CLUSTER_REMOTE_PORT inside the file <CONFIGURATION_INPUTS>\bizagi-config\<NODE_NAME>\bizagi-cluster-node.properties.

If more than one cluster node is executed in a machine, for example in vertical clusters, please set a distinct port for each instance in file <CONFIGURATION_INPUTS>\bizagi-config\<NODE_NAME>\bizagi-cluster-node.properties.

 

2. Select two cluster nodes. These nodes are the cluster seed nodes.

Get following information of the seed nodes:

Machine IP or hostname.

Port configured in the property CLUSTER_REMOTE_PORT. If no port is set in the file, the default port is 2552.

 

3. For all cluster instances, set the CLUSTER_SEED_NODES property with following syntax:

 

CLUSTER_SEED_NODES=<seed1_hostname_or_IP>:<seed1_port>,<seed2_hostname_or_IP>:<seed2_port>,...,<seedN_hostname_or_IP>:<seedN_port>

 

Examples:

CLUSTER_SEED_NODES=172.17.0.2:2552,172.17.0.3:2552

CLUSTER_SEED_NODES=machineA:2552,machineB:2552

CLUSTER_SEED_NODES=machineA:2552,machineA:2553

 

4. Save file and restart cluster.

 

note_pin

If you need advanced settings or tune up when use Asynchronous Task with feedback, please add file <CONFIGURATION_INPUTS>\bizagi-config\<NODE_NAME>\bizagi-async-cluster.conf using syntax of Akka configuration file.

 

When the bizagi-async-cluster.conf file exists, the configuration located in bizagi-cluster-node.properties file is override.

 

Configuration example

Take into account the following are examples of the configuration in the bizagi-cluster-node.properties files for a cluster with two nodes (instances).

 

Instance 1 (master)

-Dbizagi-cluster-node-config=/home/was/BizagiJEE/BizagiBPMJEE/bizagi-config/node01
 
SCHEDULER_MASTER_NODE=true
CLUSTER_SEED_NODES=10.0.2.4:50242,10.0.2.7:50242
CLUSTER_REMOTE_PORT=50242

 

Instance 2 (slave)

-Dbizagi-cluster-node-config=/home/was/BizagiJEE/BizagiBPMJEE/bizagi-config/node02
 
CLUSTER_SEED_NODES=10.0.2.4:50242,10.0.2.7:50242
CLUSTER_REMOTE_PORT=50242

 

Checkpoint

To verify whether the configuration is correct, check the bizagi-bpm.log file. After the server is started, the traces indicate that configuration is correct when all the nodes are connected to cluster.

 

For our previous example, the log shows a record like the following:

   

[akka.cluster.Cluster(akka://bizagiCluster)] Cluster Node [akka.tcp://bizagiCluster@10.0.2.7:50242] - Welcome from [akka.tcp://bizagiCluster@10.0.2.4:50242]

   

This indicates that the cluster bizagiCluster@10.0.2.7:50242 has joined the cluster lead by bizagiCluster@10.0.2.4:50242. This message must appear for each cluster node in your architecture.