General install and deployment problem with WLS clustering
on two boxes

Hi,

I've come across a general installation problem with WLS with a cluster spanning
two different physical machines and two Managed Servers, one Managed Server per
physical machine.

The problem is, starting from scratch, you install WLS on both physical
machines. You can then use the config wizard to create the domain, cluster and
managed servers, but this is a manual typing in process.

So we've now got a WLST Script which we run with "java weblogic.WLST
domaincreate.py domain.properties". This is good as it creates the domain,
cluster, managed servers and JMS modules.

Now the trouble is, it doesn't do anything to the 2nd physical machine which
will be running only the 2nd Managed Server. 

One dirty way to get around this in order to start the 2nd managed server was to
copy the domain directory to the 2nd server, but I'm sure this is bad practice
and what you can actually do is improve the WLST script to actually, but the
same as the config wizard and dump the nessary information to the 2nd physical
machine in order so you don't need to copy the domain directory across so that
it will startup straight after running the WLST.


Any help appriecated.