B SIP Data Tier Configuration Reference

The following sections provide a complete reference to the SIP data tier configuration file, datatier.xml:

Section B.1, "Overview of datatier.xml"
Section B.2, "Editing datatier.xml"
Section B.3, "XML Schema"
Section B.4, "Example datatier.xml File"
Section B.5, "XML Element Description"

B.1 Overview of datatier.xml

The datatier.xml configuration file identifies servers that manage the concurrent call state for SIP applications, and defines how those servers are arranged into SIP data tier partitions. A partition refers to one or more SIP data tier server instances that manage the same portion of the call state. Multiple servers in the same partition are referred to as replicas because they all manage a copy of the same portion of the call state.

datatier.xml is stored in the DOMAIN_DIR/config/custom subdirectory where DOMAIN_DIR is the root directory of the Oracle WebLogic Communication Services domain.

B.2 Editing datatier.xml

You can edit datatier.xml using either the Administration Console or a text editor. Note that changes to the SIP data tier configuration cannot be applied to servers dynamically; you must restart servers in order to change SIP data tier membership or reconfigure partitions.

B.3 XML Schema

This schema file is bundled within the wcp-sipserver.xsd library, installed in the WLSS_HOME/server/lib/wlss directory.

B.4 Example datatier.xml File

Example B-1 shows the template datatier.xml file created using the Configuration Wizard.

Example B-1 Default datatier.xml File

<st:data-tier xmlns:st="http://www.bea.com/ns/wlcp/wlss/300">
 <st:partition>
   <st:name>partition-0</st:name>
   <st:server-name>replica1</st:server-name>
   <st:server-name>replica2</st:server-name>
 </st:partition>
</st:data-tier>

B.5 XML Element Description

datatier.xml contains one or more partition elements that define servers' membership in a SIP data tier partition. All SIP data tier clusters must have at least one partition. Each partition contains the XML elements described in Table B-0.

Table B-1 Nested partition Elements

Element Description

Element	Description
name	A String value that identifies the name of the partition. Oracle recommends including the number of the partition (starting at 0) in the text of the name for administrative purposes. For example, "partition-0."
server-name	Specifies the name of a Oracle WebLogic Communication Services instance that manages call state in this partition. You can define up two three servers per `partition` element. Multiple servers in the same partition maintain the same call state data, and are referred to as replicas. Oracle recommends including the number of the server (starting with 0) and the number of the partition in the server name for administrative purposes. For example, "replica-0-0."

name

A String value that identifies the name of the partition. Oracle recommends including the number of the partition (starting at 0) in the text of the name for administrative purposes. For example, "partition-0."

server-name

Specifies the name of a Oracle WebLogic Communication Services instance that manages call state in this partition. You can define up two three servers per partition element. Multiple servers in the same partition maintain the same call state data, and are referred to as replicas.

Oracle recommends including the number of the server (starting with 0) and the number of the partition in the server name for administrative purposes. For example, "replica-0-0."