JBoss Application Server servers can be grouped together into a cluster for performance or to provide high availability. This guide provides only minimal instructions for setting up a JBoss Application Server cluster.
Because JBoss Application Server clusters do not have an administrative server, you will choose a single JBoss Application Server on which to install and configure the first instance of Content Platform Engine, then copy the necessary files to the rest of the nodes in the cluster.
In a highly available JBoss cluster environment Application Engine and Content Platform Engine must reside in separate JBoss clusters. Unless given a unique name, all JBoss nodes will be part of the cluster "Default."
To
effectively run load balancing tasks, all instances of the Content Platform Engine must
reside in a single JBoss cluster. EJB load balancing cannot span multiple
JBoss clusters.
For each Application Engine node, uniquely name the cluster something other than default.
JBOSSSH=${JBOSSSH:-"$JBOSS_HOME/bin/run.sh -c $JBOSS_CONF -b $JBOSS_HOST"}
toJBOSSSH=${JBOSSSH:-"$JBOSS_HOME/bin/run.sh -c $JBOSS_CONF -b $JBOSS_HOST"}
-Djboss.partition.name=JBossP8AE