Load Balancer Oracle Fusion Middleware Online Documentation Library
7.2 Load Balancer
Although it is not provided as part of the Oracle WebLogic Server SIP Container product, a load balancer or multiple load balancers is an essential component of any production Oracle WebLogic Server SIP Container installation. The primary goal of a load balancer is to provide a single public address that distributes incoming SIP requests to available servers in the Oracle WebLogic Server SIP Container engine tier. Distribution of requests ensures that Oracle WebLogic Server SIP Container engines are fully utilized. Most load balancers have configurable policies to ensure that client requests are distributed according to the capacity and availability of individual machines, or according to any other load policies required by your installation. Some load balancers provide additional features for managing SIP network traffic, such as support for routing policies based on source IP address, port number, or other fields available in SIP message headers. Many load balancer products also provide additional fault tolerance features for telephony networks, and can be configured to consistently route SIP requests for a given call to the same engine server on which the call was initiated. In a Oracle WebLogic Server SIP Container installation, the load balancer is also essential for performing maintenance activities such as upgrading individual servers Oracle WebLogic Server SIP Container software or hardware or upgrading applications without disrupting existing SIP clients. The Administrator modifies load balancer policies to move client traffic off of one or more servers, and then performs the required upgrades on the unused server instances. Afterwards, the Administrator modifies the load balancer policies to allow client traffic to resume on the upgraded servers. Oracle provides detailed information for setting up load balancers with the Oracle WebLogic Server SIP Container engine tier for basic load distribution. See Section 3.2, Oracle WebLogic Server SIP Container Base Platform Topologies 7-3 Configuring Load Balancer Addresses to configure a load balancer used with Oracle WebLogic Server SIP Container.7.3 Engine Tier
Parts
» Oracle Fusion Middleware Online Documentation Library
» Starting and Stopping Servers
» Administration Server Best Practices
» Common Configuration Tasks Shared Configuration Tasks
» Locking and Persisting the Configuration
» Managing Configuration Locks Locating the Oracle WebLogic Server SIP Container MBeans
» Configuring Timer Affinity Optional Configuring NTP for Accurate SIP Timers
» Creating a New SIP or SIPS Channel
» Configuring Custom Timeout, MTU, and Other Properties
» DNS Server Configurations Overview DNS Servers Listening On All Addresses IP_ANY
» Understanding the Route Resolver IP Aliasing with DNS Hardware
» IP Masquerading Alternative to Source NAT If you choose not to enable source
» NAT-based configuration Load Balancer Configuration
» maddr-Based Configuration Load Balancer Configuration
» rport-Based Configuration Load Balancer Configuration
» Configure JDBC Resources Configure Oracle WebLogic Server SIP Container Persistence Options
» Example Domain Configurations Requirements and Limitations
» Installing and Configuring the Primary Site Installing the Secondary Site
» Configuring JMS Resources Secondary Site Only
» Call State Replication Process Call State Processing After Failover
» Troubleshooting Geographical Replication Using Geographically-Redundant SIP Data Tiers
» Enabling Automatic Configuration Backups Storing the Domain Configuration Offline
» WlssEchoServer Failure Detection Forced Shutdown for Failed Replicas
» Starting WlssEchoServer on SIP Data Tier Server Machines
» Data Collection and Logging Watches and Notifications
» Configuring Server-Scoped Monitors Instrumentation
» Using XML Documents to Specify Logging Criteria
» Using Servlet Parameters to Specify Logging Criteria
» Enabling Log Rotation and Viewing Log Files trace-pattern.dtd Reference
» Steps for Configuring Diameter Client Nodes and Relay Agents Installing the Diameter Domain
» Creating a New Node Configuration General Node Configuration
» Configuring the Sh Client Application
» Configuring the Sh and Rf Simulator Applications Enabling Profile Service using an Sh backend
» Configuring Peer Nodes Configuring Routes
» Enabling the Diameter Console Extension Example Domain Configuration
» Load Balancer Oracle Fusion Middleware Online Documentation Library
» Example of Writing and Retrieving Call State Data RDBMS Storage for Long-Lived Call State Data
» Engine Tier Geographically-Redundant Installations
» Example Hardware Configurations Alternate Configurations
» Overview of SIP Application Upgrades
Show more