Thanks for reply, The current round of clients we are picking up is coming over from WebLogic and they would like to have a built in GUI to do this across a cluster, so that if they set the port in one place it would be identical for everyone in the cluster. Here are use cases I see frequently in the field. 1) Standard cluster. One or more machines on same subnet in a cluster. a) With or without load balancer configuration required. b) With and without Http Clustering in Tomcat/JBossWeb c) With and without Cache Clustering d) With and without EJB Clustering 2) "Cross Cluster" multiple instances per machine with multiple JBoss clusters across a group of machines. a) Same set. One option would be a script to setup a cluster selecting what you wanted to cluster and how (sync vs async, replication vs invalidation, etc). Then be able to run that on other machines having it change the nodeId for load balancer. Another use case would be for it to set the MaxClients, ping mode, etc in Apache and set the appropriate MaxThreads in Tomcat/JBossWeb/JBoss. Robb Greathouse JBoss CELL 505-480-4639 OFFICE 505-255-2652 FAX 505-554-2834 ----- Original Message ----- From: "Galder Zamarreno" <galder.zamarreno(a)redhat.com&gt; To: "Rob Stryker" <rob.stryker(a)redhat.com&gt; Cc: jbosstools-dev(a)lists.jboss.org Sent: Sunday, May 17, 2009 12:52:03 PM GMT -06:00 Central America Subject: [jbosstools-dev] Re: Cluster Feature Collecting Hey Rob, Sorry I never replied to this email. I've been meaning to do so but keep having to do other things. So, let me explain all the steps I have to do to create a cluster and have it ready to run a test: Command line: - cd AS_HOME/EAP_HOME (assume: EAP 4.3.0.GA) - cp -r server/all server/xyz1 - cp -r server/all server/xyz2 Open JBDS: - Create a new runtime and server for xyz1, give it a name: eap-4.3.0.ga-xyz1 and add bind address localhost2 - Create a new runtime and server for xyz2 and give it a name: eap-4.3.0.ga-xyz2, add bind address localhost3 and give it a different JBoss Messaging server Id. - Deploy your apps in xyz1 and xyz3 As you can see, if you wanna create a simple cluster for testing, it takes a fair few clicks and operations to get it done. I envision eventually having some wizard or GUI window from where you could basically do all this in one go: - Select EAP/AS home. - Select number of configs to cluster, i.e. 2 - Give names to these X number of configs: - Give bind addresses (or select service binding port configs) for each config. - Optionally give some special system properties to each, i.e. JBoss Messaging server id. - What deployments go in each server. Underneath, this would do what I know have to do manually. Thoughts? Rob Stryker wrote: > Hi All: > > I'd like to hear any and all clustering use cases relevant to tooling > that any of you have run into. Whether it be creating multiple servers / > runtimes / profiles, actions you'd like supported on a cluster type node > in the view, anything you can imagine. Spit it out. Speak up. Or > forever hold your peace ;) >