SIP Data Tier with One Partition SIP Data Tier with Two Partitions SIP Data Tier with Two Partitions and Two Replicas
4.3.1 SIP Data Tier with One Partition
A single-partition, single-server SIP data tier represents the simplest data tier configuration. Example 4–1 shows a SIP data tier configuration for a single-server deployment. Example 4–1 SIP Data Tier Configuration for Small Deployment ?xml version=1.0 encoding=UTF-8? data-tier xmlns=http:www.bea.comnswlcpwlss300 partition namepart-1name server-namereplica1server-name partition data-tier To add a replica to an existing partition, simply define a second server-name entry in the same partition. For example, the datatier.xml configuration file shown in Example 4–2 recreates a two-replica configuration. Example 4–2 SIP Data Tier Configuration for Small Deployment with Replication ?xml version=1.0 encoding=UTF-8? data-tier xmlns=http:www.bea.comnswlcpwlss300 partition namePartition0name server-nameDataNode0-0server-name server-nameDataNode0-1server-name partition data-tier4.3.2 SIP Data Tier with Two Partitions
Multiple partitions can be easily created by defining multiple partition entries in datatier.xml, as shown in Example 4–3 . Example 4–3 Two-Partition SIP Data Tier Configuration ?xml version=1.0 encoding=UTF-8? data-tier xmlns=http:www.bea.comnswlcpwlss300 partition namePartition0name server-nameDataNode0-0server-name partition partition namePartition1name server-nameDataNode1-0server-name partition data-tier4.3.3 SIP Data Tier with Two Partitions and Two Replicas
Replicas of the call state can be added by defining multiple SIP data tier servers in each partition. Example 4–4 shows the datatier.xml configuration file used to define a system having two partitions with two servers replicas in each partition. Example 4–4 SIP Data Tier Configuration for Small Deployment ?xml version=1.0 encoding=UTF-8? data-tier xmlns=http:www.bea.comnswlcpwlss300 Configuring SIP Data Tier Partitions and Replicas 4-5 partition namePartition0name server-nameDataNode0-0server-name server-nameDataNode0-1server-name partition partition namePartition1name server-nameDataNode1-0server-name server-nameDataNode1-1server-name partition data-tier4.4 Storing Long-Lived Call State Data In A RDBMS
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