<p>Optimizes cross-cluster replication for the type of network
that servers in the clusters use for administrative communication.</p>
<p>To enhance the reliability of HTTP sessions, you can
configure servers in one cluster to replicate the session data
to servers in a different cluster. In such an environment,
configure the clusters to be one of the following types:</p>
<ul>
<li><code>man</code>
<p>if the clustered servers can send their data through a metro
area network (man) in which latency is negligible. With this
ClusterType value, servers replicate session state synchronously
and in memory only. For example, when serverA in cluster1 starts an
HTTP session, its backup server, serverB in cluster2, immediately
replicates this session in memory to Server B.</p>
</li>
<li><code>wan</code>
<p>if the clusters are far apart or send their data through a wide
area network (wan) that experiences significant network latency.
With this ClusterType value, a server replicates session state
synchronously to the backup server in the same cluster and
asynchronously to a server in the remote cluster. For example, when
serverA in cluster1 starts an HTTP session, it sends the data to
serverB in cluster1 and then asynchronously sends data to serverX
in cluster 2. ServerX will persist the session state in the
database.</p>
<p>If you persist session data in a replicating database, and if you prefer
to use the database to replicate the data instead of WebLogic Server,
choose a cluster type of <code>wan</code> and leave the
remote cluster address undefined. WebLogic Server saves the session data
to the local database and assumes that the database replicates data
as needed.</p>
</li>
</ul>
(Interface=weblogic.management.configuration.ClusterMBean Attribute=getClusterType)