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


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.



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>\

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>\


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:









4. Save file and restart cluster.



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 file is override.


Configuration example

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


Instance 1 (master)



Instance 2 (slave)




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@] - Welcome from [akka.tcp://bizagiCluster@]


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