Note: Resin does not support clustering outside of the product. An effort was made to establish licensing to see if such a system would be worth it, but for now (and perhaps into production) we are using Jetty and Elastic Load Balancer to establish a cluster of Java Servers. This documentation is preserved here in case this is revisited in the future.
On Redhat, to build resin...
yum groupinstall "Development Tools"
yum install openssl-devel java-1.6.0-openjdk-devel java-1.6.0-openjdk
curl http://www.caucho.com/download/resin-4.0.35.tar.gz | tar xzf -C /usr/local/src -
./configure --enable-64bit --enable-ssl --with-setuid=resin --with-setgid=webservice --prefix=/opt/resin
(The following are answers to questions from make, defaults put everything in /opt/resin, and also puts an init script in /etc/init.d)
fqdn (for now): idp.commit
keystore passwd: eeYie1Fegi2Gohth
Changes in ResinProperties (need to be done with resin shut down)
# Set a global password to prevent foreign Resin instances from connecting.
# Must be identical between web, app, and cache clusters.
cluster_system_key : Ohthoo8xooZai2oofeinoo3Mohp5Chae
# Enable remote admin (for remote CLI and for EC2 ext: triad discovery)
remote_admin_enable : true
...also need to link (or find better way) of putting idp/lib/endorsed in /opt/resin/endorsed
resinadmin password: Baitaf3txoe0Uumi