Clusters: Configuration: Replication
Configuration Options Advanced Configuration Options Related Tasks Related Topics
This page is used to configure how WebLogic Server will replicate HTTP Session State across a cluster.
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.
Name Description Cross-cluster Replication Type
Optimizes cross-cluster replication for the type of network that servers in the clusters use for administrative communication.
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:
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.
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.
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
wanand 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.
Remote Cluster Address
Set the foreign cluster. Cluster infrastructure uses this address to connect to foreign cluster for HTTP Session WAN/MAN failover.
The channel name to be used for replication traffic. Cluster infrastructure uses this channel to send updates for HTTP sessions and stateful session beans. If none is set then the default channel will be used.
In order for this feature to work, the named channel must exist on all members of the cluster and must be configured to use the same protocol. It is valid for the selected channel to be configured to use a secure protocol.
Data Source For Session Persistence
To support HTTP Session failover across data centers, a datasource is required to dump session state on disk.
Secure Replication Enabled
Servers in a cluster replicate session data. If a replication channel is defined then the session data will be sent using the replication channel protocol and secured replication settings will be ignored. If no replication channel is defined and secured replication is enabled then session data for in-memory replication will be sent over SSL using the default secured channel. However, this added security for replication traffic comes with a significant cluster performance degradation. It should only be enabled if security is of greater concern than performance degradation.
Advanced Configuration Options
Name Description Session Flush Interval
Interval in seconds until HTTP Sessions are periodically flushed to the backup cluster to dump session state on disk.
Session Flush Threshold
When number of sessions to be flushed reaches this threshold limit, sessions will be flushed to the backup cluster before the flush interval. This helps the server to flush sessions faster under load.
Persist Sessions On Shutdown
When shutting down servers, sessions are not updated. If the primary and secondary servers of a session are shut down with no session updates, the session will be lost. Turning on PersistSessionsOnShutdown will save any active sessions to the database specified in ClusterMBean#getDataSourceForSessionPersistence() when a server is shutdown. The sessions will not be written at any other time. (For example, they are not saved via this mechanism if there is a server crash.)
This attribute is applicable both to session persistence on server shutdown or session persistence across a WAN.
Rolling upgrade can potential have a bad interaction with traditional in-memory session replication. As managed servers are shutdown and upgraded, in-memory servlet sessions will be lost if both primary and secondary are rebooted before a new request arrives for the session.
Inter-Cluster Comm Link Health Check Interval
If the cluster link between two clusters goes down, a trigger will run to periodically to see if the link is restored. The duration is specified in milliseconds.
Enable Replication Timeout
Indicates if timeout should be applied to session replication calls.
Enable One Way RMI For Replication
Indicates if one-way RMI is being used for replication. One-way RMI also requires configuring replication ports on each server in the cluster.
Enable Lazy Session Deserialization
Enables increased efficiency with session replication. Enabling this attribute should be used only when configuring a WebLogic domain for Oracle Exalogic. For more information, see "Enabling Exalogic-Specific Enhancements in Oracle WebLogic Server 11g Release 1 (10.3.4)" in the Oracle Exalogic Deployment Guide.
- Configure clusters
- Configure server migration in a cluster
- Configure cross-cluster replication
- Configure HTTP settings for a cluster
- Create JDBC generic data sources