complexType "servers"
Namespace:
http://www.terracotta.org/config
Content:
complex, 3 elements
Defined:
globally in terracotta-4.xsd, see XML source
Includes:
definitions of 3 elements
Used:
at 1 location
XML Representation Summary
<...>
   
Content: 
server*, ha?, update-check?
</...>
Content Elements (3):
ha (type ha),
server (type server),
update-check (type update-check)
All Direct / Indirect Based Elements (1):
servers (type servers)
Known Usage Locations
Annotation
This section defines the servers present in your Terracotta system. You can omit this section entirely, in which case it behaves as if there's a single server with all values set at their default. You can include exactly one server entry here (the common case), or, if you're going to run multiple servers for failover, you can include multiple servers here. If you include more than one server here, note that each server will need to know which configuration it should use as it starts up. If you name your servers according to the host that they run on (and no host contains more than one server), then they will find the hostname themselves and work automatically. If you name your servers in any other fashion (and, again, only if there is more than one 'server' element present here), then you will need to pass the command-line option "-n <name> " to the start-tc-server script, passing it the name of a server configuration from this file.
XML Source
<xs:complexType name="servers">
<xs:annotation>
<xs:documentation>
This section defines the servers present in your
Terracotta system. You can omit this section entirely, in
which case it behaves as if there's a single server with
all values set at their default. You can include exactly
one server entry here (the common case), or, if you're
going to run multiple servers for failover, you can
include multiple servers here.

If you include more than one server here, note that each
server will need to know which configuration it should use
as it starts up. If you name your servers according to the
host that they run on (and no host contains more than one
server), then they will find the hostname themselves and
work automatically.

If you name your servers in any other fashion (and, again,
only if there is more than one 'server' element present
here), then you will need to pass the command-line option
"-n
<![CDATA[
<name>
]]>
" to the start-tc-server script, passing it the name of a
server configuration from this file.
</xs:documentation>
</xs:annotation>
<xs:sequence maxOccurs="1">
<xs:sequence>
<xs:element maxOccurs="unbounded" minOccurs="0" name="server" type="server"/>
</xs:sequence>
<xs:element maxOccurs="1" minOccurs="0" name="ha" type="ha"/>
<xs:element maxOccurs="1" minOccurs="0" name="update-check" type="update-check"/>
</xs:sequence>
</xs:complexType>
Content Element Detail
ha
Type:
ha, complex content
Defined:
locally, within this complexType
XML Source
<xs:element maxOccurs="1" minOccurs="0" name="ha" type="ha"/>
server
Type:
server, complex content
Defined:
locally, within this complexType
XML Source
<xs:element maxOccurs="unbounded" minOccurs="0" name="server" type="server"/>
update-check
Type:
update-check, complex content
Defined:
locally, within this complexType
XML Source
<xs:element maxOccurs="1" minOccurs="0" name="update-check" type="update-check"/>
XML Schema documentation generated with DocFlex/XML (Kit) v1.6.2
DocFlex/XML is a powerful template-driven documentation and report generator from any data stored in XML files. Based on an innovative technology developed by FILIGRIS WORKS, this new tool offers virtuoso data querying and formatting capabilities not found in anything else!
Need to convert your XML data into a clear nice-looking documentation or reports? Web-ready hypertext HTML or printable MS Word / OpenOffice.org friendly RTF? DocFlex/XML may be a cheap, quick and effective solution exactly for this task!
Have questions? Not sure how to use it? Just send us e-mail to contact@filigris.com and we are always happy to help you! See also our services at www.filigris.com