Fixing SOA Suite coherence clustering

During an investigation into another issue I investigated the SOA Suite 11g coherence configuration. This led me to configuring for unicast instead of the default multicast. The configuration is actually quite simple. All that is needed is to change a few parameters in the setDomainEnv.sh file.

The line EXTRA_JAVA_PROPERTIES line in the setDomainEnv.sh file should be changed to:
EXTRA_JAVA_PROPERTIES="${EXTRA_JAVA_PROPERTIES} -Dsoa.archives.dir=${SOA_ORACLE_HOME}/soa -Dsoa.oracle.home=${SOA_ORACLE_HOME} -Dsoa.instance.home=${DOMAIN_HOME} -Dtangosol.coherence.log=jdk -Dtangosol.coherence.wka1=server1.example.com -Dtangosol.coherence.wka2=server2.example.com -Dtangosol.coherence.localhost=server1.example.com -Djavax.xml.soap.MessageF actory=oracle.j2ee.ws.saaj.soap.MessageFactoryImpl -Dweblogic.transaction.blocking.commit=true -Dweblogic.transaction.blocking.rollback=true -Djavax.net.ssl.trustStore=${WL_HOME}/server/lib/ DemoTrust.jks"

This would change the default multicast configuration to a proper and recommended unicast configuration.

Another possibility is to do what is in the high availability guide. The reason I don't like doing it that way is that the end result will be that the servers will have both configurations and that could lead to misunderstandings and confusion, not to mention I'm not convinced it even works.