Sun Java System Application Server Platform Edition 8 Installation Guide |
About This Guide
This guide describes how to create and run Java 2 Platform, Enterprise Edition (J2EE platform) applications that follow the new open Java standards model for Java Servlet, JavaServer Pages (JSP), Enterprise JavaBeans (EJB), and other J2EE components in the Sun Java System Application Server Platform Edition 8 environment.
This preface contains information about the following topics:
Who Should Use This GuideThe intended audience for this guide is the person who develops, assembles, and deploys J2EE applications in a corporate enterprise.
This guide assumes you are familiar with the following topics:
- J2EE specification
- HTML
- Java programming
- Java APIs as defined in the Java Servlet, JavaServer Pages (JSP), Enterprise JavaBeans (EJB), and Java Database Connectivity (JDBC) specifications
- Structured database query languages such as SQL
- Relational database concepts
- Software development processes, including debugging and source code control
Using the DocumentationThe Sun Java System Application Server Platform Edition 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.
How This Guide Is OrganizedThis guide provides instructions for installing the Sun Java System Application Server, and includes the following topics:
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:
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