[jbpm-dev] jBPM 6 Clustering

Kris Verlaenen kverlaen at redhat.com
Wed Jun 14 20:55:20 EDT 2017


Rama,

This email list is no longer actively used, I would recommend to try:
https://groups.google.com/forum/#!forum/jbpm-usage

But quick answers below ...


On Wed, Jun 14, 2017 at 1:58 PM, Rama Rao P <rama.rao.p at celstream.com>
wrote:

> Hi All,
>
>
>
> This is my first post there.. so, kindly excuse me for mistakes.
>
>
>
> I am trying to get the jBPM Clustering setup… I am new to the Clustering
> concepts..
>
> Can someone guide me / point me to a good source of this?
>
>
>
> I have already tried to follow steps given in below links…but, seem to be
> little lost on seeing the clustering in action..
>
> http://planet.jboss.org/post/clustering_in_jbpm_v6
>
> https://docs.jboss.org/jbpm/v6.0/userguide/wb.
> WorkbenchHighAvailability.html
>
>
>
> what I have today:
>
>
>
> 1.       Zookeeper is running
>
> a.       Added a cluster
>
> b.      Added two nodes
>
> c.       Added resource VFS
>
> 2.       Installed jBPM (FULL) on two machines (I know in real two
> instances for clustering may not work out. But just wanted to see things
> working).
>
> a.       Configured host.xml for required properties (as mentioned in 2nd
> link above).
>
> 3.       Running helix controller. (this is contacting Zookeeper).
>
>
>
> How do the two instances of jBPM talk to each other?
>
> How do they (jBPM instances) share the data?
>

Clustering works differently for authoring and runtime data.  For
authoring, the workbench (using helix / zookeeper) will make sure that any
change to the (internal) git repositories (that is holding all your project
assets) is distributed in the cluster.  For runtime data, you need to make
sure you are using the same database.  The server instances themselves are
stateless, they get and store their information from/in the database for
each request.

Hope that helps.

Kris


>
>
>
>
> Regards,
>
> Rama.
>
>
>
>
>
>
>
> ------------------------------------------------------------
> -----------------------------------------------------------------
> DISCLAIMER: This electronic message and any attachments to this electronic
> message is intended for the exclusive use of the addressee(s) named herein
> and may contain legally privileged and confidential information. It is the
> property of Celstream Systems Private Limited. If you are not the intended
> recipient, you are hereby strictly notified not to copy, forward,
> distribute or use this message or any attachments thereto. If you have
> received this message in error, please delete it and all copies thereof,
> from your system and notify the sender at Celstream Systems or
> administrator2 at celstream.com immediately.
> ------------------------------------------------------------
> -----------------------------------------------------------------
>
> _______________________________________________
> jbpm-dev mailing list
> jbpm-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbpm-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbpm-dev/attachments/20170615/c80c1112/attachment.html 


More information about the jbpm-dev mailing list