About This Guide
This guide discusses the purpose and use of
the
configuration files for Sun™ Open Net Environment (Sun ONE) Web Server
6.1,
including server.xml, magnus.conf,
and mime.types, and provides comprehensive
lists
of the elements and directives in these configuration files.
This preface contains information about the
following
topics:
Who Should Use This Guide
The intended audience for this guide is the
person
who administers and maintains the Sun ONE Web Server.
This guide assumes you are familiar with the
following
topics:
- J2EE specification
- HTTP
- HTML
- XML
- Java programming
- Java APIs as defined in servlet, JSP,
and
JDBC specifications
- Relational database concepts
Using the Documentation
The Sun ONE Web Server manuals are available
as
online files in PDF and HTML formats at:
http://docs.sun.com/prod/sunone
The following table lists the tasks and
concepts
described in the Sun ONE Web Server manuals.
Table 1 Sun
ONE Web Server Documentation Roadmap
For Information About
|
See the Following
|
Late-breaking information about the
software
and documentation
|
Release Notes
|
Getting started with Sun ONE Web Server,
including
hands-on exercises that introduce server basics and features
(recommended
for first-time users)
|
Getting Started
Guide
|
Performing installation and migration
tasks:
- Installing Sun ONE Web Server
and
its various components, supported platforms, and environments
- Migrating from Sun ONE Web
Server
4.1 or 6.0 to Sun ONE Web Server 6.1
|
Installation and
Migration
Guide
|
Performing the following administration
tasks:
- Using the Administration and
command-line
interfaces
- Configuring server preferences
- Using server instances
- Monitoring and logging server
activity
- Using certificates and public
key
cryptography to secure the server
- Configuring access control to
secure
the server
- Using Java™ 2 Platform,
Enterprise
Edition (J2EE™ platform) security features
- Deploying applications
- Managing virtual servers
- Defining server workload and
sizing
the system to meet performance needs
- Searching the contents and
attributes
of server documents, and creating a text search interface
- Configuring the server for
content
compression
- Configuring the server for web
publishing
and content authoring using WebDAV
|
Administrator’s
Guide
|
Using programming technologies and APIs
to
do the following:
- Extend and modify Sun ONE Web
Server
- Dynamically generate content in
response
to client requests
- Modify the content of the server
|
Programmer’s Guide
|
Creating custom Netscape Server
Application
Programmer’s Interface (NSAPI) plugins
|
NSAPI
Programmer’s Guide
|
Implementing servlets and JavaServer
Pages™
(JSP™) technology in Sun ONE Web Server
|
Programmer’s
Guide to
Web Applications
|
Editing configuration files
|
Administrator’s
Configuration
File Reference Guide
|
Tuning Sun ONE Web Server to optimize
performance
|
Performance
Tuning,
Sizing, and Scaling Guide
|
How This Guide Is Organized
This guide has the following chapters:
This chapter introduces the major
configuration
files that control the Sun ONE Web Server and describes how to activate
and
edit them.
This chapter discusses the server.xml file, which controls most aspects of
server
operation.
This chapter discusses the directives you
can
set in the magnus.conf file to configure
the Sun
ONE Web Server during initialization.
This chapter discusses the MIME types
file,
which maps file extensions to file types.
This chapter lists other important
configuration
files and provides a quick reference of their contents.
This appendix describes the changes in
configuration
files between the 4.x and 6.1
versions
of Sun ONE Web Server.
This appendix describes the changes in
configuration
files between the 6.0 and 6.1 versions of Sun ONE Web Server.
This chapter provide an alphabetical list
for
easy lookup of elements in server.xml and
directives
in magnus.conf.
Documentation Conventions
This section describes the types of
conventions
used throughout this guide:
- File and directory
paths
are given in UNIX® format (with forward slashes separating
directory
names). For Windows versions, the directory paths are the same, except
that
backslashes are used to separate directories.
- URLs are given in
the
format:
http://server.domain/path/file.html
In these URLs, server is the server name where
applications
are run; domain is your
Internet
domain name; path is the
server's
directory structure; and file
is
an individual filename. Italic items in URLs are placeholders.
- Font conventions
include:
- The monospace font
is used for sample code and code listings, API and language elements
(such
as function names and class names), file names, pathnames, directory
names,
and HTML tags.
- Italic type is used for code variables.
- Italic
type
is also used for book titles, emphasis, variables and placeholders, and
words
used in the literal sense.
- Bold type is
used
as either a paragraph lead-in or to indicate words used in the literal
sense.
- Installation root
directories
are indicated by install_dir in this
document.
By default, the location of install_dir on UNIX-based platforms is:
/opt/SUNWwbsvr/
On Windows, it is:
C:\Sun\WebServer6.1
Product Support
If you have problems with your system, contact
customer
support using one of the following mechanisms:
Please have the following information
available
prior to contacting support. This helps to ensure that our support
staff
can best assist you in resolving problems:
- Description of the problem, including
the
situation where the problem occurs and its impact on your operation
- Machine type, operating system
version,
and product version, including any patches and other software that
might
be affecting the problem
- Detailed steps on the methods you have
used
to reproduce the problem
- Any error logs or core dumps