![]() |
Sun ONE Application Server 7 Administrator's Configuration File Reference |
About This BookThe book discusses the purpose and use of the configuration files for Sun Open Net Environment (Sun ONE) Application Server 7, including server.xml, init.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
- Using the Documentation
- How This Guide Is Organized
- Documentation Conventions
- Product Support
Who Should Use This Guide
The intended audience for this guide is the person who administers and maintains the Sun ONE Application 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, EJB, and JDBC specifications
- Relational database concepts
Using the Documentation
The Sun ONE Application Server manuals are available as online files in Portable Document Format (PDF) and Hypertext Markup Language (HTML) formats, at:
The following table lists tasks and concepts described in the Sun ONE Application Server manuals. The left column lists the tasks and concepts, and the right column lists the corresponding manuals.
How This Guide Is Organized
This book has the following modules:
- "Basics of Server Operation"
This module introduces the major configuration files that control the Sun ONE Application Server and describes how to activate and edit them.
- "Server Configuration Files"
This module discusses the server.xml file, which controls most aspects of server operation.
- "Syntax and Use of init.conf"
This module discusses the directives you can set in the init.conf file to configure the Sun ONE Application Server during initialization.
- "MIME Types"
This module discusses the MIME types file, which maps file extensions to file types.
- "Other Configuration Files"
This module lists other important configuration files and provides a quick reference of their contents.
- "Time Formats"
This module describes the format strings used for dates and times in the server log.
- "Alphabetical List of Server Configuration Elements"
"Alphabetical List of Directives in init.conf"
These modules provide alphabetical lists for easy lookup of elements in server.xml and directives in init.conf.
Documentation Conventions
This section describes the types of conventions used throughout this guide:
General Conventions
The following general conventions are used in 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 for most platforms are indicated by install_dir in this document. Exceptions are noted in Conventions Referring to Directories.
By default, the location of install_dir on most platforms is:
Solaris 8 non-package-based Evaluation installations:
user's home directory/sun/appserver7
Solaris unbundled, non-evaluation installations:
/opt/SUNWappserver7
Windows, all installations:
C:\Sun\AppServer7
For the platforms listed above, default_config_dir and install_config_dir are identical to install_dir. See Conventions Referring to Directories for exceptions and additional information.
- Instance root directories are indicated by instance_dir in this document, which is an abbreviation for the following:
default_config_dir/domains/domain/instance
- UNIX-specific descriptions throughout this manual apply to the Linux operating system as well, except where Linux is specifically mentioned.
Conventions Referring to Directories
By default, when using the Solaris 8 and 9 package-based installation and the Solaris 9 bundled installation, the application server files are spread across several root directories. These directories are described in this section.
- For Solaris 9 bundled installations, this guide uses the following document conventions to correspond to the various default installation directories provided:
install_dir refers to /usr/appserver/, which contains the static portion of the installation image. All utilities, executables, and libraries that make up the application server reside in this location.
default_config_dir refers to /var/appserver/domains, which is the default location for any domains that are created.
install_config_dir refers to /etc/appserver/config, which contains installation-wide configuration information such as licenses and the master list of administrative domains configured for this installation.
- For Solaris 8 and 9 package-based, non-evaluation, unbundled installations, this guide uses the following document conventions to correspond to the various default installation directories provided:
install_dir refers to /opt/SUNWappserver7, which contains the static portion of the installation image. All utilities, executables, and libraries that make up the application server reside in this location.
default_config_dir refers to /var/opt/SUNWappserver7/domainswhich is the default location for any domains that are created.
install_config_dir refers to /etc/opt/SUNWappserver7/config, which contains installation-wide configuration information such as licenses and the master list of administrative domains configured for this installation.
Product Support
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