Configuration Reference Manual

     Previous  Next    Open TOC in new window    View as PDF - New Window  Get Adobe Reader - New Window
Content starts here

Data Tier Configuration Reference (datatier.xml)

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

 


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 data tier partitions. A partition refers to one or more 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 WebLogic SIP Server domain.

 


Editing datatier.xml

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

 


XML Schema

This schema file is available at http://www.bea.com/ns/wlcp/wlss/300. The schema is also also bundled within the wlss-descriptor-binding.jar library, installed in the WL_HOME/server/lib/wlss directory.

 


Example datatier.xml File

Listing 2-1 shows the template datatier.xml file created using the Configuration Wizard. See also Example Data Tier Configurations and Configuration Files in the Configuration Guide.

Listing 2-1 Default datatier.xml File
<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>

 


XML Element Description

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

Table 2-1 Nested partition Elements
Element
Description
name
A String value that identifies the name of the partition. BEA 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 WebLogic SIP Server 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.
BEA 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."


  Back to Top       Previous  Next