Anyone who is running 20 or so instances of JBoss in any corporation's enterprise environment knows that configuring JBoss to run 10 different cluster partitions, sometimes on a single machine, can be a bit tedious. So, I've written this little script which configures your JBoss cluster for you.
Included in the download is two different versions of JBoss, 3.2.3 and 3.2.5. As new release branches are made available I will include them in the JBossConfigurator.tar.gz in order to allow you to choose which version of JBoss you would like to deploy.
It is a very simple script which uses modified jboss-x.x.x.tar.gz downloads from jboss.org. I've gone through the trouble of changing all those little places in all the XML files which need to be customized to change the partition name from DefaultPartition to whatever you specify when prompted by the script. Also, I replace all the spots in the XML which refer to 'localhost' or anything else which will screw up a multi-homed installation. This makes it terribly easy to run multiple instances of JBoss on a single machine which is sometimes needed in dev environments where you have multiple teams of developers working on multiple JBoss projects. For example, you can add virtual interfaces to your Unix box, then generate JBoss installs for each IP or a cluster of JBoss installs for virtual IPs on a single machine.
The script will ask you for an installation directory where you plan on placing your install. Just make this the parent directory (this instruction, along with all the others is printed on the terminal as you run the script). It will also ask you for the name of the project, the name of the partition, and all the IPs for the members of the cluster. It will then generate a JBoss install for each member of the cluster, identified by the filename under the ./deployments directory which is created during the run.
As I said, all this information is displayed on the terminal. Guinea pigs who have used this don't seem to have problems with it, but I'm releasing this to the world to see what people think. It's a big download (96M) as it includes two complete JBoss distros. In the future, I'll just be using patches to the default install.
Make sure you use the generated start scripts in the $JBOSS/bin dir as they set the IP of your cluster member to be used by the run.sh.
By the way, this is written in bash. Windows users: Too bad, so sad.
I'm very interested to see what other people do to make their JBoss installs easy in large enterprise environments where there are dozens of JBoss boxen and countless developers. Please send me feedback at damon at sicore.org
Here it is: Right Here.