Single-node Topologies OWLCS Deployment Topologies

16-10 Oracle WebLogic Communications Server Administration Guide more than one partition is used, the concurrent call state is split among the partitions, and each partition manages an separate portion of the data. For example, with a two-partition SIP state tier, one partition manages the call state for half of the concurrent calls for example, calls A through M while the second partition manages the remaining calls N through Z. In most cases, the maximum call state size that can be managed by an individual server is limited by the heap size in the Java Virtual Machine. Additional servers can be added within the same partition to manage copies of the call state data. When multiple servers are members of the same partition, each server manages a copy of the same portion of the call data, referred to as a replica of the call state. If a server in a partition fails or cannot be contacted due to a network failure, another replica in the partition supplies the call state data to the engine tier. Oracle recommends configuring two servers in each partition for production installations, to guard against machine or network failures. A partition can have a maximum of three replicas for providing additional redundancy.

16.3.1.7 Example SIP State Tier Configurations and Configuration Files

The sections that follow describe some common Oracle WebLogic Communication Services installations that utilize a separate SIP state tier.

16.3.1.7.1 SIP State Tier with One Partition A single-partition, two server SIP state tier

represents the simplest state tier configuration. For example, the datatier.xml configuration file shown in Example 16–1 creates a two-replica configuration. Example 16–1 SIP State Tier Configuration for Small Deployment with Replication ?xml version=1.0 encoding=UTF-8? data-tier xmlns=http:.... partition namePartition0name server-nameDataNode0-0server-name server-nameDataNode0-1server-name partition data-tier

16.3.1.7.2 SIP State Tier with Two Partitions Multiple partitions can be created by defining

multiple partition entries in datatier.xml, as shown in Example 16–2 . Example 16–2 Two-Partition SIP State Tier Configuration ?xml version=1.0 encoding=UTF-8? data-tier xmlns=http:.... partition namePartition0name server-nameDataNode0-0server-name partition partition namePartition1name server-nameDataNode1-0server-name partition data-tier

16.3.1.7.3 SIP State Tier with Two Partitions and Two Replicas Replicas of the call state can

be added by defining multiple SIP state tier servers in each partition. Example 16–3