1. Download the jboss-bpmsuite-brms-VERSION-supplementary-tools.zip, which contains Apache Zookeeper, Apache Helix, and Quartz DDL scripts. After downloading, unzip the archive: the Zookeeper directory ($ZOOKEEPER_HOME) and the Helix directory ($HELIX_HOME) are created.
2. Now Configure ZooKeeper:
   1. In the ZooKeeper directory, go to conf directory and do the following:

      cp zoo_sample.cfg zoo.cfg

   2. Open zoo.cfg for editing and adjust the settings including the following:

      # the directory where the snapshot is stored.
      	dataDir=$ZOOKEEPER_HOME/data/
      	# the port at which the clients connects
      	clientPort=2181
      	server.1=server1:2888:3888
      	server.2=server2:2888:3888
      	server.3=server3:2888:3888
      

      Make sure the dataDir location exists and is accessible.
   3. Assign a node ID to each member that will run ZooKeeper. For example, use "1", "2" and "3" respectively for node 1, node 2 and node 3 respectively. ZooKeeper should have an odd number of instances, at least 3 in order to recover from failure.
      The node ID is specified in a field called myid under the data directory of ZooKeeper on each node. For example, on node 1, run: $ echo "1" > /zookeeper/data/myid
3. Set up ZooKeeper, so you can use it when creating the cluster with Helix:
   1. Go to the $ZOOKEEPER_HOME/bin/ directory and start ZooKeeper:

      ./zkServer.sh start

      You can check the ZooKeeper log in the $ZOOKEEPER_HOME/bin/zookeeper.out file. Check this log to ensure that the 'ensemble' (cluster) is formed successfully. One of the nodes should be elected as leader with the other two nodes following it.
4. Once the ZooKeeper ensemble is started, the next step is to configure and start Helix. Helix only needs to be configured once and from a single node. The configuration is then stored by the ZooKeeper ensemble and shared as appropriate.
   Set up the cluster with the ZooKeeper server as the master of the configuration:
   1. Create the cluster by providing the ZooKeeper Host and port as a comma separated list:

      $HELIX_HOME/bin/helix-admin.sh --zkSvr ZOOKEEPER_HOST:ZOOKEEPER_PORT --addCluster CLUSTER_NAME

   2. Add your nodes to the cluster:

      $HELIX_HOME/bin/helix-admin.sh --zkSvr ZOOKEEPER_HOST:ZOOKEEPER_PORT --addNode CLUSTER_NAME NODE_NAMEUNIQUE_ID

      Example 5.4. Adding two cluster nodes

      ./helix-admin.sh --zkSvr server1:2181,server2:2181,server3:2181 --addNode brms-cluster nodeOne:12345
      	./helix-admin.sh --zkSvr server1:2181,server2:2181,server3:2181 --addNode brms-cluster nodeTwo:12346
      	./helix-admin.sh --zkSvr server1:2181,server2:2181,server3:2181 --addNode brms-cluster nodeThree:12347
      

5. Add resources to the cluster.

   Example 5.5. Adding vfs-repo as resource

   ./helix-admin.sh --zkSvr server1:2181,server2:2181,server3:2181 --addResource brms-cluster vfs-repo 1 LeaderStandby AUTO_REBALANCE

6. Rebalance the cluster with the three nodes.

   Example 5.6. Rebalancing the brms-cluster

   ./helix-admin.sh --zkSvr server1:2181,server2:2181,server3:2181 --rebalance brms-cluster vfs-repo 3
   

   In the above command, 3 stands for three zookeeper nodes.
7. Start the Helix controller in all the nodes in the cluster.

   Example 5.7. Starting the Helix controller

   ./run-helix-controller.sh --zkSvr server1:2181,server2:2181,server3:2181 --cluster brms-cluster 2>&1 > /tmp/controller.log &

Procedure 5.1. Stopping Helix and Zookeeper

1. Stop JBoss EAP server processes.
2. Stop the Helix process that has been created by run-helix-controller.sh, for example,kill -15 <pid of HelixControllerMain>.
3. Stop ZooKeeper server using the zkServer.sh stop command.