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:
- cd AS_HOME/EAP_HOME (assume: EAP 4.3.0.GA)
- cp -r server/all server/xyz1
- cp -r server/all server/xyz2
- 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
- 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.
Rob Stryker wrote:
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 ;)
Sr. Software Maintenance Engineer
JBoss, a division of Red Hat