WebLogic Server provides the ability to replicate HTTP session state
across multiple clusters. This improves high-availability and fault
tolerance by allowing clusters to be spread across multiple geographic
regions, power grids, and internet service providers. WebLogic Server
allows you to implement cross-cluster replication with a Metropolitan
Area Network (MAN) or Wide Area Network (WAN) depending on your
requirements and network configuration.
Before configuring cross-cluster replication using the Administration
Console, you must set up your network environment, including hardware
load balancers, WebLogic Server instances and clusters. If you are using
cross-cluster replication within a WAN environment, you must also create
and configure a data source. For more information, see Configuration Requirements for Cross-Cluster
Replication in Using WebLogic Server Clusters.
To configure cross-cluster
replication from the Administration Console:
If you have not already done so, in the Change Center of the Administration Console, click Lock & Edit (see Use the Change Center).
Administration Console, expand Environment and
Click the name
of a cluster for which you want to configure cross-cluster
Choose the type
of cross-cluster replication you want to implement.
for the following:
Remote Cluster Address: The address used to communicate with
the secondary cluster.
Replication Channel: The network channel used to communicate
with the secondary cluster.
Note: Both of these settings should be configured
so that communication between the primary and secondary cluster are
not routed through the hardware load balancers.
If you are
configureint cross-cluster replication in a WAN environment, perform
Select the Data Source for Session Persistence.
Click the Advanced tab and set the
Session Flush Interval
Session Flush Threshold
For more information on using these parameters to
configure performance within a WAN environment, see WAN
HTTP State Session Replication in Using WebLogic
To activate these changes, in the Change Center of the Administration Console, click Activate Changes. Not all changes take effect immediately—some require a restart (see Use the Change Center).