WebLogic Server clusters form a loosely-federated group of managed servers that provide a model for applications to leverage for achieving scalability, load balancing, and failover. Each managed server manages its view of what servers are in the cluster and its own cluster-wide view of the JNDI tree. The cluster uses a messaging model for members of the cluster to exchange the information required to keep the cluster in sync. WebLogic Server supports two different cluster messaging protocols, known as unicast and multicast. This blog entry describes the two different cluster messaging protocols and makes recommendations around selecting which protocol to use for all versions of WebLogic Server up to and including WLS 12c (12.1.x).
WebLogic Server Clustering Fundamentals
Most features of WebLogic Server clustering are targeted at providing scalability, high availability, and failover capabilities to specific application component types (e.g., web applications, EJBs, JMS). To support these capabilities, WebLogic Server clustering provides some infrastructure services upon which all of the other features rely. The two most important services are: Read the full article here.
For regular information become a member in the WebLogic Partner Community please visit: http://www.oracle.com/partners/goto/wls-emea ( OPN account required). If you need support with your account please contact the Oracle Partner Business Center.