The following sections provide a complete reference to the SIP data tier configuration file, 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 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 WLSS_HOME/server/lib/wlss
directory.
Listing 2-1 shows the template datatier.xml
file created using the Configuration Wizard. See also
Example SIP Data Tier Configurations and Configuration Files in the Configuration Guide.
<st:data-tier xmlns:st=”http://bea.com/wcp/sip/management/internal/webapp”>
<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>
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 2-1.