Getting Connections with Clustered JDBC
Failover and Load Balancing for JDBC Connections
Multicast and Cluster Configuration
If Your Cluster Spans Multiple Subnets In a WAN
Firewalls Can Break Multicast Communication
Do Not Share the Cluster Multicast Address with Other Applications
Considerations When Using Unicast
Pure-Java Versus Native Socket Reader Implementations
Configuring Reader Threads for Java Socket Implementation
Determining Potential Socket Usage
Deploy Homogeneously to Avoid Cluster-Level JNDI Conflicts
WebLogic Server Supports “Relaxed Deployment” Rules
Deployment to a Partial Cluster is Allowed
Deploying to Complete Clusters in WebLogic Server
Pinned Services can be Deployed to Multiple Managed Servers.
How Session Connection and Failover Work with a Proxy Plug-in
Load Balancer Configuration Requirements
Load Balancers and the WebLogic Session Cookie
Related Programming Considerations
How Session Connection and Failover Works with a Load Balancer
Server Affinity and Initial Context
Server Affinity and IIOP Client Authentication Using CSIv2
Round-Robin Affinity, Weight-Based Affinity, and Random-Affinity
Example 1—Context from cluster
Example 2—Server Affinity and Failover
Example 3—Server affinity and server-to-server connections
Requirements for HTTP Session State Replication
Supported Server and Proxy Software
Programming Considerations for Clustered Servlets and JSPs
Using URL Rewriting to Track Session Replicas
Connection with Load Balancing Hardware
Failover with Load Balancing Hardware
Network Requirements for Cross-cluster Replication
Configuration Requirements for Cross-Cluster Replication
Configuring Session State Replication Across Clusters
Configuring a Replication Channel
MAN HTTP Session State Replication
MAN Replication, Load Balancers, and Session Stickiness
WAN HTTP Session State Replication
Failover Scenarios Within a WAN
Database Configuration for WAN Session State Replication
Failover for Stateful Session EJBs
Failover for Entity Beans and EJB Handles
Startup Process in a Cluster with Migratable Servers
Administration Server’s Role in Whole Server Migration
Migratable Server Behavior in a Cluster
Node Manager’s Role in Whole Server Migration
Cluster Master’s Role in Whole Server Migration
Messaging/JMS-related Services
JTA Transaction Recovery Service
User-defined Singleton Services
User-Preferred Servers and Candidate Servers
Targeting Rules for JMS Servers
Targeting Rules for SAF Agents
Re-targeting SAF Agents to Migratable Targets
Targeting Migratable SAF Agents For Increased Message Throughput
Targeting SAF Agents For Consistent Quality-of-Service
Targeting Rules for Path Service
Special Considerations For Targeting a Path Service
Targeting Rules for Custom Stores
Migratable Targets For the JTA Transaction Recovery Service
Leasing for Migratable Services
How Health Monitoring of the JTA Transaction Recovery Service Triggers Automatic Migration
Configuring a Migratable Server As a Migratable Target
Create a New Migratable Target
Optionally Select Constrained Candidate Servers
Optionally Specify Pre/Post-Migration Scripts
Special Considerations When Targeting SAF Agents or Path Service
Select the Automatic JTA Migration Check Box
Optionally Select Candidate Servers
Optionally Specify Pre/Post-Migration Scripts
Packaging and Deploying a Singleton Service Within an Application
Deploying a Singleton Service As a Standalone Service in WebLogic Server
Configuring Singleton Service Migration
Physical Hardware and Software Layers
Firewall Between Proxy Layer and Cluster
DMZ with Basic Firewall Configurations
Combining Firewall with Load Balancer
Expanding the Firewall for Internal Clients
DMZ with Two Firewall Configuration
WebLogic Server Instances on Multi-CPU machines
Check Host Machines’ Socket Reader Implementation
Setting Up a Cluster on a Disconnected Windows Machine
Avoiding Listen Address Problems
When Internal and External DNS Names Vary
Assigning Names to WebLogic Server Resources
Administration Server Address and Port
Managed Server Addresses and Listen Ports
Cluster Multicast Address and Port
Multicast and Multiple Clusters
Multicast and Multi-Tier Clusters
Explicitly Defining Cluster Address for Production Environments
Explicitly Defining Cluster Address for Development and Test Environments
Explicitly Defining Cluster Address for Single, Multihomed Machine
Starting a WebLogic Server Cluster
Proxy Servlet Deployment Parameters
Accessing Applications Via the Proxy Server
Deploying to a Single Server Instance (Pinned Deployment)
Pinned Deployment from the Command Line
Cancelling Cluster Deployments
Cancel Deployment from the Command Line
Cancel Deployment Using the Administration Console
Undeploying Deployed Applications
Deploying JMS to a Migratable Target Server Instance
Activating JTA as a Migratable Service
Migrating a Pinned Service to a Target Server Instance
Migrating When the Currently Active Host is Unavailable
Configure Native IP Sockets Readers on Machines that Host Server Instances
Set the Number of Reader Threads on Machines that Host Server Instances
Set the Number of Reader Threads on Client Machines
Configure Multicast Time-To-Live (TTL)
Configure Multicast Buffer Size
Configure Multicast Data Encryption
Configuration Notes for Multi-Tier Architecture
Session Facades Reduce Remote Calls
Transfer Objects Reduce Remote Calls
Distributed Transactions Increase Remote Calls
Cluster-Related Configuration Options
Getting a JRockit Thread Dump Under Linux
Setting Debug Flags on the Command Line
Setting Debug Flags by Using weblogic.Admin