In order to make riftsaw to be able to work in a clustering environment, it has to be configured to a shared database for all the nodes that among the clustering environment, because riftsaw persists all of process states into database. For the frontend, it needs a load balancer to dispatch the soap message into nodes properly.Below is the picture of riftsaw server deployment architecture for clustering.
In the $riftsaw/install folder, if you set the org_jboss_as_config=all in the deployment.properties,
it will deployed riftsaw-clustering libraries and files into JBoss AS. If you want to deploy the riftsaw clustering feature into other config, say like you copied 'all' into 'node1',
you can run the following command, (which basically added '-Dclustering.support=true').
ant deploy -Dclustering.support=true
Note
Please be noted that the riftsaw clustering support depends on the JBoss AS Clustering's HAPartitionService, so please be sure that you have this service started if you use some customized config for JBoss AS.
Deploying bpel artifact in clustering environment is different from deploying it into a single server.
You have to copy your bpel artifact (say hello_world.jar) into $JBossAS/server/$config (like all)/farm/,
any artifacts deployed in this folder will be copied into all nodes that in the clustering environment.