|Oracle® Communications Converged Application Server Administration Guide
Part Number E17647-03
The chapter describes the SIP data tier configuration file,
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
/config/custom subdirectory where
DOMAIN_DIR is the root directory of the Oracle Communications Converged Application Server domain.
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.
This schema file is bundled within the
wlss-descriptor-binding.jar library, installed in the
Example 31-1 shows the template
datatier.xml file created using the Configuration Wizard. See also "Example SIP Data Tier Configurations and Configuration Files" in Chapter 3, "Configuring SIP Data Tier Partitions and Replicas."
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 31-0.
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."
Specifies the name of a Converged Application Server instance that manages call state in this partition. You can define up two three servers per
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."