This guide discusses the purpose and use of the configuration files for Sun Java System 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:
The intended audience for this guide is one who administers and maintains the Sun Java System Web Server.
This guide assumes you are familiar with the following topics:
J2SE specification
HTTP
HTML
XML
Java programming
Java APIs as defined in servlet, JSP, and JDBC specifications
Relational database concepts
The Sun Java System Web Server manuals are available as online files in PDF and HTML formats at http://docs.sun.com/app/docs/coll/1308.5.
The following table lists the tasks and concepts described in the Sun Java System Web Server manuals.
Table P–1 Sun Java System Web Server Documentation Roadmap
This guide has the following chapters:
Chapter 1, Basics of Server Operation
Introduces the major configuration files that control the Sun Java System Web Server and describes how to activate and edit them.
Chapter 2, Server Configuration Elements in server.xml
Describes the server.xml file, which controls most aspects of server operation.
Chapter 3, Syntax and Use of magnus.conf
Describes the directives you can set in the magnus.conf file to configure the Sun Java System Web Server during initialization.
Chapter 4, Predefined SAFs in obj.conf
describes the predefined SAFs used in the obj.conf file.
Describes the MIME types file, which maps file extensions to file types.
Chapter 6, Other Server Configuration Files
Lists other important configuration files and provides a quick reference of their contents.
Appendix A, Configuration Changes Between iPlanet Web Server 4.1 and Sun Java System Web Server 6.1
Describes the changes in configuration files between the 4.x and 6.1 versions of Sun Java System Web Server.
Appendix B, Configuration Changes Between iPlanet Web Server 6.0 and Sun Java System Web Server 6.1
Describes the changes in configuration files between the 6.0 and 6.1 versions of Sun Java System Web Server.
Describes the format strings used for dates and times in the server log.
Appendix D, Alphabetical List of Server Configuration Elements
Provides an alphabetical list for easy lookup of elements in server.xml and directives in magnus.conf.
Appendix E, Alphabetical List of Predefined SAFs
Provides an alphabetical list for easy lookup of directives in obj.conf.
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
If you have problems with your system, contact customer support using one of the following mechanisms:
The online support web site at:
The telephone dispatch number associated with your maintenance contract
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