Sun Java™ System Application Server Platform Edition 8 Administration Guide |
About This Guide
This guide describes how to configure and administer the Sun Java System Application Server Platform Edition 8. This preface contains information about the following topics:
Who Should Use This GuideThis guide is intended for information technology administrators in production envrionments. This guide assumes you are familiar with the following topics:
Using the DocumentationThe Sun Java System Application Server Platform Edition 8 manuals are available as online files in Portable Document Format (PDF) and Hypertext Markup Language (HTML).
The following table lists tasks and concepts described in the Sun Java System Application Server manuals.
Table 1 Sun Java System Application Server Documentation Roadmap
For information about
See the following
Late-breaking information about the software and the documentation. Includes a comprehensive, table-based summary of supported hardware, operating system, JDK, and JDBC/RDBMS.
Release Notes
Installing the Sun Java System Application Server software and its components, such as sample applications, the Administration Console, and the high-availability components. Instructions for implementing a basic high-availability configuration are included.
Installation Guide
Creating and implementing Java 2 Platform, Enterprise Edition (J2EE platform) applications intended to run on the Sun Java System Application Server that follow the open Java standards model for J2EE components and APIs. Includes general information about application design, developer tools, security, assembly, deployment, debugging, and creating lifecycle modules. A comprehensive Sun Java System Application Server glossary is included.
Developer’s Guide
Using J2EE 1.4 platform technologies and APIs to develop J2EE applications and deploying the applications on the Sun Java System Application Server.
J2EE 1.4 Tutorial
Information and instructions on the configuration, management, and deployment of the Sun Java System Application Server subsystems and components, from both the Administration Console and the command-line interface. Topics include cluster management, the high-availability database, load balancing, and session persistence. A comprehensive Sun Java System Application Server glossary is included.
Administration Guide
Editing the Sun Java System Application Server configuration file,
domain.xml
.Reference
Migrating your applications to the new Sun Java System Application Server programming model, specifically from iPlanet Application Server 6.x and from Netscape Application Server 4.0. Includes a sample migration.
Migrating and Redeploying Server Applications Guide
Information on solving Sun Java System Application Server problems.
Troubleshooting Guide
Utility commands available with the Sun Java System Application Server; written in manpage style.
Utility Reference Manual
Using the Sun Java System Message Queue 3.5 software.
The Sun Java System Message Queue documentation at:
http://docs.sun.com/db? p=prod/s1.s1msgqu
How This Guide Is OrganizedThe organization of this guide corresponds to the layout of the Admin Console, the browser-based tool for administering the Application Server. Each chapter begins with conceptual information, followed by procedural sections that explain how to perform specific tasks with the Admin Console.
Documentation ConventionsThis section describes the types of conventions used throughout this guide:
General Conventions
The following general conventions are used in this guide:
- 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:
For the platforms listed above, default_config_dir is identical to install_dir. See "Conventions Referring to Directories" for exceptions and additional information.
Conventions Referring to Directories
By default, when using the Solaris package-based or Linux RPM-based installation, the application server files are spread across several root directories. This guide uses the following document conventions to correspond to the various default installation directories provided:
- install_dir refers to
/opt/SUNWappserver
, which is the default location for 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/SUNWappserver/domains
, which is the default location for any domains that are created.
Contacting SunYou might want to contact Sun Microsystems in order to:
Give Us Feedback
If you have general feedback on the product or documentation, please send this to appserver-feedback@sun.com.
Obtain Training
Application Server training courses are available at:
http://training.sun.com/US/catalog/enterprise/web_application.html
Visit this site often for new course availability on the Sun Java System Application Server.
Contact Product Support
If you have problems with your system, contact customer support using one of the following mechanisms:
- The online support web site at:
http://www.sun.com/supportraining/
- 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. Here are some of the commonly used commands:
- Detailed steps on the methods you have used to reproduce the problem
- Any error logs or core dumps
- Configuration files such as:
- For an application, whether the problem appears when it is running in a cluster or standlone