Netscape ENTERPRISE SERVER 6.1, Manual

Page: 292 / 373

The server.xml File
292 Netscape Enterprise Server NSAPI Programmer’s Guide • April 2002 (Draft)
For example, the following code defines the
VSCLASS
(or virtual server class)
element. The first line specifies that a
VS
element can contain
VARS
,
VS
, or
QOSPARAMS
elements (if this element could not contain other elements, you would
see
EMPTY
instead of a list of element names in parentheses). The remaining lines
specify that a
VSCLASS
element can contain
id
,
connections
,
objectfile
, or
rootobject
attributes, but only the
id
attribute is required.
<!ELEMENT VSCLASS (VARS?,VS*,QOSPARAMS?)>
<!ATTLIST VSCLASS
id ID #REQUIRED
objectfile CDATA #IMPLIED
rootobject CDATA #IMPLIED
acceptlanguage (yes|no|on|off|1|0) #IMPLIED
Labels such as
ID
and
CDATA
are XML data types. For more information about
XML, see the XML specification at:
http://www.w3.org/TR/REC-xml
The server.xml File
The
server.xml
file configures the addresses and ports that the server listens on
and assigns virtual servers to these listen sockets. The encoding is UTF-8 to
maintain compatibility with regular UNIX text editors. The
server.xml
file is
located in the server_root
/https
-server_id
/config
directory.
Here is a simple
server.xml
file. It contains two listen sockets (
LS
), two virtual
server classes (
VSCLASS
), and three virtual servers (
VS
).
<?xml version="1.0" encoding="UTF-8"?>
<!-- declare any variables to be used in the server.xml file in the
ATTLIST below -->
<!DOCTYPE SERVER SYSTEM "server.dtd" [
<!ATTLIST VARS
docroot CDATA #IMPLIED
adminusers CDATA #IMPLIED
webapps_file CDATA #IMPLIED
webapps_enable CDATA #IMPLIED
accesslog CDATA #IMPLIED
user CDATA #IMPLIED
group CDATA #IMPLIED
chroot CDATA #IMPLIED
dir CDATA #IMPLIED