|Sun ONE Application Server 7, Update 1 Developer's Guide|
About This Guide
This guide describes how to create and run Java 2 Platform, Enterprise Edition (J2EE) applications that follow the new open Java standards model for Servlets, Enterprise JavaBeans (EJB components), and JavaServer Pages (JSPs) on the Sun Open Net Environment (Sun ONE) Application Server 7. In addition to describing programming concepts and tasks, this guide offers sample code, implementation tips, reference material, and a glossary.
This preface contains information about the following topics:
- Who Should Use This Guide
- Using the Documentation
- How This Guide Is Organized
- Related Information
- Documentation Conventions
- Product Support
Who Should Use This Guide
The 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
- Java programming
- Java APIs as defined in servlet, JSP, EJB, and JDBC specifications
- Structured database query languages such as SQL
- Relational database concepts
- Software development processes, including debugging and source code control
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.
Sun ONE Application Server Documentation Roadmap
For information about
See the following
Late-breaking information about the software and the documentation
Supported platforms and environments
Introduction to the application server, including new features, evaluation installation information, and architectural overview.
Getting Started Guide
Installing Sun ONE Application Server and its various components (sample applications, Administration interface, Sun ONE Message Queue).
Creating and implementing J2EE applications that follow the open Java standards model on the Sun ONE Application Server 7. Includes general information about application design, developer tools, security, assembly, deployment, debugging, and creating lifecycle modules.
Creating and implementing J2EE applications that follow the open Java standards model for web applications on the Sun ONE Application Server 7. Discusses web application programming concepts and tasks, and provides sample code, implementation tips, and reference material.
Developer's Guide to Web Applications
Creating and implementing J2EE applications that follow the open Java standards model for enterprise beans on the Sun ONE Application Server 7. Discusses EJB programming concepts and tasks, and provides sample code, implementation tips, and reference material.
Developer's Guide to Enterprise JavaBeans Technology
Creating clients that access J2EE applications on the Sun ONE Application Server 7
Developer's Guide to Clients
Creating web services
Developer's Guide to Web Services
J2EE features such as JDBC, JNDI, JTS, JMS, JavaMail, resources, and connectors
Developer's Guide to J2EE Features and Services
Creating custom NSAPI plugins
Developer's Guide to NSAPI
Performing the following administration tasks:
- Using the Administration interface and the command line interface
- Configuring server preferences
- Using administrative domains
- Using server instances
- Monitoring and logging server activity
- Configuring the web server plugin
- Configuring the Java Messaging Service
- Using J2EE features
- Configuring support for CORBA-based clients
- Configuring database connectivity
- Configuring transaction management
- Configuring the web container
- Deploying applications
- Managing virtual servers
Editing server configuration files
Administrator's Configuration File Reference
Configuring and administering security for the Sun ONE Application Server 7 operational environment. Includes information on general security, certificates, and SSL/TLS encryption. HTTP server-based security is also addressed.
Administrator's Guide to Security
Configuring and administering service provider implementation for J2EE CA connectors for the Sun ONE Application Server 7. Includes information about the Administration Tool, DTDs and provides sample XML files.
J2EE CA Service Provider Implementation Administrator's Guide
Migrating your applications to the new Sun ONE Application Server 7 programming model from the Netscape Application Server version 2.1, including a sample migration of an Online Bank application provided with Sun ONE Application Server
Using Sun ONE Message Queue.
The Sun ONE Message Queue documentation at:
How This Guide Is Organized
This guide provides a Sun ONE Application Server environment overview for designing programs, and includes the following topics:
- "Designing Applications"
This module summarizes the Sun ONE Application Server application design process and offers effective development guidelines.
- "Developing J2EE Applications"
This module describes how to set up a development environment and provides basic steps for creating application components.
- "Securing J2EE Applications"
This module describes how to write secure J2EE applications, which contain components that perform user authentication and access authorization for servlets and EJB business logic.
- "Assembling and Deploying J2EE Applications"
This module describes the contents of Sun ONE Application Server modules and how these modules are assembled separately or together in an application.
- "Debugging J2EE Applications"
- "Developing Lifecycle Listeners"
Finally, a Glossary and Index are provided.
You can find a directory of URLs for the official specifications at install_dir/docs/index.htm. Additionally, we recommend the following resources:
General J2EE Information:
Core J2EE Patterns: Best Practices and Design Strategies by Deepak Alur, John Crupi, & Dan Malks, Prentice Hall Publishing
Java Security, by Scott Oaks, O'Reilly Publishing
Programming with Servlets and JSPs:
Java Servlet Programming, by Jason Hunter, O'Reilly Publishing
Java Threads, 2nd Edition, by Scott Oaks & Henry Wong, O'Reilly Publishing
Programming with EJB components:
Enterprise JavaBeans, by Richard Monson-Haefel, O'Reilly Publishing
Programming with JDBC:
Database Programming with JDBC and Java, by George Reese, O'Reilly Publishing
JDBC Database Access With Java: A Tutorial and Annotated Reference (Java Series), by Graham Hamilton, Rick Cattell, & Maydene Fisher
This section describes the types of conventions used throughout this guide:
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:
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.
- Solaris 8 non-package-based Evaluation installations:
user's home directory/sun/appserver7
- Solaris unbundled, non-evaluation installations:
- Windows, all installations:
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:
- UNIX-specific descriptions throughout this manual apply to the Linux operating system as well, except where Linux is specifically mentioned.
Forte for Java 4.0 has been renamed to Sun ONE Studio 4 throughout this manual.
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.
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