SIP Data Tier with One Partition SIP Data Tier with Two Partitions SIP Data Tier with Two Partitions and Two Replicas

4-4 Oracle WebLogic SIP Server Container Administrators Guide

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-tier

4.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-tier

4.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-tier

4.4 Storing Long-Lived Call State Data In A RDBMS