Proxy Registrar Oracle Fusion Middleware Online Documentation Library

15 Oracle WebLogic Communication Services Base Platform Topologies 15-1 15 Oracle WebLogic Communication Services Base Platform Topologies The following sections provide an overview of the Oracle WebLogic Communication Services architecture and deployment topologies: ■ Section 15.1, Goals of the Oracle WebLogic Communication Services Base Platform ■ Section 15.2, Load Balancer ■ Section 15.3, Engine Tier ■ Section 15.4, SIP Data tier ■ Section 15.5, Geographically-Redundant Installations ■ Section 15.6, Example Hardware Configurations ■ Section 15.7, Alternate Configurations

15.1 Goals of the Oracle WebLogic Communication Services Base Platform

Oracle WebLogic Communication Services is designed to provide a highly scalable, highly available, performant server for deploying SIP applications. OWLCS is used for deploying any JSR 289 compliant SIP applications. For supported topologies for all the services in OWLCS, see Chapter 16, Deployment Topologies for Communication Services . The Oracle WebLogic Communication Services architecture is simple to manage and easily adaptable to make use of available hardware. The basic architecture consists of these components: ■ Section 15.2, Load Balancer ■ Section 15.3, Engine Tier ■ Section 15.4, SIP Data tier Figure 15–1 shows the components of a basic Oracle WebLogic Communication Services installation. The sections that follow describe each component of the architecture in more detail. 15-2 Oracle WebLogic Communications Server Administration Guide Figure 15–1 Oracle WebLogic Communication Services Architecture

15.2 Load Balancer

Although it is not provided as part of the Oracle WebLogic Communication Services product, a load balancer or multiple load balancers is an essential component of any production Oracle WebLogic Communication Services 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 Communication Services engine tier. Distribution of requests ensures that Oracle WebLogic Communication Services 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 Communication Services installation, the load balancer is also essential for performing maintenance activities such as upgrading individual servers Oracle WebLogic Communication Services 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 Communication Services engine tier for basic load distribution. See